buildlisted

Explicit-invocation-only orchestrator that reads a completed `.design/<slug>/` folder and implements the code — frontend + backend — autonomously, without per-phase confirmation. All decisions were made in `/design`; this skill executes them. Invoked ONLY when the user types /build or explicitly asks to "build from the design", "implement the design", "code the feature from the brief", or "run the build pipeline". DO NOT auto-trigger from adjacent talk about writing frontend or backend code — those have their own skills. Requires a `.design/<slug>/` folder from a prior `/design` run.
muzalee/claude-atelier · ★ 0 · Web & Frontend · score 57

Install: claude install-skill muzalee/claude-atelier

This skill is the **build** orchestrator. It takes the design docs produced by `/design` and turns them into working code. Two phases, executed back-to-back without confirmation gates — the design phase was the interactive one, this phase just delivers. The three-part pipeline: - `/design` — produces docs in `.design/<slug>/`. - `/build` — this skill. Reads those docs, writes the code. - `/review` — reviews the code against the docs. ## Prerequisite `.design/<slug>/` must exist with at minimum `DESIGN_BRIEF.md`. If it doesn't, stop and tell the user to run `/design` first. This skill needs a brief, tasks, and (optionally) a backend brief + tokens spec — not a vibe. ## The Sequence ``` 1. Frontend Build → materialize tokens spec + implement frontend from TASKS.md 2. Backend Build → implement server from BACKEND_DESIGN.md ``` Skip either phase if the design didn't include it (e.g. no `BACKEND_DESIGN.md` → skip phase 2). ## Operating Rules 1. **Open with a scan, then proceed.** Auto-detect the slug: if exactly one folder exists under `.design/`, use it; if several, ask once which one. List the artifacts present in `.design/<slug>/` and state which phases will run (frontend if `TASKS.md` exists, backend if `BACKEND_DESIGN.md` exists — skip absent ones). Do not ask permission — the user asked for a build. 2. **Announce each phase as you enter it, then execute.** Format: "Phase N: [name]. Building now." No wait, no confirmation. 3. **Run each phase by reading its SKILL.