What problem does it solve? After picking a tech stack, developers still face the fiddly work of running the right starter CLI, merging scaffold output into an existing directory without clobbering files, and checking whether the starter and its dependencies are stale or vulnerable. This Skill automates that entire bootstrap sequence with a strict conflict policy and an audit trail. ## Core Features & Use Cases - Hand-off-driven scaffolding: Reads context/foundation/tech-stack.md written by /10x-tech-stack-selector, resolves the starter card from the registry, and refuses cleanly when the hand-off is missing or the starter_id is unknown. - Three cwd strategies with conflict protection: Dispatches to subdir-then-move, native-cwd, or git-clone strategies; existing files become .scaffold siblings, context/ is never overwritten, and .gitignore is append-merged. - Two verification slots: A pre-scaffold recency check (npm publish date, GitHub pushed_at) and a post-scaffold dependency audit (npm audit, pip-audit, cargo audit, etc.) with severity tiering, all written to context/changes/bootstrap-verification/verification.md. - Use Case: After running /10x-tech-stack-selector to choose Next.js, invoke this Skill to scaffold the app into your current directory, learn that the starter was last published two weeks ago, and get a dependency audit summary — all logged for later review. ## Quick Start Run /10x-bootstrapper after /10x-tech-stack-selector has written context/foundation/tech-stack.md to scaffold the chosen starter into your current directory.
