Loading...
Loading...
Found 11,734 Skills
Create or revise agent skills. Use when adding a new skill file, renaming a skill, simplifying an existing skill, improving trigger descriptions, or deciding what belongs in a skill versus references, scripts, assets, or ordinary docs.
Emit and maintain a dagr run file — a live, contract-valid JSON description of recursive projects, tasks, attempts, gates, evidence, policies, events, and operator-message resolutions that `dagr view` renders as a DAG. Use when orchestrating agents or tracking multi-step work that a dagr pane should display.
Commit les changements, se synchronise avec main distant, push la branche courante et crée une Pull Request. Refuse de tourner directement sur main. Utilise sur /livre, ou quand l'utilisateur veut livrer/expédier son travail : "commit et push", "ouvre une PR", "livre ça", "ship", "envoie la PR", "finalise et pousse". Aval naturel de /branche.
Operate and collaboratively edit live Max/MSP patches through the maxforge MCP tools without screenshots, Max JavaScript, node.script, or raw thispatcher commands. Use for maxforge-related live inspection, human-edit adoption, isolated patch creation, desired-DSL preview/apply, acknowledgement verification, or broker/controller/recovery failures. On the first maxforge-related task in a session, check the latest coherent release and local version set with the bundled preflight; do not trigger merely for unrelated general Max/MSP questions. Use the maxforge skill for offline compilation.
When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).
This skill should be used when the user asks to revise a chapter, edit prose, continuity check, find inconsistencies, audit character state, check timeline consistency, line edit, developmental edit, polish a draft, or prepare existing story material for the next revision pass.
Builds standard operating procedures from a guided interview, screen-recording transcript, or existing draft. Use when the user says "write an SOP", "document this process", "make an SOP for X", "I keep redoing this", "delegate this to my VA", "onboarding doc for new hire", "write up how I do this", or asks to audit / clean up an existing SOP. Treats the user as the expert being interviewed and acts as a COO who pushes back on weak steps before they get written down.
pipeline: interview→plan→execute→QA→verify (idea→code)
Establish model registry standards, governance controls, metadata schemas, approvals, and lifecycle policies for enterprise AI deployments.
Plan, produce, register, validate and integrate UI, characters, scenes, animations, VFX, backgrounds and reference reconstruction resources for Phaser 4 games. Applicable to formal visual resources, visual systems, resource integration, visual reconstruction, runtime visual acceptance and authorization registration; not applicable to pure gameplay rule modifications.
Role for release and compliance of Phaser 4 mobile 2D games. Used for preparing builds, store materials, privacy settings, resource authorization, submission checklists, and release candidate packages for mini-games, iOS, Google Play, or new channels.
Manual image resource optimization task for Phaser 4 projects. Only to be used when the user explicitly calls $phaser4-game-image-optimization. It is used to inventory runtime bitmaps, generate compression candidates, verify image quality and channel compatibility, and replace resources under the control of global Work Items, task authorization, paths and evidence; A4-A6 operations require separate approval.