Leaderboard/Software Engineering/skills
Last commit on August 21, 2026·Created on February 3, 2026

mattpocock/skills

A library of structured engineering patterns for architectural design and codebase maintenance
Combined rank
#1
across all skills
In Software Engineering
#1
category rank
Stars
266k
+2.1% in last 7d
Forks
22.4k
+2.1% in last 7d
Watchers
1.5k
+1.9% in last 7d
Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
TL;DR

This collection provides a set of specialized skills for technical leads and architects to maintain rigor across the software development lifecycle. It focuses on formalizing activities such as domain modeling, module design, and the recording of architectural decision records.

The repository includes specific workflows for diagnosing complex performance regressions and conducting dual-axis code reviews that evaluate changes against both documented coding standards and original specifications.

WHO IT'S FOR
Technical leads / architects
designing deep modules and domain models
Backend / infrastructure engineers
diagnosing hard bugs and performance regressions
AI agent / automation builders
implementing AI-navigable code structures
Software engineers
performing standards-based code reviews
Repository contents

38 skill files

Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.

Use this skill collection

Follow the documented setup, then try a first task.

I’m using

Claude Code plugin from terminal

Installs: The complete managed, read-only mattpocock-skills Claude Code plugin bundle, with automatic updates. · Claude Code

Before you start
  • Claude Code with plugin support

Run from: Run the setup step from the repository being configured; no directory requirement is documented for the plugin-install command.

  1. In a terminal, install the mattpocock-skills plugin from Claude Code's official marketplace.

    claude plugins install mattpocock-skills
  2. Open an agent session in the target repository and enter this agent-session command once for that repository. Answer its questions about the issue tracker, triage labels, and documentation location.

    /setup-matt-pocock-skills
.claude-plugin/plugin.json · Checked Sep 18, 2026README.md · Checked Sep 18, 2026docs/engineering/setup-matt-pocock-skills.md · Checked Sep 18, 2026

Give it something to do.

Suggested first task

Stress-test a plan with one interview round

Uses grilling

  • A plan, decision, or design to examine
Use the grilling skill to stress-test this plan or design: [paste the plan or design]. Map its decisions as a design tree, then ask only the first currently answerable frontier round. Number each question, include your recommended answer, and wait for my responses before continuing.
Suggested first task

Start one test-driven vertical slice

Uses tdd

  • A repository or relevant code path
  • A small feature or bug described as externally observable behavior
Use the tdd skill for this small feature or bug in [repository or relevant path]: [describe the required external behavior]. First identify the public interface and propose the seam to test for my confirmation. After I confirm it, complete one red-to-green vertical slice: one failing behavior test followed by the minimum implementation needed to pass it. Do not refactor yet.
skills/engineering/tdd/SKILL.md · Checked Sep 18, 2026
Suggested first task

Create a focused discovery questionnaire

Uses to-questionnaire

  • Questionnaire topic
  • Recipient's role, expertise, and relationship to you
  • The decisions or facts you need from the recipient
Use the to-questionnaire skill to create a discovery questionnaire about [topic] for [recipient role or relationship], so I can decide or accomplish [what you need back]. First ask me about the recipient and the specific knowledge gap. Then draft the questionnaire as documented and save it in the current directory; do not send it.