Go deep.
Ship with proof.

Use architect. Design a stateful cache boundary, compare two ownership models, derive types from caller usage and implement the selected sketch within authorized scope.

Use arena. Compare two cache API designs in isolated directories, judge completed candidates, select the cleaner boundary and adapt one useful idea from the other design.

Use automate-me. After baseline acceptance, update an existing jay-mode from newer workspace history, retain uncontradicted preferences and show the draft before an authorized local edit.

Use benchmark-checklist. Vet export on a 60k-row dataset across revisions A and B using at least 5 alternating runs per side before reporting a speedup.

Use blast-radius. Review cache invalidation and trace a caller outside the diff through teardown timing, then run the real pinned library to test the safety fact.

Use bro. After an explanation about concurrent writes, invoke bro to get the same point in plain language.

Use correct. Use /correct to investigate two reverted changes that copied the same unsafe state owner, then propose one owner and prove the old mistake fails.

Use create-verification-skill. Inspect a notes app toolbar, keyboard shortcuts and CLI; generate its local verification skill and feature map, then exercise one feature and retain proof after cleanup.

Use figure-it-out. Use /figure-it-out for a large migration, capture the old behavior, verify atomic units and record an inconclusive measurement as an open limit.

Use how. Trace an API request from its route through its service calls and storage layer, citing the files read.

Use interrogate. Challenge a branch diff with identical reviewer prompts, then trace a disputed null-input finding to its caller before categorizing it.

Use maintain-verification-skill. Audit a save feature that now requires entitlement and asynchronous completion; reconcile source and live proof, update confirmed doc drift, and report product regressions without changing product code.

Use make-bot-ui. Design buttons that POST an agreed action to a local server, which wakes the configured bot routine without exposing its sender key.

Use no-comments. Invoke no-comments on an authorized diff to remove redundant narration while retaining its license header and justified public API contract.

Use poteto-help. For a question about reproducing an app bug, read the Bug fix playbook, provide its reproduction and verification recipe, and disclose missing app verification support without starting work.

Use poteto-mode. For a scoped feature, read the full mode and Feature playbook, name its data shape, write the checkpoint, assign an authorized fresh worker and inspect its resulting diff before reporting evidence.

Use principle-attack-the-premise. After two balancing fixes fail, count which workers retain excess load across runs and trace the assignment that keeps selecting them.

Use principle-boundary-discipline. Validate an incoming order quantity in an HTTP adapter, pass a typed order to pure pricing logic and remove redundant internal quantity checks.

Use principle-build-the-lever. Migrate one file by hand, build an idempotent codemod, and rerun it on that file to compare the result before applying it to the remaining files.

Use principle-encode-lessons-in-structure. Require a source revision in the release-record schema and reject records that omit it, then remove the redundant reminder.

Use principle-exhaust-the-design-space. Compare a command palette, a direct manipulation canvas and a guided form for a novel editing interaction before choosing its implementation.

Use principle-experience-first. Choose three polished import controls over ten rough controls because users can finish and recover from the core import workflow with clear feedback.

Use principle-explain-the-number. Before reporting a parser speedup, check completed requests, repeated-run spread, cache effects and the runtime limiter using benchmark-checklist.

Use principle-fix-root-causes. For a crash after restart, reproduce it and inspect stale serialized state before adding a nil-check guard.

Use principle-foundational-thinking. Before building a job queue, define job state and worker ownership, trace claim and status queries, and isolate concurrently mutable state.

Use principle-guard-the-context-window. For a large repository corpus, assign authorized workers bounded document groups and inspect their summaries. Without workers, read narrower groups sequentially and label reduced capability.

Use principle-laziness-protocol. Remove a forwarding adapter that adds no behavior, preserving the service rounding and tax contract.

Use principle-make-operations-idempotent. After an interrupted payment job, inspect its action identity and destination outcome before authorized recovery with the same idempotency key.

Use principle-migrate-callers-then-delete-legacy-apis. Inventory callers of an internal request API, move them to the new contract, update contract tests and delete the old API in one reviewed unit.

Use principle-minimize-reader-load. Trace an invoice total through two one-caller pass-through wrappers, collapse them where they hide no decisions, and derive total from rows instead of synchronizing a cached module value.

Use principle-model-the-domain. Replace queued, running and completed job booleans with states carrying worker IDs or results and explicit allowed transitions.

Use principle-never-block-on-the-human. Apply an authorized local code fix and present the diff; wait for required human review before merging, while continuing independent authorized work.

Use principle-outcome-oriented-execution. Migrate a module to the agreed interface in phases, declare temporary caller breakage, check touched code during migration and verify the completed target after removing temporary adapters.

Use principle-prove-it-works. After a feature compiles, run the feature and read its actual stored value before declaring it complete.

Use principle-redesign-from-first-principles. When adding tenant ownership, rethink the data model and access paths with ownership as a foundational assumption, update references, and deliver coherent increments.

Use principle-separate-before-serializing-shared-state. Give an indexer and a metrics worker separate state files instead of separate fields in one state.json; combine their independent facts when reading the report.

Use principle-sequence-verifiable-units. Migrate one schema boundary, run its concrete migration check, then begin the next unit only after green; deliver the failing test before its fix.

Use principle-subtract-before-you-add. Inspect callers of an obsolete handler, remove that handler and its redundant validator, then add the specified replacement without speculative guards.

Use principle-test-behavior-not-implementation. Call slugify with Hello, World! and assert hello-world; confirm that an empty function fails the assertion when execution is available.

Use principle-type-system-discipline. Replace completed plus optional completedAt with open and done variants, where done carries its timestamp.

Use recall. Recall seven days of cache work in the active workspace, use a complete supplied capsule first, sweep prior incidents and verify the current branch and PR state.

Use reflect. Reflect on a debugging session, reject already-covered advice, route enforceable checks to Backlog and show proposed skill edits for approval.

Use setup-pstack. Run /setup-pstack when model enumeration is unavailable; retain inherited choices, reject an unknown slug, and return a session-only table without writing personal configuration.

Use show-me-your-work. Record a verified checkpoint and a reverted decision, resolve their evidence, audit this run and request an independent different-family reviewer.

Use swarm. Use /swarm to cover separate repository slices at an exact commit; reject a result missing its sampling method, retry it once and report any remaining coverage gap.

Use tdd. For an incorrect empty-input result with an existing local unit test, add the intended-behavior assertion, run it and observe the failure, fix the implementation, then run the same test and report the passing result.

Use teach. Explain a supplied chat virtualization subsystem using its actual rendering and loading code, then layer in the reasons and edge cases as requested.

Use technical-writing. Rewrite a how-to about budget.mjs and budget.json while keeping the lower-only --write rule and CI failure condition.

Use typescript-best-practices. Replace a JSON.parse cast and optional-field state bag with schema parsing and a kind-discriminated union; keep number[] for a total sum and strengthen a partial newest-session input.

Use unslop. Rewrite a supplied paragraph to remove chatbot praise, filler, jargon, and unnecessary passive voice without adding facts.

Use why. Trace a retry threshold through git history, PR discussion, a linked ticket and release telemetry, separating stated rationale from correlation.