agentleFS
joris887joris887/exosuit/.claude/skills/build/SKILL.md

build

Skill9 starsChanged 3 months agoMITView on GitHub

Build a project from a plain-English description. Handles all technical decisions automatically. Designed for non-technical users but useful for anyone who wants fast results.

168 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use backprop, finances 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.
  • JuliusBrusseeSkill

    backprop

    Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.

    Also in 4 projects that use this

  • GerardoRdz96Skill

    finances

    Use when Gera talks about his money — logging an expense ("I spent X on Y"), checking where he stands this pay-period, closing a period, planning debt payoff, onboarding his financial picture, or asking for budgeting/finance opinions. Servy's financial brain. Triggers — "I spent", "log this expense", "where am I this period", "close the period", "how's my budget", "debt plan", "should I pay off", "finances onboard", "/finances".

    Also in 3 projects that use this

  • cpiprintSkill

    favicon

    Generate favicons from a source image

    Also in 3 projects that use this

  • madeehahassanSkill

    Go-Live

    Pre-launch checklist. Use before making any app public, sharing a link externally, or announcing a product launch. Adapts to Claude Code, claude.ai, and Cowork.

    Also in 3 projects that use this

  • JuliusBrusseeSkill

    deepen

    Optional design-improvement pass for when you have spare usage to drain. Finds the shallowest modules in the code the spec touches, researches a deeper design, and proposes refactors that shrink interfaces and hide decisions — behavior held constant, tests green before and after. Proposes §I/§V/§T edits, never silent rewrites. Triggers when the user says "deepen this", "improve the design", "this module feels shallow", "pull complexity down", "use spare budget on the codebase", or invokes /ck:deepen. Leans on the codebase-design skill's deep-module vocabulary when present.

    Also in 3 projects that use this

  • synaptiaiSkill

    gate

    Create a BDSK review_gate artifact. Defines a checkpoint that controls whether generated output may proceed toward acceptance. Use when defining quality, security, or scope gates for execution plans.

    Also in 5 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. 0 are common, 14 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 154 edited versions we read keep these.

  • 14

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask: "What would you like me to build?

    line 28
  2. Distinctive:

    Wait for response before proceeding.

    line 29
  3. Distinctive:

    Run a silent minimal bootstrap:

    line 35
  4. Very specific:

    Read the current profile from CLAUDE.md.

    line 46
  5. Distinctive:

    Do NOT surface any of this to the user: No story types, no SPIDR, no priority labels, no methodology terminology.

    line 58
  6. Distinctive:

    Create a simple internal plan (not shown to user):

    line 60
  7. Distinctive:

    Use language the user would understand.

    line 94
  8. Distinctive:

    Commit with conventional format (don't explain commit conventions)

    line 100
  9. Distinctive:

    Only stop for genuine product ambiguity: "The design could go two ways: [A] or [B].

    line 106
  10. Distinctive:

    Never stop for: database choice, API style, file naming, test framework, folder structure

    line 107
  11. Distinctive:

    If a step fails after 2 attempts, skip it with a note: "I couldn't get [X] working automatically.

    line 110
  12. Very specific:

    Check CLAUDE.md Commands for a dev: command.

    line 117
  13. Very specific:

    Run the dev command in background using Bash with run_in_background: true

    line 120
  14. Distinctive:

    Wait a few seconds. Read any output — look for URLs, ports, file paths, or status messages.

    line 121
  15. Distinctive:

    Ask: "Take a look and tell me what you think!"

    line 123
  16. Distinctive:

    Wait for feedback. Positive → proceed to completion report.

    line 124
  17. Very specific:

    If no dev command is configured (libraries, packages, pipelines, etc.) → skip this step.

    line 126
  18. Distinctive:

    Do NOT assume localhost or any specific URL: Read the actual command output.

    line 128

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

build

Build a project from a natural-language description. Orchestrates setup, planning, and implementation automatically.

All user-facing output MUST use plain English. No jargon: no "TDD", "sprint", "PR", "squash merge", "CI/CD", "ORM", "middleware". If a technical term is unavoidable, explain it in parentheses.

Arguments

$ARGUMENTS — a plain-English description of what to build (e.g., "a task management app with user accounts and due dates").

<IF condition="$ARGUMENTS is empty"> Ask: "What would you like me to build? Describe it in your own words — as much or as little detail as you like." Wait for response before proceeding. </IF>

Phase 0: Check Setup

<IF condition="CLAUDE.md has placeholder commands (contains '<test command>' or '<lint command>')"> Run a silent minimal bootstrap: 1. Detect stack (languages, package manager, test framework, formatter, linter) 2. Configure CLAUDE.md commands 3. Set profile to **lean** (unless already set) 4. Skip: architecture docs, coding standards, ground rules, readiness report, foundation backlog 5. Show: "Setting up the project..." (nothing more) </IF> <ELSE> Show: "Project already set up. Starting build..." </ELSE>

Read the current profile from CLAUDE.md. If not lean, note the profile but proceed — /build always uses lean-style execution internally regardless of project profile.

Phase 1: Decompose

Show: "Planning what needs to be built..."

Internally decompose the description into ordered stories using /ideate logic:

  1. Identify the core entities and features described
  2. Break into dependency-ordered implementation steps
  3. Classify each as feature, infrastructure, or testing
  4. Size each step by conceptual cohesion (canonical policy: .claude/skills/ideate/references/story-template.md) — one coherent, independently verifiable unit per step; file count informs judgement but is never a threshold

Do NOT surface any of this to the user. No story types, no SPIDR, no priority labels, no methodology terminology. Keep the decomposition internal.

Create a simple internal plan (not shown to user):

steps:
  - summary: "Set up the database tables"
    type: infrastructure
    files: [...]
  - summary: "Build the API endpoints"
    type: feature
    files: [...]
  - summary: "Add user authentication"
    type: feature
    files: [...]
  - summary: "Write tests"
    type: testing
    files: [...]

Discovery Capture (Retroactive)

Silently capture discovery context for future phase reviews — the user does NOT see this:

  1. Infer archetype from description (classify against the 10 archetypes in .claude/skills/discover/references/scale-guide.md)
  2. Set scale to Quick Build
  3. Auto-generate a minimal docs/reference/DECISION_LOG.md (copy template from .claude/skills/discover/assets/decision-log.md), logging all technical decisions with confidence: ASSUMED
  4. Include Phase Transition Stories (E0N-REVIEW: 3-story quick variant — E0N-001, E0N-004, E0N-006) as the last internal step
  5. Save classification to vision/classification.md

This ensures /build users get the review cycle without upfront friction.

Phase 2: Execute

For each step in dependency order:

  1. Show progress in plain English:
    • "Setting up the database..." / "Building the API..." / "Adding user login..." / "Writing tests to make sure everything works..."
    • Use language the user would understand. Never: "Executing story E01-003 (type: feature, size: STANDARD)"
  2. Execute using story-cycle Lean behavior:
    • Plan (lightweight — no confidence scoring)
    • Build with TDD where non-trivial (run tests, don't explain TDD methodology)
    • Verify tests pass
    • Commit with conventional format (don't explain commit conventions)
  3. Make all technical decisions silently:
    • Framework/library choices: pick the best fit, document in a final summary
    • Architecture: follow standard patterns for the detected stack
    • File structure: follow existing project conventions or detected stack defaults
    • Only stop for genuine product ambiguity: "The design could go two ways: [A] or [B]. Which do you prefer?"
    • Never stop for: database choice, API style, file naming, test framework, folder structure
  4. Handle failures gracefully:
    • If a step fails after 2 attempts, skip it with a note: "I couldn't get [X] working automatically. Here's what needs to be done manually: [description]"
    • Continue with remaining steps — don't block the entire build

Phase 3: Complete

3A. Launch & Verify (if applicable)

Check CLAUDE.md Commands for a dev: command. If one is configured:

  1. Show: "Starting your project..."
  2. Run the dev command in background using Bash with run_in_background: true
  3. Wait a few seconds. Read any output — look for URLs, ports, file paths, or status messages.
  4. Show whatever the command produces. If it outputs a URL, highlight it. If it's a CLI, show the help output. If it starts a server, show the address.
  5. Ask: "Take a look and tell me what you think!"
  6. Wait for feedback. Positive → proceed to completion report. Issues → fix and re-run.

If no dev command is configured (libraries, packages, pipelines, etc.) → skip this step. Tests already verified the build.

Do NOT assume localhost or any specific URL. Read the actual command output. Different projects produce different results.

3B. Completion Report

Show a completion report in plain English:

## All Done!

### What Was Built
- [Feature 1]: [plain-English description of what it does]
- [Feature 2]: [description]
- ...

### Files Created/Modified
- `src/models/user.ts` — User data model
- `src/api/auth.ts` — Login and registration endpoints
- ...

### Tests
- [N] tests written, all passing

### Technical Decisions Made
- **Database:** PostgreSQL (reliable, free, works well with [framework])
- **Auth:** [chosen approach] — [one-line reason]
- ...

### Try It
[If dev command ran: "Your project is running — see above"]
[If dev command exists but didn't launch: "Run `[dev command]` to start"]
[If no dev command: omit this section]

### Next Steps
- [Suggestion 1, e.g., "Add a payment system with /build 'Stripe payment integration'"]
- [Suggestion 2]

Rules

  • Plain English only — every user-facing message must be understandable by someone who has never coded
  • Silent technical decisions — pick good defaults, document them in the completion report, never ask
  • Stop only for product questions — "Should users be able to delete their account?" is valid. "REST or GraphQL?" is not.
  • Safety hooks still run — secrets detection, git protection, and test execution happen invisibly
  • Lean execution — no quality agent dispatch, no sprint specs, no retrospectives, no documentation generation beyond what's needed to work
  • Skip gracefully — failed steps are noted, not fatal. The build continues.
  • One session — the first version of /build completes in a single session. Multi-session builds are future work.

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.