agentleFS
kapadiaskapadias/nonna/.claude/skills/implement/SKILL.md

implement

Skill0 starsChanged 46 days agoMITView on GitHub

Implement code against an existing failing test or a clear spec — minimal, typed, reviewable, matching the surrounding style. Use when the test/spec already exists.

192 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • liufeng1976Skill

    setup-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

  • GoogleSkill

    ask-matt

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

    Also in 91 projects that use this

  • RoentekSkill

    loop-me

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

    Also in 50 projects that use this

  • AWSSkill

    to-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

  • ryotaroh180105Skill

    claude-handoff

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

    Also in 42 projects that use this

  • GoogleSkill

    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.

    Also in 168 projects that use this

  • +3 more from google

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 175 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the neighborhood: Read the specific spans you will touch and the patterns around them (use explorer for anything broad).

    line 15
  2. Distinctive:

    Verify locally: run lint + type-check + tests.

    line 21

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Implement: $ARGUMENTS

Steps

  1. Anchor on the gate. Confirm a failing test or unambiguous spec exists. If it does not, stop and run /tdd first — production logic without a test is not allowed (see .claude/rules/dev-process.md).
  2. Read the neighborhood. Read the specific spans you will touch and the patterns around them (use explorer for anything broad). Match local naming, error handling, and idiom.
  3. Write the minimal code that makes the test pass. Follow .claude/rules/engineering.md: typed at boundaries, validate untrusted input at the edge, pure where it matters, fail loud in the critical path, no secrets, no print.
  4. Refactor with tests green: remove duplication, clarify names, keep the diff small and reviewable.
  5. Verify locally: run lint + type-check + tests. Leave the tree green.

Guardrails

See .claude/rules/safety.md — irreversible/outward-facing actions require explicit authorization; fail loud on the critical path, never swallow errors silently.

Output

The diff, confirmation the suite is green, and a handoff to /review.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.