Loopify Bootstrap
Use when seeding a repository with loop materials such as a goal prompt, Loop Contract, quality gate, trace template, acceptance checklist, and test skeletons.
Loopify Review
Use when auditing a Loop Contract, trace, quality gate, or done claim — or when acting as the independent verifier that grades a loop's success claim and writes verdict.md.
Loopify Spec
Use when converting a prose spec, PRD, README, issue, or goal prompt into a Loop Contract with requirements, checks, authority boundaries, stop rules, and trace requirements.
Loopify Demo
Use when creating demo-ready loop seed projects with a normal app target, material pack, quality gate, acceptance tests, trace template, and presenter script.
Loopify Codex Sdk
Use when adding Codex SDK scripts or templates as loop actuators for repair, review, context building, trace summarization, or meta-loop proposal steps.
Loopify Governance
Use when adding budgets, approvals, rollback plans, data/privacy limits, dependency policy, authority boundaries, and harness-change contracts to higher-risk loops.
Loopify Run
Use when executing an existing Loop Contract by running checks, observing failures, patching, rerunning, updating the trace, and stopping only with evidence.
Loopify Debug
Use when a loop is stuck, repeating failures, flaking, patching the wrong target, hitting an authority conflict, or burning turns without convergence.
Loopify Checks
Use when turning vague requirements into concrete automated checks, visual review gates, manual review items, acceptance tests, or quality-gate commands.
Loopify Retro
Use after a loop completes to extract reusable lessons from the contract, trace, final diff, failures, useful checks, ambiguities, and rejected attempts.
Loopify Trace
Use when creating, maintaining, auditing, or summarizing loop trace receipts that record checks, failures, patches, rationale, evidence, and stop reasons.
James
Use immediately after an agent writes or materially edits a concept, PRD, plan, specification, design document, strategy document, architecture proposal, or similar planning artifact, and whenever the user says "invoke James", "run James", "James this", or "James-review". Reviews whether a future agent can act on the document using only declared project-owned context, persists recipes and append-…
Dojo
Use when an Agent Skill needs behavioral evaluation, hardening, trigger tuning, isolation auditing, or evidence before release, or when the user explicitly asks to create a skill through Dojo. Runs coverage-scaled baseline and skilled scenarios, pressure-tests discipline skills, holds out graduation cases, checks routing collisions, and records proof under ~/.dojo. Responds to "dojo", "test this…
Taste Extractor
Extracts portable taste from any accessible medium into an evidence-traced profile and downstream production brief. Use when the user asks to extract, distill, reverse-engineer, or capture the style, taste, feel, visual language, voice, or character of an interface, image, text, video, music, object, brand, or experience so another agent can create new work with the same character without copying…