What problem does it solve? Turning a chosen tech stack into an actual scaffolded codebase is error-prone: starter CLIs overwrite existing files, registries drift, and nobody records what happened. This Skill consumes a written tech-stack hand-off and scaffolds the project into the current directory with a strict conflict policy and a full 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, and refuses cleanly when the hand-off is missing or the starter is unknown. - Conflict-safe merge: 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, runs the ecosystem audit tool (npm audit, pip-audit, cargo audit, etc.), and writes a structured verification.md audit trail. - Use Case: After running /10x-tech-stack-selector to pick the 10x-astro-starter, invoke this Skill to clone the starter, strip its git history, merge files into your project directory without touching context/, and receive a verification log with audit findings. ## Quick Start Say "bootstrap the project" after your tech-stack hand-off exists at context/foundation/tech-stack.md.
