10x-bootstrapper

Project scaffolding from a selected tech stack reads your tech-stack.md hand-off file, resolves a starter from a registry, and executes the starter CLI directly in your current working directory to generate a ready-to-run application.

When scaffolding encounters existing files, a strict conflict policy applies to protect your current files. The tool supports strategies like scaffolding in a temp directory then merging or cloning with history removed to preserve existing content safely.

Yes, you need a context/foundation/tech-stack.md file containing the tech stack hand-off. This file is a required prerequisite that provides the starter_id needed to resolve the correct CLI template for bootstrapping your project.

Yes, an optional post-scaffold security audit can run immediately after project bootstrapping. It performs checks on the newly generated scaffold and writes an auditable verification log to the bootstrap-verification directory.

Project scaffolding supports both JavaScript and non-JS ecosystems for repeatable bootstrapping. It resolves the appropriate starter CLI invocation and handles monorepo directory merge strategies while preserving your context files.

Bootstrap fails when the tech-stack.md hand-off file is missing or lacks a valid starter_id. The scaffolding process requires this identifier to look up the corresponding cmd_template and working directory strategy in the starter registry.