setup-stack

/setup-stack: adapt the template to a stack

This template is stack-agnostic on purpose: the agentic loop only needs the command contract in CLAUDE.md (check / test / build / run / smoke). This skill makes those commands real, and sets the codebase up so agents can properly test the application. That is the template's core design goal.

1. Choose

Establish the stack with the user (language/framework, package manager, test runner) unless they already said. Offer sensible bundles (e.g. "TypeScript + Vite + Vitest", "Python + uv + pytest", "Go + std tooling") but accept anything.

2. Scaffold minimally

Use the stack's official initializer where one exists, scaffolding into the repo's fixed monorepo layout (see CLAUDE.md): the first app in apps/<name>, shared code in packages/<name>, even for a single app. Wire up the stack's workspace tooling when it has one (pnpm workspaces, cargo workspaces, uv workspaces, Nx, moon, ...); a plain directory layout is fine when it doesn't. Keep it minimal: the loop needs something to lint, test, build, and run, not a demo app. Include at least one real passing test, so the contract's test command is meaningful from day one. Extend .gitignore for the stack.

3. Make the app agent-testable

The part most templates skip. Agents must be able to verify behavior, not just that code compiles:

• Run: the app starts with one command, on a stable port/URL (or deterministic CLI entrypoint), with seeded deterministic data. No interactive prompts, no manual setup steps.
• Smoke: one command drives the running app through its critical user journeys (HTTP calls against real endpoints, CLI invocations checking real output, or a headless-browser check for UIs) and exits non-zero on failure. Today that is one journey, because the app has one; it grows with the app.

Both must be reliable enough that red means "the app is broken", never "the harness is flaky".

4. Fill the command contract

Replace every TODO in CLAUDE.md's command-contract section with real commands. Wire check/test/build into the gates job of .github/workflows/ci.yml, above the generated-file drift step that ends that job, and smoke into its smoke job; as a PR gate rather than a per-round command, smoke can afford to be slower, as long as it stays reliable. The drift step assumes a hermetic build, so confirm it passes on a clean tree: anything the contract rewrites on every run belongs in .gitignore, or the command needs fixing. Also add the stack's package ecosystem to .github/dependabot.yml if it introduces one that isn't covered (npm is already active for the repo's toolchain; keep updates grouped). Then verify each contract entry by running it; a command that hasn't run green doesn't go in. Keep check/test/build fast and deterministic: they gate every inner-loop round.