What problem does it solve? Turning a chosen tech stack into an actual scaffolded codebase is error-prone: starter CLIs vary in how they write into a directory, existing files can be clobbered, and there is no audit trail of what happened. This Skill consumes a written tech-stack hand-off and scaffolds the project into the current working directory with a strict conflict policy and a verification log. ## Core Features & Use Cases - Hand-off-driven scaffolding: Reads context/foundation/tech-stack.md, resolves the starter card from the tech-stack-selector registry by starter_id, and refuses cleanly if the hand-off or registry entry is missing. - Three cwd strategies with a strict conflict matrix: Supports subdir-then-move, native-cwd, and git-clone strategies; existing files become .scaffold siblings, context/ is always preserved, and .gitignore is append-merged. - Pre- and post-scaffold verification: Checks starter recency via npm and GitHub signals, then runs the ecosystem's audit tool (npm audit, pip-audit, cargo audit, govulncheck, etc.) with severity tiering, writing everything to context/changes/bootstrap-verification/verification.md. - Use Case: After running /10x-tech-stack-selector to pick Next.js as your stack, invoke this Skill to run create-next-app, merge the output safely into your project directory, and receive a verification log with dependency audit findings. ## Quick Start Say "bootstrap the project" after your tech-stack hand-off file exists at context/foundation/tech-stack.md.
