Claude Skills by rogue-dev-studio

Python 3.13 with uv package manager via mise. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `python` work when listed in TEAM.yaml or explicitly requested.

PyTorch deep learning framework. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `pytorch-ml` work when listed in TEAM.yaml or explicitly requested.

QGIS GIS operations MCP server. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `qgis` work when listed in TEAM.yaml or explicitly requested.

Canonical remote desktop / GUI access playbook: Guacamole, XFCE/xRDP, and VNC for environments that need a graphical desktop.

Canonical research and local/remote LLM usage: Ollama, DeepSeek/Perplexity style research MCPs, web/youtube summary, and research swarms.

Ruby development environment. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `ruby` work when listed in TEAM.yaml or explicitly requested.

Rust development environment. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `rust` work when listed in TEAM.yaml or explicitly requested.

SDKMAN - The Software Development Kit Manager for JVM tools. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `sdkman` work when listed in TEAM.yaml or explicitly requested.

Canonical guide for authoring and validating portable agent skills (SKILL.md packs) for the agent house catalog and team local skills.

Canonical skill/pack marketplace management: install, update, and audit agent skills across hosts (OpenSkills, agent-skills-cli, Claude marketplace).

Slack GIF generation. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `slack-gif-creator` work when listed in TEAM.yaml or explicitly requested.

Supabase CLI for local development, migrations, and edge functions. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `supabase-cli` work when listed in TEAM.yaml or explicitly requested.

Swift programming language. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `swift` work when listed in TEAM.yaml or explicitly requested.

Tmux session management. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `tmux-workspace` work when listed in TEAM.yaml or explicitly requested.

Expert UI/UX design for product interfaces: user flows, information architecture, wireframes, interaction patterns, accessibility, and a mandatory theme/brand alignment gate against the active project (PROJECT.md, design docs, existing tokens/visual language). Use before or alongside frontend work when designing screens, reviewing mockups, or validating that proposed UI matches the project theme already in progress or about to ship.

Canonical vector DB / knowledge-graph tooling for code and embeddings: RuVector CLI, RVF format, and GitNexus-style knowledge graphs.

Strategic mapping visualization. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `wardley-maps` work when listed in TEAM.yaml or explicitly requested.

Organize personal folders (Downloads, Desktop, Documents, arbitrary paths) by file category or by face clusters in photos. Modes: by-type, by-extension, by-face (when user explicitly asks to group images by wajah/face). Run ONLY when the user explicitly asks to merapihkan/organize/tidy a folder — never proactively. Aliases: personal-folder-tidy, organize-downloads, file-organizer, merapihkan-folder, organize-by-face.

Manual YouTube upload via local API and MCP. OAuth setup, auth status, and explicit confirm-gated video upload — never auto-upload after export.

Write, rewrite, and review CVs/résumés; screen candidates against a job description; summarize interview notes; generate interview questions. Use for CV, résumé, screening, ATS, talent, recruiter, kandidat, lamaran.

Employee onboarding checklists, policy FAQ from supplied documents, leave-request policy checks, coverage notes, and performance-review frameworks. Use for onboarding, karyawan baru, cuti, KPI, performance review, handbook, code of conduct, people ops.

Design and interpret workplace psychometric assessments for hiring: cognitive aptitude, work-style, integrity, collaboration, and stress scenarios. Generate rubrics, score sheets, and hiring recommendations for engineers and other roles. Use for psikotest, psychometric, aptitude test, personality assessment, DISC-like, cognitive test, integrity test, kandidat baru, screening perilaku.

Design and run technical interviews for hiring: backend, frontend, fullstack, live coding, system design light, take-home rubrics, and candidate prep. Score sheets and practice Q&A for recruiters and candidates. Use for technical interview, technical test, live coding, take-home assignment, wawancara teknis, tes coding, backend interview, frontend interview, simulasi interview engineer.

Alias. SIMRS module map and hospital workflows now live in simrs-hospital-ops. Use that skill for registration, outpatient, inpatient, pharmacy, billing, medical record, lab, radiology, and clinical role mapping.

Review a SIMRS / hospital information system against real hospital workflows: role-based access (dokter, spesialis, perawat, farmasi, kasir, RM), patient journey continuity (RM, kunjungan, ruangan), orders-results-meds-billing, audit, and BPJS bridging. Use when reviewing SIMRS modules, menus, RBAC, worklists, rekam medis, or clinical feature PRs.

Map Indonesian hospital regulatory and policy data elements to SIMRS application artifacts: business entity, table/column, API, UI, PDP class, RBAC, and audit. Use for data mapping, kamus data, field mapping, schema vs Permenkes rekam medis, UU PDP, informed consent, SEP, STR/SIP, SATUSEHAT, or when aligning RHS models to hospital rules.

SIMRS and hospital operations domain: patient journeys, clinical roles (dokter, spesialis, DPJP, perawat, bidan, farmasi, lab, radiologi, gizi, RM, kasir, pendaftaran), module map, ruangan/workspace, order-result-meds-billing chains. Use for SIMRS, rumah sakit, rekam medis, rawat jalan, rawat inap, IGD, BPJS, poli, resep, when designing or explaining hospital workflows.

Handle patient health data carefully in SIMRS work: minimize PII/PHI in logs, role-based access, export controls, audit on clinical and billing changes, and safe test fixtures. Use whenever features touch patient identity, medical record, resep, lab results, NIK, SEP, or billing identity.

Indonesian hospital and SIMRS regulatory checklist: UU Kesehatan, praktik kedokteran, keperawatan, PDP, rekam medis elektronik, SIMRS Permenkes, informed consent, rahasia kedokteran, SATUSEHAT, BPJS/JKN, kefarmasian, keselamatan pasien, akreditasi. Use when reviewing SIMRS compliance, kebijakan rumah sakit, UU, Permenkes, or legal obligations in hospital software. Not a substitute for legal counsel.

Technical assessment for SIMRS and hospital software roles: clinical workflows, API design for visits and orders, PHI handling, RBAC, BPJS integration scenarios, regulatory awareness, live coding, and take-home rubrics. Use for SIMRS technical interview, technical test rumah sakit, assessment developer SIMRS, wawancara teknis klinis, tes coding SIMRS, review kandidat IT rumah sakit.