match
Set up Match for iOS code signing certificate management
release
Submit iOS app to App Store for review
setup-fastlane
Set up Fastlane for iOS/macOS app automation
snapshot
Automate App Store screenshot capture across devices and languages
clarity-gate
Pre-ingestion verification for epistemic quality in RAG systems. Ensures documents are properly qualified before entering knowledge bases. Produces CGD (Clarity-Gated Documents) and validates SOT (Source of Truth) files.
2026-coach
Executive coaching skill that helps you plan your 2026 using research-backed process goals. Guides you through discovery questions, creates outcome goals, converts them to daily behaviors, and sets up accountability systems. Use when you want to plan your year, set goals, or need a coach to help you stay focused.
askme
Explore intent with Verbalized Sampling before planning. Use when the task is ambiguous, you need maximum clarifying questions, or you want collaborative or adversarial mode via `/askme`.
ast-grep
Run code analysis and refactoring with ast-grep. Use when doing AST-based modifications, structural search, linting across code shape, or replacing regex-fragile transformations.
contexts
Use when the user says "get context on X", "how does X work", or wants architectural orientation before coding.
gh-fix-ci
Use when the user asks to debug or fix failing CI checks on a GitHub pull request.
inits
Creates or improves an AGENTS.md file. Use when onboarding to a repo, or capturing conventions, constraints, and rationale that are expensive to rediscover.
proof-driven
Use when using property-based testing, theorem proving, or formal proof tactics with a zero-unproven-property policy.
resolve
Use when addressing review feedback or analyzing whether a comment is valid.
test-driven
Run test-driven development. Use when implementing features or fixes with TDD, or refactoring with coverage.
type-driven
Develop with refined types. Use when modeling a domain, encoding a state machine in types, hardening an API boundary against malformed input, or the user says "make invalid states unrepresentable" or "parse don't validate".
strategy
Use when defining product strategy, setting a north star, starting or redirecting a product, or an existing STRATEGY.md has gone stale.
strict-validation-setup
Bootstrap strict-mode tooling and per-task GOALS.md scaffolding so an agentic loop can self-verify. Use when setting up a new project, making a task self-verifying, or scaffolding goals for an agentic loop.
subagent-driven
Execute a multi-task plan. Use when the user says "execute with subagents", or hands you an ordered multi-task plan to run.
sync-docs
Detect docs-vs-code drift from a diff. Use when the user says "sync docs" or "update changelog".
taste
Apply taste judgment to an artifact or decision. Use when asking "is this slop?", "overkill?", "audit", or "taste-test this", or setting a taste register.
teach
Use when the user wants to learn a skill or concept across multiple sessions in a persistent teaching workspace at the cwd: they ask you to set up a course, design lessons, build a learning workspace, or explicitly request ongoing teaching. Not for one-off explanations or quick answers.
tests-adversarial
Write adversarial tests. Use when hardening error handling, validating boundary behavior, or hunting silent failures.
tests-purge-unneeded
Delete tests that do not catch real bugs. Use when reviewing legacy suites, investigating slow CI, sweeping tests after a refactor, or checking whether the type system already covers an assertion.
tidy
Dispatch compress operations. Use when the user says "tidy" or names a file, diff, memory, workspace, git stack, or doc to tidy.
to-questionnaire
Use when the user wants to turn a knowledge gap into an async questionnaire for someone else: identify the recipient and the needed answers, then write a discovery questionnaire to to-questionnaire-<slug>.md. Triggers: "turn this into a questionnaire", "questionnaire for X", "I need to ask someone else", async information gathering.
validation-first-driven
Define state machines, invariants, and temporal properties. Use when building protocols, workflows, concurrent systems, or lifecycle-heavy state.
verification-before-completion
Requires fresh, actually-run evidence before any claim that a task is complete. Use when about to tell the user a task, feature, or fix is done, complete, finished, working, or ready, or about to report a DONE or passing status.
work
Execute a plan or concrete work prompt end-to-end. Use when implementing from a plan or spec path, or a clear build request; use /debug for open-ended bugs.
workflows-driven
Drive decomposable work as a deterministic multi-subagent workflow: phased fan-out under per-task contracts with adversarial verification. Use for audits, migrations, broad research or review sweeps, work needing independent cross-checks before committing, or scale one context cannot hold.
worktree
Set up isolated git worktrees: create a new branch for fresh work, or attach a worktree to an existing branch/PR/commit.
writing-beats
Use when the user wants to build an article as a choose-your-own-adventure journey of beats, sequence raw material one move at a time, or says "write this beat by beat", "journey-style article", or "assemble beats".
writing-fragments
Use when the user wants to generate raw writing material before structuring it, has scattered ideas for an article, or says "collect fragments", "mine this topic", or "gather notes first".
writing-shape
Use when the user wants to turn a pile of fragments into a polished article, shape raw material paragraph by paragraph, or says "write this up", "turn this into a post", or "structure these fragments".
writing-skills
Reference for writing and editing skills so they run predictably — invocation choice, information hierarchy, leading words, pruning, and the failure modes that make a skill misfire. Use when authoring or refactoring a SKILL.md, or the user says "write a skill", "improve this skill", or "why does my skill fire unreliably".
zoom-out
Step up one layer of abstraction and map surrounding modules, callers, and invariants. Use when the local view is too narrow, the region is unfamiliar, or before committing to a change in unknown code.
ai-collab-protocols
Surface in-task AI collaboration protocols one tactic at a time. Use when the user refers to entities by colloquial labels, asks how to structure a Claude workflow, or describes a multi-step workflow without durable URLs.
api-design
Guide stable API and interface design. Use when creating REST or GraphQL endpoints, defining type contracts, or establishing frontend/backend or module boundaries.
atomic-issues-prs
Publish a change-set as atomic GitHub issues or PRs. Use when the user says "atomic PRs" or wants one issue/PR per logical change.
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
autolearn
Compound a solved problem into a durable in-repo learning doc. Use when a verified non-trivial fix lands, the user says "compound this", "document this fix", or "remember this".
autopilot
Run a hands-off plan-to-ship pipeline by chaining existing skills. Use when the user says "autopilot", "take this from plan to shipped", "run the whole pipeline", "hands-off ship it", or "do the end-to-end build".
axiom-mode
Switch to ODIN's compact formal-logic English register using predicate claims and ASCII keywords. Use when the user requests "axiom", "axiom-mode", "axiom-compact", "formal-logic", or "compact form".
batch-ask-me
Use when the user wants to walk a complex design space round by round: map the decision tree, fire the current frontier as batched single-select questions, and loop until shared understanding is reached. Triggers: multi-fork decisions, ambiguous requirements, unresolved prerequisites, "batch ask me", "clarify the design space".
brainstorm
Explore vague or ambitious ideas into a right-sized requirements-only plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning, not for a decisive verdict on whether to adopt or switch to a specific external technology, library, or platform.
breaking-driven
Demolish bloated code and re-derive it clean, cutting every surface the rebuilt contract does not name. Use for a repo-wide bloat sweep, when patching a subsystem has stopped paying, or when the user says "this whole module is bloated", "rewrite this properly", or "break it and rebuild".
browser-testing
Test and debug browser code with Chrome DevTools MCP. Use when building or debugging browser UI, inspecting the DOM, capturing console errors, analyzing network requests, or verifying visual output.
can-i-help
Route contributors to data-backed contribution opportunities. Use when the user asks "where can I help", "what can I contribute", "find a good first issue", or "what should I work on".
caveman
Switch to a verbosity-reduction response register. Use when the user says "caveman", "compact mode", "less tokens", "be brief", or context-window pressure calls for shorter replies.
ci-cd
Set up or modify CI/CD pipelines and deployment automation. Use when setting up build pipelines, automating quality gates, configuring test runners in CI, or establishing deployment strategies.
cleanup-codebase
Reduce internal duplication, dead code, and ceremony. Use when you spot dead fields, redundant wrappers, or speculative abstractions in code you are already editing.
Page 805 of 1671 · 83537 results
