claude

mattpocock-skills

Agent skills for real engineering and product lifecycle (discovery, grilling, spec/ticket flows, TDD, zero-downtime migrations, security review, QA, and post-mortems).

1 on GitHubby Matt Pocockv1.5.0MITupdated 2 days agoengineering
/

Plugin mattpocock-skills from marketplace op3616windows in op3616windows/skills. Commands read from the repo's manifest — 2 days ago.

What it installs

Skills (48)

  • ask-matt

    Ask which skill or flow fits your situation. A router over the skills in this repo.

  • code-review

    Review the changes since a fixed point (commit, branch, tag, or merge-base) along three axes: Standards (does the code follow this repo's documented coding standards?), Spec (does the code match what the originating issue/spec asked for?), and Security (does the code introduce AppSec or privacy vuln

  • codebase-design

    Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

  • diagnosing-bugs

    Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

  • domain-modeling

    Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

  • e2e-testing

    Author, maintain, run, and debug resilient end-to-end browser tests (Playwright, Cypress) for critical user journeys. Use when writing automated E2E tests, codifying acceptance criteria into browser suites, or diagnosing flaky browser tests.

  • expand-contract

    Plan and execute zero-downtime database schema migrations, breaking API changes, or wide refactors using the Expand-Contract pattern. Use when modifying database schemas, altering API contracts, or refactoring high-blast-radius code.

  • grill-with-docs

    A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

  • implement-spec

    Implement the result of /to-spec and /to-tickets in code.

  • implement

    Implement a piece of work based on a spec or set of tickets.

  • improve-codebase-architecture

    Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

  • post-mortem

    Lead a blameless post-mortem analysis after an incident or severe bug: establish timeline, run 5 Whys, identify detection gaps, record ADRs, and trigger retro.

  • pr

    Use when writing a PR body.

  • prototype

    Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

  • qa-session

    Lead an interactive acceptance and exploratory QA session against a feature or bugfix, verifying acceptance criteria and filing standardized bug reports.

  • research

    Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

  • retro

    Conduct a retrospective on a coding session.

  • security-review

    Audit a git diff, branch, or PR for security vulnerabilities, authorization flaws, PII leaks, and injection risks. Use when conducting security reviews, auditing PRs for security, or verifying tenant isolation.

  • setup-matt-pocock-skills

    Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

  • tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

  • telemetry-design

    Define product analytics events, structured logs, system metrics, and error boundaries for a feature. Use when designing telemetry, observability, tracking plans, or verifying event emissions in tests.

  • to-spec

    Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

  • to-tickets

    Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

  • triage

    Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

  • ux-states

    Design and specify a comprehensive UI state matrix (empty, loading, optimistic UI, error recovery, accessibility, and localization) for frontend components or user flows. Use when designing, reviewing, or implementing user interfaces.

  • wayfinder

    Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

  • wizard

    Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can pe

  • chief-of-staff

    Pursue a long-running goal in a single session by co-ordinating subagents.

  • claude-handoff

    Hand the current conversation off to a fresh background agent that picks up the work immediately.

  • loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

  • setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module, with implementation hidden in subfolders and reachable only through its entry-point files. User-invoked.

  • software-factory

    Shared language for designing a software factory: the tasks it runs and the services it plugs into.

  • writing-beats

    Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.

  • writing-fragments

    Writing, explore: mine raw fragments, no structure yet.

  • writing-shape

    Writing, exploit: shape raw material into an article, paragraph by paragraph.

  • git-guardrails-claude-code

    Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.

  • migrate-to-shoehorn

    Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

  • scaffold-exercises

    Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.

  • setup-pre-commit

    Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

  • grill-me

    A relentless interview to sharpen a plan or design.

  • grilling

    Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

  • handoff

    Compact the current conversation into a handoff document for another agent to pick up.

  • release-notes

    Generate user-facing release notes from merged pull requests, commits, and closed issues since the last release, translating technical diffs into customer value.

  • shape-problem

    Interview and synthesize raw customer feedback, support logs, or metrics into a focused problem statement before discussing technical solutions.

  • teach

    Teach the user a new skill or concept, within this workspace.

  • to-questionnaire

    Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

  • wait-what

    Stop. That last message did not land: re-pitch it.

  • writing-for-agents

    Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

View source on GitHub aihero.dev

Similar plugins

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

nextjs

claude

Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.

6 skills

vercel/next.js 143,495

Taste Skill

claudecodex

tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.

1 skill

Leonxlnx/taste-skill 114,391

5 skills + 35 modes + Material Passport pipeline. Includes v3.6.7 cross-model audit gate and v3.6.8 generator-evaluator contract.

5 skills · 16 commands · 4 agents · hooks

Imbad0202/academic-research-skills 56,698

obsidian

claude

Claude Skills for Obsidian

6 skills

kepano/obsidian-skills 51,587

Maintain mattpocock-skills?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted