Menu
SkillsMP a collecté 55 skills depuis ryanportfolio/AI-Firmware. Ouvrez un skill pour examiner sa source et ses détails.
Affichage de 40 skills collectés sur 55.
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.
Langue du texte source : anglais
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Langue du texte source : anglais
Use when implementing any feature or bugfix, before writing implementation code
Langue du texte source : anglais
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Langue du texte source : anglais
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.
Langue du texte source : anglais
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.
Langue du texte source : anglais
Use when the user asks to humanize, de-AI, de-slop, voice-match, or review prose for AI tells before publishing.
Langue du texte source : anglais
Use when the user explicitly asks to lab or prototype a visual, UI, motion, or game-feel element with live tuning before production implementation.
Langue du texte source : anglais
Use when executing an implementation plan with independent tasks in the current session and exposed multi-agent tools.
Langue du texte source : anglais
Use when the user asks to add, install, or create a repo-local skill that must work in future Claude Code and Codex sessions.
Langue du texte source : anglais
Use only when the user explicitly invokes $advocate to challenge a change just made before it lands. Do not trigger from natural-language requests.
Langue du texte source : anglais
Use before non-trivial features, refactors, performance work, bug fixes, or applying a performance-review finding in web or TypeScript code.
Langue du texte source : anglais
Use only when the user invokes $conflict and a merge, rebase, or cherry-pick has unmerged paths or conflict markers, especially after parallel edits.
Langue du texte source : anglais
Use when the user asks to rewrite a rough request into a polished, copy/paste-ready prompt for another agent or a fresh session.
Langue du texte source : anglais
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.
Langue du texte source : anglais
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.
Langue du texte source : anglais
Use when the user asks for a self-contained audit prompt to paste into a separate fresh session for independent verification.
Langue du texte source : anglais
Use when the user asks to review, audit, or stress-test recent code changes with fresh independent agents; requires exposed multi-agent tools.
Langue du texte source : anglais
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.
Langue du texte source : anglais
Use after confirmed multi-attempt problem solving reveals durable gotchas, or when the user asks to capture or save session learnings.
Langue du texte source : anglais
Use only when the user explicitly asks to enable session-wide automatic commit, push, PR, and merge; not for one-shot shipping requests.
Langue du texte source : anglais
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.
Langue du texte source : anglais
Use before unfamiliar project-area edits, when the user asks what the project knows or its pitfalls, or when saving durable project-specific learning.
Langue du texte source : anglais
Use when the user explicitly asks to ship changes end to end, including scope audit, branch, verification, commit, push, and pull request.
Langue du texte source : anglais
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.
Langue du texte source : anglais
Use only when the user explicitly invokes $why to challenge the assistant's immediately prior recommendation; never trigger from ordinary why questions or paraphrases.
Langue du texte source : anglais
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.
Langue du texte source : anglais
Use only when the user invokes /conflict and a merge, rebase, or cherry-pick has unmerged paths or conflict markers, especially after parallel edits.
Langue du texte source : anglais
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.
Langue du texte source : anglais
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.
Langue du texte source : anglais
Use when the user asks to humanize, de-AI, de-slop, voice-match, or review prose for AI tells before publishing.
Langue du texte source : anglais
Use after confirmed multi-attempt problem solving reveals durable gotchas, or when the user asks to capture or save session learnings.
Langue du texte source : anglais
Use when executing an implementation plan with independent tasks in the current session and exposed multi-agent tools.
Langue du texte source : anglais
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Langue du texte source : anglais
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Langue du texte source : anglais
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
Langue du texte source : anglais
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Langue du texte source : anglais
Use when implementing any feature or bugfix, before writing implementation code
Langue du texte source : anglais
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
Langue du texte source : anglais
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Langue du texte source : anglais