Bring a repo into existence already conforming to the atelier standard, green from the first commit. This is the companion skill for the one moment the main standard assumes has already happened: repo birth. The raw material — the per-variant bootstrap checklists and the copyable gate assets — already exists; this skill sequences and executes it so a fresh repo passes all eight gates before a line of feature code is written.
Like grill-me, it is a focused, on-demand counterpart to the always-on atelier standard: grill-me owns the pre-decision moment, greenfield owns the repo-birth moment.
When to use
- Starting a brand-new Bun/TypeScript script repo, or a new package in a Next.js monorepo.
- The user says "scaffold / bootstrap / set up a new repo (or package) to the standard".
- An empty or near-empty directory that should become a conforming repo.
Greenfield only. For a repo that already has code, the main atelier skill applies — do not run this over a populated tree; it scaffolds and would collide. Match intensity to the ask: a throwaway spike does not need the full eight-gate machinery — say so and offer the minimal subset.
How to run
- Confirm variant and target directory — one question, with a recommendation. Read the shape from the directory: a
packages/*workspace withnext.config.tsnearby → Next.js package; otherwise → Bun-script. State your read and confirm before touching anything. - Locate the atelier assets. The gate scripts and helpers live in the installed
atelierskill'sassets/directory (typically~/.claude/skills/atelier/assets/). Resolve that path and report it. If it is missing, stop and tell the user to install theatelierskill first — greenfield copies from it, it does not vendor its own copies. - Follow the matching bootstrap checklist verbatim. Read and execute the numbered checklist for the variant — do not improvise the config:
- Bun-script → the installed
atelierskill'sreferences/bun-typescript.md(§ Bootstrap checklist): layout,tsconfig, flat ESLint config,Result+ Logger port/adapter/fake, asset copy, coverage gate, Stryker, the two git hooks,bunfig.toml. - Next.js → the installed
atelierskill'sreferences/nextjs-monorepo.md(§ Bootstrap checklist): package layout,tsconfig/eslint/postcss/next.config,simple-git-hooks,globals.css, thesrc/components/{atoms,molecules,organisms}+src/page+src/lib+src/configtree. Never install both hook mechanisms — eight-gate.githooksfor Bun-script,simple-git-hooksfor Next.js.
- Bun-script → the installed
- Pin versions properly. Add every dependency with
bun add/bun add -dso it resolves to a concrete^X.Y.Z; never hand-write"latest"or"*"(rule 19 — gate 2 would reject it). - Seed session memory. Create
.claude/LESSONS.mdwith just its header so the cross-session journal works from commit one. Offer/initfor aCLAUDE.mdrather than writing one here. - Lay a minimal walking skeleton. The thinnest end-to-end slice that touches every layer (see the installed
atelierskill'sreferences/architecture.md§ The walking skeleton): for a Bun-script repo, one use-case returningResult.okthrough its primary port, its branded input, and its confirmed test (rule 24 — propose the test, get the yes, then write it); for Next.js, onesrc/libpure function with a test wired into a page shell that renders a single atom. This is not speculative code — it is what makes coverage and mutation pass for real and demonstrates the TDD loop in place. Keep it to the absolute minimum, and offer to skip it for a bare scaffold. - Prove green. Run the inner loop and confirm each is clean —
bun test,bun run lint,bun run typecheck,bun run coverage, and for the Bun-script variantbun run mutate. Confirm thecommit-msghook rejects a junk message. A bootstrap that does not end green has not finished. - Stop before the first commit. Stage the tree, propose the Conventional-Commits message (
chore: scaffold repoor similar), and wait for the user's explicit yes (rule 25). Never auto-commit.
Output
A directory that passes every gate, with a one-screen summary: variant chosen, assets copied (and from where), hooks wired, scripts added, the walking skeleton's single scenario, the inner-loop results, and the proposed first-commit message awaiting confirmation.
Scaffold the simplest conforming repo that runs green — the walking skeleton is one slice, not a feature. Everything past it is built later, test-first, under the main atelier standard. Out of scope here: brownfield adoption of an existing repo, CI/CD, deployment, Docker, and choosing a web framework.