skills

Write and maintain concise Architecture Decision Records that capture durable technical decisions in the repository. Use when the user asks for an ADR, architecture decision record, decision log, to record a technical decision, to compare architectural options, or to update/supersede an existing decision.

Turn ADRs, technical decisions, architecture discussions, or brownfield refactor context into an engineering-focused spec. Use when work has no product user stories, when converting ADRs into implementation-neutral specs, or when planning internal architecture migrations, API contracts, state ownership, provider boundaries, or platform refactors.

Refactor existing code without changing observable behavior. Use when the user asks to improve structure, reduce technical debt, remove code smells, split large functions/classes, reduce duplication, make code easier to test, or prepare code for a feature while preserving behavior.

Set up Husky pre-commit hooks with lint-staged using Biome, plus type checking and tests. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time

Enforce a lightweight task contract for new agent work so scope, non-goals, acceptance criteria, implementation notes, completion summary, verification, and remaining risks are explicit. Use when a user asks an agent to begin a new task with deliverables, implementation work, research work, debugging work, review work, or verification expectations; when creating a task prompt for another agent; or when delegating work to a subagent.

Audit a repository's agent-readiness. Use when a user wants to improve AGENTS.md, CLAUDE.md, CONTEXT.md, repo-local agent docs, domain context, issue tracker guidance, bootstrap/setup for agents, or install Matt Pocock skills for their agent harness.

Use when refactoring code for clarity without changing behavior, when working code is harder to read, maintain, or extend than it should be, or when reviewing code that has accumulated unnecessary complexity.