mikemimik-skills

Skills

[!NOTE]
These skills are heavily inspired by Matt Pocock's skills mattpocock/skills. Please have a look there if you're looking for similar inspiration.

A collection of composable agent skills for Claude Code — small, hackable, and designed for real engineering work.

Quickstart

1. Run the command in claude to install:

/plugin marketplace add mikemimik/skills

2. Pick the skills you want and which coding agents to install them on. Make sure you select /setup-skills.

3. Run /setup-skills in your agent. It will:

   • Ask which issue tracker you use (GitHub, GitLab, local files, or other)
   • Ask what triage labels you apply to tickets
   • Ask where domain docs should live

4. You're ready to go.

Reference

Skills split on one axis — who can invoke them. User-invoked skills are reachable only when you type them (e.g. /implement); they orchestrate. Model-invoked skills can be invoked by you or reached for automatically by the agent when the task fits; they hold the reusable discipline.

User-invoked

• setup-skills — Configure a repo for these skills (issue tracker, triage labels, domain doc layout). Run once per repo before using the other skills.
• implement — Build the work described by a spec or set of tickets, driving /tdd at pre-agreed seams and closing out with /code-review.
• to-spec — Turn the current conversation into a spec and publish it to the issue tracker. No interview — just synthesizes what you've already discussed.
• to-tickets — Break a plan, spec, or conversation into tracer-bullet tickets with blocking edges, published to the configured tracker.
• wayfinder — Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets, resolved one at a time until the way is clear.
• handoff — Compact the current conversation into a handoff document so another agent can continue the work.
• writing-great-skills — Reference for writing and editing skills well: the vocabulary and principles that make a skill predictable.

Model-invoked

• grilling — Interview the user relentlessly about a plan or design until every branch of the decision tree is resolved.
• tdd — Test-driven development with a red-green-refactor loop. Builds features or fixes bugs one vertical slice at a time.
• code-review — Two-axis review of the diff since a fixed point: Standards (repo conventions + Fowler smell baseline) and Spec (does it match the originating issue?), run as parallel sub-agents.
• research — Investigate a question against high-trust primary sources and capture findings as a cited Markdown file, run as a background agent.
• domain-modeling — Build and sharpen a project's domain model — challenge terms, stress-test with scenarios, update CONTEXT.md and ADRs inline.
• judge — Audit the current conversation for AI persuasion tactics — escalation through ethos, logos, and pathos rather than conceding when challenged.