agentleFS
Sign inStart free
jvalin17jvalin17/agent-toolkit/skills/implementation/SKILL.md

implementation

Skill2 starsChanged 31 days agoApache-2.0View on GitHub

Build features with TDD. Skeleton first, then feature slabs. Fix, refactor, demo modes. Keywords: implement, build, code, TDD, skeleton, slab, fix, debug, refactor, demo

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use bug-fix, investigate and 4 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.
  • u9401066Skill

    bug-fix

    Structured bug fixing workflow with root cause analysis and regression prevention. Triggers: BF, 修 bug, fix bug, debug, 除錯, 錯誤, error, 問題, issue, 修復, fix, 故障, fault, 異常, exception, 失敗, failure, 不能用, broken, 壞掉.

    Also in 3 projects that use this

  • VercelSkill

    investigate

    Investigate an issue report, or analyze the constraints of a proposed change, with strict, evidence-driven diagnosis.

    Also in 3 projects that use this

  • MicrosoftSkill

    playwright-cli

    Automate browser interactions, test web pages and work with Playwright tests.

    Also in 4 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

  • MicrosoftSkill

    release

    Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).

    Also in 4 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 3

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

    Test first → implement → verify.

    line 28
  2. Very specific:

    Before commit → /precommit (or get_skill("precommit") + gates).

    line 29
  3. Distinctive:

    Never claim done without evidence.

    line 30
  4. Distinctive:

    Follow ORCHESTRATION PLAN in context if present (includes HOST + PULL POLICY).

    line 43

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

You are an Implementation Agent. Short default path — pull modules for depth.

Topic / slug: from user argument (lowercase, hyphens).

Modes (detect — don't ask)

SignalMode
fix / debug / brokenFix → failing test → fix → verify
refactorRefactor → impact analysis → tests → change → tests
demo / mock dataDemo
greenfieldBuild → skeleton → slabs
trivial 1–2 filesDirect → TDD for logic
else existing appFeature → slabs

Default path

  1. Prerequisites: requirements/<slug>.md + architecture/<slug>.md (or tell user to run those skills).
  2. Execution plan for non-trivial work → save it to .scratch/execution-plan.json (schema in get_module("implementation", "workflow") step 0d; precommit finalize blocks without it) → wait for approval.
  3. run_function("check_tdd_order") before source edits when unsure.
  4. Test first → implement → verify.
  5. Before commit → /precommit (or get_skill("precommit") + gates).
  6. Never claim done without evidence; UI needs user try-local.

Pull map

WhenPull
Writing tests / logicget_module("implementation", "tdd")
Full slab cycle, skeleton, reportingget_module("implementation", "workflow")
Frontend UIfrontend.md (skill subfile)
Language standardsreferences/coding-standards-index.md
Auto modeshared/orchestrator.md
Guardrail detailshared/guardrails-quick.md

Follow ORCHESTRATION PLAN in context if present (includes HOST + PULL POLICY).

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.

Reviews can't be read right now.

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