Planning
claudeTurn an idea into tickets — find and test ideas, write the spec, cut thin slices and triage them in any tracker.
7 skills
Prove the work in the real app — unattended builds and loops, user-style testing, change risk, review and PRs.
Plugin engineering from marketplace dotfiles in cpeaustriajc/dotfiles. Commands read from the repo's manifest — today.
blast-radiusThis skill should be used when the user types /blast-radius on a change: find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or
break-itThis skill should be used when the user says "break it", "try to break this", "monkey test", "bug bash", "dogfood" or "QA this like a user", or after a flow change. It drives the app as a careless user. Visual sign-off: ui-polish.
cleanupThis skill should be used when the user says "cleanup", "clean up after yourself", "tear down the dev server", "archive this session" or "clean up stale branches". It removes what a session left once safe. Not code tidying.
commitThis skill should be used when the user says "commit" or words along those lines. It commits the changes as atomic commits in the repo's style and pushes them; `local` skips the push. Typed only: /commit.
create-prThis skill should be used when the user asks to open a pull request: "open a PR", "make a PR for this branch", "create a draft PR" or "PR this against develop". It commits, runs the fast checks, pushes and opens the PR.
implementThis skill should be used when the user types "/implement" with a ticket or a spec. It builds one ready ticket without supervision: it gets the ticket from the tracker, trusts its answers, builds it in checked slices, runs review-loop on the commits and opens a PR that closes it. With a spec or seve
review-loopThis skill should be used after a build or a fix, before its PR is marked ready, and when the user says "run the review loop" or "is this ready for review". It runs verify, code review and simplify in rounds until a round changes nothing.
Turn an idea into tickets — find and test ideas, write the spec, cut thin slices and triage them in any tracker.
7 skills
Sign off UI work and motion — check it against the design, add missing microinteractions, make launch videos.
3 skills
Keep what the team learns — a decision log, research pages, lessons from past sessions, and a recap of recent work.
3 skills
Show it as a picture — paint scenes in code to a gallery standard.
1 skill
Turn corrections into fixes — suggests /hone <skill> after you correct Claude during a dotfiles skill.
Hold /implement to its stop point — denies a merge or push past commit, pr, ready or merged, and blocks an early stop.
Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.
1 MCP server
Build powerful, stateful CLI interfaces for any GUI application using the cli-anything harness methodology.
5 commands
Automates browser interactions for web testing, form filling, screenshots, and data extraction
12 skills
Use Alibaba Open Code Review from local Codex.
2 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.