Menu
SkillsMP has collected 14 skills from jasonm4130/claude-skills. Open a skill to review its source and details.
Showing 14 of 14 collected skills.
Covers the skill-authoring rules specific to this repo and the empirical wording findings that general guidance does not contain — matching guidance form to failure type, micro-testing against a no-guidance control, and the plugin/marketplace conventions a…
Use when the user knows what they want built and says "/adr", "write an ADR for X", "decide and build X", or "ADR-driven". Turns an intent into a grounded, cited, build-ready ADR at docs/adr/YYYY-MM-DD-<slug>.md — load-bearing decisions surfaced to the human…
Write a structured handoff / resume document for this session so the next session can pick up exactly where this one left off. Use when the user asks to write a handoff, "prep for resume", "session handoff", or when context is high and you want to preserve…
Run an interactive session retrospective. Reads the per-session event log (maintained by the PostToolUse hook) and uses git diff/status/log as memory primer, then walks through specific moments via adaptive questions driven by what changed, and writes…
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Do NOT use once the cause is already established, or for adding new behaviour — that is implementation, not diagnosis.
Use when implementing any feature or bugfix, before writing implementation code. Do NOT use inside the subagent-driven-development loop, which runs its own per-task implement→review→fix cycle and supersedes this skill there.
Use when you have a spec or requirements for a multi-step task, before touching code. Do NOT use to produce the spec itself (use brainstorming) or to execute a plan that already exists (use subagent-driven-development).
Use when writing or revising a durable written artifact — README, ADR, design doc, PR description, release notes, runbook, error message, user-facing docs. Gives a positive writing system (reader model, sentence positions, document jobs), not a ban-list. Do…
Guidance for distinctive, intentional frontend/UI design — aesthetic direction, typography, layout, motion, and copy — when building new UI or reshaping existing UI. Gates by scope before designing: a light/surgical change (one component, one page section,…
Use when a written implementation plan exists and the user wants to execute it — "execute this plan", "implement the plan", "run the plan", "build it", "subagent-driven development". Plans + confirms in this session, then hands a lightweight task list to a…
Audit a repo's documentation for internal contradictions, stale claims, orphans and bloat after it has accumulated commits, then report findings for the user to disposition. Use when the consolidation nudge fires, or when the user asks to consolidate, audit,…
Use when pinning down domain terminology, building a ubiquitous language or project glossary, disambiguating overloaded or vague terms, or maintaining a CONTEXT.md — or when another skill needs to sharpen the domain model. Do NOT use for recording…
Use before feature or design work that carries real ambiguity or a load-bearing decision, ahead of writing implementation code — explores intent, requirements and design first. Do NOT use for trivial changes, mechanical edits, or work whose design is already…
Cross-provider adversarial review of a finalized plan, spec, design doc, ADR, or code diff using OpenAI Codex (GPT-5.6 Terra). AUTO-TRIGGER at plan gates — invoke immediately after any of: (1) a brainstorming spec is written and user-approved, (2) a…