← ClaudeAtlas

build-looplisted

Drive a build to actually-works, near-finish-line craft by looping build → see → exercise → check → critique → rebuild over the agent's existing tools (bash build/test, headless screenshot + vision, Playwright, axe/Lighthouse) until acceptance criteria pass or an explicit stop-condition fires — no infinite thrash. ALWAYS invoke when the user says any of "tighten this build", "iterate until it passes", "self-verify the UI", "make it actually work, not just compile", "loop until the core flows pass", or "drive this to near-finish-line". Also invoke proactively after a scaffold or feature lands and before handing a draft to a human. Composition-first over existing tools, not a new program; it states its own honest bounds — objective craft only, taste self-graded, ~80% ceiling, market validation out of scope. Do NOT use to decide WHAT to build (that's ideate) or whether a design/strategy is sound (deep-dive).
nelsonwerd/idea-to-ship-skills · ★ 83 · AI & Automation · score 80
Install: claude install-skill nelsonwerd/idea-to-ship-skills
# Build-Loop — see-and-exercise iteration until a build actually works `build-loop` takes a build that compiles-but-isn't-done and drives it toward **near-finish-line craft** by repeating one disciplined cycle — **build → see → exercise → check → critique → rebuild** — until its acceptance criteria pass or a stop-condition fires. It doesn't just re-read its own plan; it *runs, sees, and exercises what it built*, then feeds those observations back into the next rebuild. It is **composition-first**: it orchestrates tools the agent already has — `bash` (build/test), a headless screenshot + vision to *see*, Playwright/headless to *exercise* the flows, `axe`/Lighthouse to *check* — via prose. It is **not** a new program, and not a reinvention of the see-and-exercise agents vendors already ship; it's the discipline that wraps them: a target, a loop, a stop-condition, and an honest ledger of what was actually checked. This skill is the downstream partner to `prompt-pack` (which sequences *what* to build) and `ideate` (which decides *whether* to build it). It carries `prompt-pack`'s execute-discipline (**never fake a signal you didn't run**) and `ideate`'s conditional-design (**a design bar only when feel is load-bearing**). ## When to use this **Strong triggers — invoke without asking:** - "Tighten this build" / "drive it to near-finish-line" / "make it actually work, not just compile" - "Iterate until it passes" / "loop until the core flows pass" - "Self-verify the UI" / "see