agentleFS
Sign inStart free
Marnie0415Marnie0415/pi-skills/implement/SKILL.md

implement

Skill1 starsChanged 5 months agoMITView on GitHub

Full implementation workflow - scout gathers context, planner creates plan, worker implements. Use for implementing features from scratch.

191 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

9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 171 edited versions we read keep these.

  • 9

    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
  1. Distinctive:

    Use the subagent tool with the chain parameter to execute this workflow:

    line 10
  2. Distinctive:

    Read the surrounding code to match style and conventions

    line 19
  3. Distinctive:

    Check if the codebase has a CLAUDE.md, README.md, or contributing guide

    line 20
  4. Distinctive:

    Follow the principle of least surprise

    line 24
  5. Distinctive:

    Keep functions small and focused (one level of abstraction per function)

    line 26
  6. Distinctive:

    Add comments only when the code cannot be made self-documenting

    line 28
  7. Distinctive:

    Verify with existing tests

    line 31
  8. Distinctive:

    If no tests exist for the affected area, add them

    line 32
  9. Distinctive:

    Run the linter and formatter if available

    line 33

“Common” is measured: kept by at least 6 in 10 of the 171 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

Implementation (Opus 级)

Workflow

Use the subagent tool with the chain parameter to execute this workflow:

  1. First, use the "scout" agent to find all code relevant to: $@
  2. Then, use the "planner" agent to create an implementation plan for "$@" using the context from the previous step
  3. Finally, use the "worker" agent to implement the plan from the previous step

Coding Standards

Before writing code

  • Read the surrounding code to match style and conventions
  • Check if the codebase has a CLAUDE.md, README.md, or contributing guide
  • Understand the existing patterns before introducing new ones

While writing code

  • Follow the principle of least surprise
  • Name things by what they are, not how they're used
  • Keep functions small and focused (one level of abstraction per function)
  • Handle errors at the boundary, not in the middle
  • Add comments only when the code cannot be made self-documenting

After writing code

  • Verify with existing tests
  • If no tests exist for the affected area, add them
  • Run the linter and formatter if available

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.

Check your setup, free