ryanportfolio/AI-Firmware

writing

Use when writing or editing any prose a person will read (site copy, guides, docs, READMEs, UI text, titles, captions, emails, PR descriptions, release notes) or when a draft reads as machine-made.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

writing-skills

Use when creating new skills, editing existing skills, or verifying skills work before deployment

optimize-context

Use when the user asks to reduce per-turn context or token load, trim kernels, skills, or connectors, or propagate a generic context optimization to the starter.

brainstorming

Use when brainstorming or designing a product, interface, workflow, architecture, or behavior change with unresolved goals or material tradeoffs; not for routine or fully specified work.

humanizer

Use when the user asks to humanize, de-AI, de-slop, voice-match, or review prose for AI tells before publishing.

lab

Use when the user explicitly asks to lab or prototype a visual, UI, motion, or game-feel element with live tuning before production implementation.

subagent-driven-development

Use when executing an implementation plan with independent tasks in the current session and exposed multi-agent tools.

addskill

Use when the user asks to add, install, or create a repo-local skill that must work in future Claude Code and Codex sessions.

advocate

Use only when the user explicitly invokes $advocate to challenge a change just made before it lands. Do not trigger from natural-language requests.

applying-best-practices

Use before non-trivial features, refactors, performance work, bug fixes, or applying a performance-review finding in web or TypeScript code.

conflict

Use only when the user invokes $conflict and a merge, rebase, or cherry-pick has unmerged paths or conflict markers, especially after parallel edits.

enhance-prompt

Use when the user asks to rewrite a rough request into a polished, copy/paste-ready prompt for another agent or a fresh session.

fable-mode

Use proactively for hard layered work with dependent steps, load-bearing unknowns, repeated failures, or verification-sensitive handoff; also when the user asks for Fable mode.

forge-repo-ui-skill

Use when the user wants a repository-specific UI or design skill synthesized from current agent skills; not for ordinary UI implementation or backend-only work.

handoff-audit

Use when the user asks for a self-contained audit prompt to paste into a separate fresh session for independent verification.

impartial-review

Use when the user asks to review, audit, or stress-test recent code changes with fresh independent agents; requires exposed multi-agent tools.

init-project

Use once in a spawned starter repo when the user asks to initialize or configure it, or when FILL IN markers remain; never auto-run in a claude-starter template checkout.

learning

Use after confirmed multi-attempt problem solving reveals durable gotchas, or when the user asks to capture or save session learnings.

merge

Use only when the user explicitly asks to enable session-wide automatic commit, push, PR, and merge; not for one-shot shipping requests.

optimize-context

Use when the user asks to reduce per-turn context or token load, trim kernels, skills, or connectors, or propagate a generic context optimization to the starter.

recall

Use before unfamiliar project-area edits, when the user asks what the project knows or its pitfalls, or when saving durable project-specific learning.

safe-ship

Use when the user explicitly asks to ship changes end to end, including scope audit, branch, verification, commit, push, and pull request.

sync-starter

Use when the user asks to pull template improvements into a spawned repo, compare starter drift, or push a generic improvement back to the starter.

why

Use only when the user explicitly invokes $why to challenge the assistant's immediately prior recommendation; never trigger from ordinary why questions or paraphrases.

brainstorming

Use when brainstorming or designing a product, interface, workflow, architecture, or behavior change with unresolved goals or material tradeoffs; not for routine or fully specified work.

conflict

Use only when the user invokes /conflict and a merge, rebase, or cherry-pick has unmerged paths or conflict markers, especially after parallel edits.

fable-mode

Use proactively for hard layered work with dependent steps, load-bearing unknowns, repeated failures, or verification-sensitive handoff; also when the user asks for Fable mode.

forge-repo-ui-skill

Use when the user wants a repository-specific UI or design skill synthesized from current agent skills; not for ordinary UI implementation or backend-only work.

humanizer

Use when the user asks to humanize, de-AI, de-slop, voice-match, or review prose for AI tells before publishing.

learning

Use after confirmed multi-attempt problem solving reveals durable gotchas, or when the user asks to capture or save session learnings.

subagent-driven-development

Use when executing an implementation plan with independent tasks in the current session and exposed multi-agent tools.

dispatching-parallel-agents

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

executing-plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

finishing-a-development-branch

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

using-git-worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

using-superpowers

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions