10x-bootstrapper

To scaffold a project safely, you need a validated tech-stack hand-off file. The skill reads this file, resolves the starter registry, executes the scaffold command, and handles file conflicts using .scaffold siblings to preserve existing context.

Conflict-aware file merging during project setup preserves your existing project context by generating .scaffold sibling files. This mechanism prevents overwriting local changes when the scaffold command dispatches new codebase generation into the current working directory.

To generate a starter codebase, you need a root SKILL frontmatter contract and a tech-stack hand-off file located at context/foundation/tech-stack.md or a supplied path. The scaffolding process then resolves the starter and executes the setup.

Yes, you can run codebase generation in an existing directory. The scaffold execution strategies include conflict-aware file merging, which protects your current working directory context by using .scaffold siblings instead of overwriting files directly.

Yes, project scaffolding includes post-scaffold audit handling that records a full verification log. This report documents the starter lookup, recency checks, and merge conflicts so you can inspect the setup before implementation begins.

Using a starter registry for repository setup automates command dispatch and ensures the selected ecosystem starter is current through recency checks. This approach prevents manual configuration errors and provides a documented verification log for audit purposes.