What problem does it solve? Turning a chosen tech stack into a working project scaffold is error-prone: starter CLIs differ in how they handle the current directory, existing files can be clobbered, and there is no audit trail of what was run. 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 runs the starter's cmd_template with the correct cwd strategy (subdir-then-move, native-cwd, or git-clone). - Strict conflict policy: Existing files become .scaffold siblings, context/ is never overwritten, and .gitignore is append-merged, so re-runs never destroy user work. - Verification and audit trail: Runs pre-scaffold recency checks (npm/GitHub), post-scaffold dependency audits (npm audit, pip-audit, cargo audit, govulncheck, etc.), and writes a structured verification.md log. - Use Case: After running /10x-tech-stack-selector to pick Next.js, invoke this Skill to scaffold the app into your project directory, get warned about stale starters or CRITICAL vulnerabilities, and receive a full audit log of the run. ## Quick Start Run /10x-bootstrapper after /10x-tech-stack-selector has written context/foundation/tech-stack.md to scaffold the chosen starter into the current directory.
