project-init

To set up a Claude project, you provide the project path and the scaffolding generates CLAUDE.md, SPEC.md, tasks.md, and a base .claude/settings.json tailored to your project. This creates a consistent filing cabinet without overwriting existing data.

Yes, the project scaffolding is state-aware and detects whether the project is new or existing. It reads the current project state, asks for minimal input, and writes only the missing files like CLAUDE.md and SPEC.md without overwriting existing configurations.

The best way to bootstrap a Claude environment is using an automated scaffolding process that prepares a structured project layout. It generates the necessary governance files, allowing teams to begin coding immediately with a solid foundation.

No, bootstrapping a Claude project does not overwrite existing settings.json files. The setup process is designed to read the project state and write only what is missing, ensuring your current data and configurations remain intact.

You need CLAUDE.md, SPEC.md, tasks.md, and a base .claude/settings.json to start coding with Claude governance. These files form a minimal, consistent filing cabinet that guides project setup and structure scaffolding.

You need SPEC.md and tasks.md for Claude project onboarding because they provide a solid governance scaffold. SPEC.md defines project specifications while tasks.md tracks progress, streamlining the onboarding process so teams can start coding immediately.