mxInitProject

To bootstrap a repository structure without overwriting content, run an idempotent initialization process that performs pre-flight checks to detect existing files and only generates missing project skeletons like CLAUDE.md and docs directories.

The best way to set up an MCP project with local fallback is to use an auto-detection mechanism that identifies MCP mode during initialization and adjusts the bootstrap steps to register the MCP project or configure the local fallback accordingly.

Yes, you can safely re-run the project initialization because it is designed to be idempotent, meaning repeated executions will only fill in missing files like CLAUDE.md and update project context without breaking or duplicating existing content.

Updating CLAUDE.md during repository bootstrapping works by creating the file if it is missing and appending or modifying content to accurately document the current project context, ensuring the repository skeleton remains aligned with the actual setup.

You should not use automated project initialization on repositories that already contain custom or complex configurations, as the bootstrap process is specifically designed for new, empty repositories or explicitly requested project setup actions.