implement
Skill0 starsChanged 15 days agoMITView on GitHub
Build a planned change in small, test-first steps, with the layer checklists and a self-review. Use when you write product code.
192 other projects use a version of this.
Adopted by
Most recently taken up by
- lhotwll217/owner-operatortheir own version, first seen Nov 16, 2026
- chuckplayer/claude-agent-packtheir own version, first seen Nov 16, 2026
- philoserf/claude-code-configtheir own version, first seen Nov 15, 2026
- muxy-app/muxytheir own version, first seen Nov 15, 2026
- geoffbremner/skillstheir own version, first seen Nov 15, 2026
- SireJeff/k0ntexttheir own version, first seen Nov 15, 2026
Used with
Projects with it also use setup-ts-deep-modules, ask-matt and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 43 projects that use this
GoogleSkillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Also in 91 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 50 projects that use this
AWSSkillto-questionnaire
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
Also in 88 projects that use this
ryotaroh180105Skillclaude-handoff
Hand the current conversation off to a fresh background agent that picks up the work immediately.
Also in 42 projects that use this
GoogleSkillto-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.
Also in 168 projects that use this
- +3 more from google
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- mattpocock/skills★ 325ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- foambubble/foam★ 17ksame name
- formbricks/formbricks★ 13ksame name
- ArcReel/ArcReel★ 6.6ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- fallow-rs/fallow★ 5.3ksame name
- withcoral/coral★ 4.9ksame name
- bestofjs/bestofjs★ 3.1ksame name
182 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/CLAUDE.mdCLAUDE.md
- a11y-auditSkill
- architecture-reviewSkill
- bootstrap-projectSkill
- capture-screenshotsSkill
- customizeSkill
- deliver-featureSkill
- design-reviewSkill
- docs-upkeepSkill
- fix-bugSkill
- handoffSkill
- leadSkill
- log-decisionSkill
- refine-requirementsSkill
- release-readinessSkill
- reproduce-in-worktreeSkill
- security-auditSkill
- ship-prSkill
- start-taskSkill
- sync-branchSkill
- threat-modelSkill
- verify-featureSkill
- vet-dependencySkill
- write-adrSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 175 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Run the step's check, then the related suite: Never move on while red. Paste failures.
- Distinctive: line 66
Lifecycle: delete, leave, sign out, a second device, an old app version talking to the new server.
- Distinctive: line 74
Every line traces to the task, with no debug code and no secrets.
“Common” is measured: kept by at least 6 in 10 of the 175 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Implement
Playbook files named here: when the project has its own copy at
.playbook/local/<same path>, use that copy instead.
Work: $ARGUMENTS
AGENTS.md is the law: the project's rules win over anything here. Principles: ${CLAUDE_PLUGIN_ROOT}/principles/01-engineering.md (how code is written), 02-architecture.md, 04-design-and-ux.md, 05-accessibility-i18n.md, 06-security-privacy.md, 08-testing-qa.md, 09-data-and-migrations.md.
Before the first line
- Have a plan with checks (
start-task). If there isn't one, write the short version now: steps, and a verify for each. - Know the product intent: the acceptance criteria, the requirement ids, and the owner decisions already made. If a customer-visible behaviour isn't settled (a wording, a limit, what happens on delete, who sees what), stop and ask. Don't invent product.
- Read before writing: the code you'll change, its tests, and the nearest existing example of the same kind of change. Follow that pattern.
- Check the docs for the installed version of any API you'll call. Memory isn't a source.
- Order the work bottom up: data → server → client data → UI → docs. Each step leaves the project green.
The loop, per step
- Test first where it fits: a failing test for a bug, a unit test for a rule, a DB test for a policy. For UI, decide what you'll look at.
- Write the least code that passes it, matching the surrounding style, names and comment density. Comments explain why.
- Run the step's check, then the related suite. Never move on while red. Paste failures; don't paper over them.
- Stay in scope. Touch only what the step needs. Note anything else you find, and file it later.
Layer checklists
Data (09)
- A migration, never an edit to a merged one; types regenerated
- Tenant id; deny-by-default policies; grants (column grants where needed); can/can't tests per role
- Constraints and size caps in the DB; triggers for cross-row or role rules
- Soft delete plus purge coverage; files follow rows
- Realtime: published or not, with a column list if any column is secret
- Content tables are included in the data export
Server / API / functions (06, the stack add-on)
- Validate at the boundary (types, sizes, enums); derive the tenant from the session, never from the client
- Idempotent creates (a client id or an idempotency key); a stable error code for each failure, mapped on the client
- Rate limits where abuse is possible; no content in logs or notifications
- Jobs are idempotent, record their outcome, and can be re-planned
Client data (02)
- Query keys scoped by tenant, and by user for "me" queries
- Writes are idempotent (client UUID) through the project's write path (an outbox if offline matters)
- One retry layer; errors classified by code; live updates invalidate
- Entitlement or plan checks before costly creates, with a friendly limit message
UI (04, 05)
- Kit components and tokens only; no hard-coded colours, fonts, curves or strings
- Loading, error (retry), offline and empty states through the shared gate; never "empty" before data arrives
- Copy in the catalogue, from the reader's side; names and pronouns from data
- Labels, roles and hints; targets at the minimum size in
05; a cue besides colour; works at the largest text size; reduce motion respected - Destructive actions confirm with their consequence
The product check (before calling it built)
Walk the change as each person who meets it:
- The first-time user, and the empty account.
- The other person or tenant member: what do they see, and when (realtime, push)?
- The unhappy paths: offline, the app killed mid-action, slow network, a server error, a limit reached, no permission.
- Time: someone in another zone, near midnight, on a leap day.
- Lifecycle: delete, leave, sign out, a second device, an old app version talking to the new server.
Anything that behaves in a way the customer wouldn't expect is either fixed now (in scope) or raised as a question or ticket. Never left silent.
Finish the build
- Full check suite from
AGENTS.md(lint, typecheck, unit tests, plus DB and integration tests when data changed). All green. - Self-review the whole diff (
git diff <base>...):- Every line traces to the task, with no debug code and no secrets.
- Nothing your change left unused remains.
- No speculative abstraction.
- No unnecessary try/catch: each catch handles the error (retry, user-facing state, context and re-throw, or cleanup); nothing is swallowed, re-thrown unchanged, or logged twice (
${CLAUDE_PLUGIN_ROOT}/principles/01-engineering.md§7). - No unnecessary comments: none that restate the code, narrate the change, keep commented-out code, or are TODOs without a ticket (§5).
- Note what the release needs: a new build, an env var, a migration deploy, an owner action.
- Note rules to record: new helpers or conventions for
AGENTS.md, and decisions for the Decision Log (docs-upkeepwrites them). - Don't push or open a PR: that's
ship-pr, on the owner's word. As a delegated agent in your own worktree (product-engineer), commit there on its own branch so the orchestrator can review and bring it in; in the main session, leave committing toship-pr. - Hand off (
${CLAUDE_PLUGIN_ROOT}/templates/handoff.md):- The changes by file; the checks you ran, with their results.
- Decisions you took, and questions you hit.
- What verification should focus on (the riskiest path, the states, the screens to capture).
- Anything still running.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

