59 skills (repositories by mattpocock) · sorted by popularity
Clarify a project's business concepts and terminology through concrete scenarios and comparisons with code. Record agreed definitions in a glossary and document significant design trade-offs in ADRs, records explaining why a decision was made.
Turn notes, fragments, or transcripts into an article through a paragraph-by-paragraph discussion. Compare opening options, establish what readers need to know, and save agreed sections in a separate document while preserving the original material.
Learn a new skill or concept through short, interactive lessons tailored to your goals and previous learning. The skill creates HTML lessons, reference sheets, and learning records to support practice and review across multiple sessions.
Plan work too large for one agent session by mapping decisions and their dependencies in an issue tracker. Resolve questions one at a time, preserve the reasoning, and identify what must be settled before execution can begin.
Turn a course plan into numbered exercise folders with problem, solution, and explanation variants. Create starter readme files, check naming and links with the project’s linter, and fix structural errors before committing.
Build features or fix bugs by writing one failing test, then the smallest implementation that passes it. Tests check behavior through public interfaces, the entry points callers use, so they remain useful when internal code changes.
Create an interactive bash script for setup or migration steps that require a person. It guides dashboard actions, captures values, saves configuration and GitHub secrets, and requests confirmation at each stage.
Build a disposable prototype to answer a design question. Explore logic and changing states through a shareable HTML demo, or compare distinct interface variations, then record the findings and carry validated decisions into real code.
Summarize an ongoing conversation and launch a fresh background agent to continue the work. The handoff includes the next focus, references to existing documents, and suggested skills, with sensitive information removed.
Examine a plan, decision, or idea through structured rounds of questions with recommended answers. Organize dependent decisions into a branching map, resolve assumptions, and build a shared understanding before taking action.
Investigate difficult bugs and performance slowdowns by building a repeatable test or script that detects the exact symptom. Reduce the failing case, compare possible causes, and verify the fix with checks that catch the bug if it returns.
Turn collected Markdown material into an article by choosing one narrative step at a time. Compare possible directions, introduce concepts before relying on them, and build the article while preserving the user's edits.
Create and edit documents that AI agents follow, including skills and project instructions. Organize steps and reference material, define clear completion criteria, and refine document links and wording to reduce duplication and unnecessary context.
Ask the agent to explain its last message again with some context. The revised explanation uses ASD-STE100, a simplified technical English standard, and the vocabulary defined in the project's glossary.
Turn plans, specifications, or conversations into small development tickets that each deliver verifiable behavior. Identify which tickets must finish first, review the breakdown together, and publish approved tickets to local files or the configured issue tracker.
Implement work described in a specification or tickets, checking types and running tests along the way. Review the completed changes with the code-review skill, then commit the implementation to the current branch.
Refine a plan or design through a persistent interview that asks probing questions. This skill starts the conversation by invoking the related grilling skill, providing an entry point for examining and sharpening what you have in mind.
Review a codebase for structural problems that make understanding and testing difficult. Compare refactoring candidates in an HTML report with before-and-after diagrams, then explore the chosen option through questions about constraints, design, and tests.
Coordinate subagents, separate agents assigned tasks, to pursue a long-running goal in one session. Maintain dialogue with the user while improving working conditions, shared rules, and access to information needed for future tasks.
Set up Claude Code hooks that block Git commands such as push, hard reset, and forced deletion before execution. Choose project-wide or global settings, customize the blocked commands, and verify that the hook rejects a test command.
Turn a decision that needs someone else’s knowledge into a Markdown questionnaire. Clarify who will answer and what information is needed, then create prioritized questions with answer spaces for asynchronous replies or a meeting.
Turn a specification and its tickets into code by coordinating multiple agents around task dependencies. Combine their work on one integration branch, use test-driven development, review the result, and close tickets through the issue tracker’s workflow.
Choose which related skill to use and in what order for planning, building, debugging, or maintaining software. It explains routes through the available workflows and helps select the next step based on your situation and project size.
Write a pull request description that helps reviewers understand a code change. Use a compact diagram or diff, show before-and-after evidence, and explain how reversible the change is and what areas it may affect.