Devil's advocate against a ticket's implementation as built — run every round of the pick loop, not once. Attacks the code that now exists with evidence — hidden coupling it introduced, a cheaper route it should have taken, an irreversible or load-bearing step, or a route the plan got wrong. Read-only; returns a…
Derives a ticket's non-functional requirements while it is still being written — as measurable statements that each carry their own verification. Invoke in /ticket-new step 2 (alongside the research agents, before the step 2.5 grilling) and on /ticket-refine's resume path, so unresolved requirements become grilling…
Turn shot-plan.json into one renderable HyperFrames composition (compositions/index.html). Everything stays in the HF ecosystem — HTML is the source of truth; a single paused GSAP timeline carries all motion; the engine seeks it. Category-specific build rules live in categories/ /module.md; this file is the shared…
Turn a request into a shot-plan.json for a short (3–30s) design-led motion graphic. You run in two parts around the asset-sourcing step: Part 1 (plan) before sourcing, Part 2 (design) after. You do NOT write composition code — that's the Builder. Schema: references/shot-plan-ir.md.
Code-simplify code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked via Task after a parent gathers diff and file contents. Uses the code-simplify skill as the complete rubric.
Specialized agent that runs the full Playwright e2e suite in the project's Dockerized Chromium environment (docker-compose.e2e.yml) and reports pass/fail. Use before pushing to GitHub to guarantee e2e never regresses on main. Trigger on "run e2e", "e2e before push", "playwright check", or invoked by the pre-push git…
Use this agent when you need to audit dependencies for vulnerabilities, resolve version conflicts, optimize bundle sizes, or implement automated dependency updates.
Use this agent when you need to create, architect, or overhaul comprehensive documentation systems including API docs, tutorials, guides, and developer-friendly content that keeps pace with code changes.
Writes and repairs .nika.yaml workflows with the deterministic authoring protocol. Use when the user wants repeatable AI work turned into a workflow file, asks for a .nika.yaml, or a nika check must pass. Routes intent to a template, fills the SLOT markers, then loops nika check until rc=0. Its craft is WRITING …
Root-causes failed or paused Nika runs from their hash-chained traces. Use when nika run exited red, a run paused on a prompt and needs the exact resume line, a NIKA-XXXX runtime finding needs a cause, or a trace must be verified and explained. Evidence-first — reads .nika/traces via nika trace; its craft is the…
Ports an existing script, Makefile target, CI job or prompt chain to a checkable .nika.yaml workflow. Use when converting ad-hoc automation to nika, when a shell script wraps LLM/HTTP/file plumbing, or when a prompt chain in a doc should become a runnable, auditable file. Inventories side effects first, maps steps to…
Surgical 1-2 file edit. Typo fixes, single-function rewrites, mechanical renames, comment removal, format-preserving tweaks. Hard refuses 3+ file scope. Returns caveman diff receipt. Use when scope is bounded and obvious; do NOT use for new features, new files (unless asked), or cross-file refactors.