Loading...
Loading...
Found 8,853 Skills
Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.
Control video generation requests before execution. Use this when the user asks for a simple clip, storyboard video, UGC video, podcast clip, reference video, talking-head, image-to-video, text-to-video, or research-handoff video and the skill must classify the request before handing it to video-request-architect and a runner such as seedance-submitter or video-batch-runner.
Bubble integration. Manage Applications. Use when the user wants to interact with Bubble data.
Review whole-repo test quality, rerun coverage, score remaining worth-testing files, inspect slow-drift and stale test debt, and publish the next testing batch. Use every few weeks or before large breaking changes and rearchitecture.
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
Per-client asset templates scoped by workspace.
First-pass privilege log review — make the obvious privilege calls and flag the hard ones for attorney review without making close calls. Use when the user says "review the privilege log", "priv log", "check privilege on these docs", or has a log to QA before production.
Status dashboard for cheat-on-content. Displays current mode / rubric version / calibration progress / pending retros / pool status / whether SQLite needs an upgrade / whether rubric should be bumped. **Can be invoked at any time with no side effects**. Trigger words: "状态" / "看板" / "status" / "What should I do now?" / "How's the progress?"
Used for header-only preflight of one DICOM series folder before conversion or inference. Not for de-identification or clinical clearance.
Use when checking live Capy task or PR state through Brave, Computer Use, or a Capy browser panel.
Crear o actualizar Architecture Decision Records (ADRs) en docs/adr/. Activar siempre que el usuario quiera documentar, registrar, actualizar o cambiar el estado de una decisión arquitectónica — incluso si no usa la palabra "ADR". Frases que activan este skill: "registrar decisión", "documentar por qué usamos X", "dejar constancia de esta elección técnica", "decision record", "cambiar ADR a Accepted", "marcar como Superseded", "crear ADR", "actualizar ADR", "nuevo ADR", "ADR-XXX". Usar también cuando el usuario describa una tensión arquitectónica que deba quedar documentada.
Used when executing implementation plans containing independent tasks in the current session