agentleFS
Sign inStart free
wheslleyrimarwheslleyrimar/BuildCLI-Agents/.claude/skills/forge/SKILL.md

forge

Skill3 starsChanged 11 days agoMITView on GitHub

Create or refresh a project-specific skill built from this repository's real patterns. Saves to .claude/skills/<name>/SKILL.md.

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 66 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Write a SKILL.md that captures what is true about *this* codebase and nothing that a competent engineer already knows.

    line 17
  2. Very specific:

    Check whether .claude/skills/<name>/SKILL.md already exists:

    line 26
  3. Distinctive:

    If the skill is not already listed in CLAUDE.md, add it.

    line 40
  4. Distinctive:

    Every line must be specific to this project.

    line 50
  5. Distinctive:

    Keep it under roughly 400 words.

    line 52

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

Forge

Arguments

Skill name, optionally followed by a band (service|interface|store|verify|delivery|custom). Example: "payments service" or "shadcn-ui interface".

Output

.claude/skills/<name>/SKILL.md.

Goal

Write a SKILL.md that captures what is true about this codebase and nothing that a competent engineer already knows. The test: an agent should be able to act on it without reopening the full project context.

Steps

  1. Parse the skill name and band from the arguments.
    • Examples: payments service, shadcn-ui interface, auth-flow service, checkout-e2e verify
    • Band omitted → infer it from the name, or ask.
  2. Check whether .claude/skills/<name>/SKILL.md already exists:
    • Exists → read it, compare against the current context, refresh whatever went stale.
    • New → start from the structure in _shared/templates/skill-template.md.
  3. Load the band: .buildcli/runtime/bcx band <band>.
  4. Open two or three representative source files in that band and extract the patterns that are actually in use: naming, error handling, auth guards, test layout, module boundaries.
  5. Write the skill:
    • Purpose — one sentence, tied to how this project uses the band
    • When to use — 3 to 5 concrete triggers, none of them generic
    • Context loading — the exact band to read
    • Workflow — steps that name real paths, modules, and patterns from step 4
    • Constraints — drawn from the engineering standards and the band
    • Example — one input/output pair that could plausibly come from this codebase
  6. Save to .claude/skills/<name>/SKILL.md.
  7. If the skill is not already listed in CLAUDE.md, add it.

Output

  • Path written
  • The project-specific patterns the skill now encodes
  • Anything left as NEEDS CLARIFICATION for want of evidence

Rules

  • Every line must be specific to this project. Delete any sentence that would survive a copy-paste into another repo.
  • [band:<band>] empty or full of NEEDS CLARIFICATION → run survey first and say so.
  • Keep it under roughly 400 words.
  • One concern per skill. Never fold two bands into one file.
  • Skills outside the five standard bands are fine — just name them unambiguously.

Download now (ZIP)

  • Other versions77 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 77

    1. cwinvestments/memstack★ 425same name
    2. ansari-project/codev★ 296same name
    3. cluesmith/codev★ 296same name
    4. swyxio/skills★ 189same name
    5. simota/agent-skills★ 96same name
    6. alp82/forge★ 36same name
    7. TT-Wang/forge★ 34same name
    8. emiliosheinz/agent-skills★ 20same name
    9. MetalLegBob/solana-vibes-kit★ 19same name
    10. kecoma1/MQL5-SKILLS★ 17same name

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

  • Used alongsideProjects with it also use forge-review, forge-ship and 8 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.
    • tonmoy007Skill

      forge-review

      Run a multi-dimensional parallel code review over the current change.

      Also in 7 projects that use this

    • redteamlifeSkill

      forge-ship

      Use when the user asks to merge, release, promote, reconcile, or close out work in a repo containing `docs/forge/` or governed by FORGE. Not for per-task commits; those complete inside forge-execute-task.

      Also in 5 projects that use this

    • DailenGSkill

      forge-design

      Design, UX, and polish discipline for the forge lifecycle. Covers the design tier, the design brief in docs/DESIGN.md, UX requirements and their verification methods, the per-slice design pass, the UX defect register, and the release polish pass. Load whenever work touches a user-facing surface (GUI, terminal, library API, or operated service), whenever a UX observation needs disposing of, and whenever a release is in reach.

      Also in 3 projects that use this

    • weselbenSkill

      forge-docs

      Load before code changes, before writing docs or an ADR, when a user question exposes a missing how-to, and when closing a chunk of work; also loaded by forge after each squash-merge and by deep-research after a report.

      Also in 3 projects that use this

    • DshamirSkill

      forge-plan

      Takes analysis.json + budget cap → derives the full phase sequence, hyperparameters, instance type, cost estimate, and acceptance thresholds. Emits plan.md (the single human gate document) and plan.json (the machine-readable spec that dispatch-v2 consumes). Refuses to plan if estimated cost exceeds budget×1.2.

      Also in 3 projects that use this

    • TT-WangSkill

      forge-status

      Show current forge project status, plan, and iteration history

      Also in 3 projects that use this

  • In this repository19 other files it gives its agents.

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