bootspring init

Initialize Bootspring in your project.

Synopsis#

bootspring init [options]

Description#

The init command sets up Bootspring in your project by:

  1. Creating bootspring.config.js with detected settings
  2. Generating CLAUDE.md context file
  3. Creating .mcp.json for MCP server configuration
  4. Setting up recommended defaults

Options#

OptionDescription
--force, -fOverwrite existing configuration
--stack <items>Specify tech stack (comma-separated)
--skip-generateSkip CLAUDE.md generation
--minimalCreate minimal configuration
--yes, -yAccept all defaults

Usage Examples#

Basic Initialization#

bootspring init

Interactive prompts guide you through setup:

? Project name: my-awesome-app ? Project type: SaaS Application ? Detected stack: Next.js, TypeScript, Prisma, Tailwind ? Is this correct? Yes ✓ Created bootspring.config.js ✓ Created .mcp.json ✓ Generated CLAUDE.md ✓ Bootspring initialized successfully!

Non-Interactive#

bootspring init --yes

Uses detected defaults without prompts.

Specify Stack#

bootspring init --stack nextjs,prisma,clerk,stripe

Explicitly set technologies instead of auto-detection.

Force Overwrite#

bootspring init --force

Overwrites existing configuration files.

Minimal Setup#

bootspring init --minimal

Creates only essential files without extras.

Generated Files#

bootspring.config.js#

1module.exports = { 2 project: { 3 name: 'my-awesome-app', 4 type: 'saas', 5 description: 'Auto-detected from package.json', 6 }, 7 8 stack: { 9 frontend: ['react', 'nextjs', 'tailwindcss'], 10 backend: ['nodejs'], 11 database: ['postgresql', 'prisma'], 12 auth: ['clerk'], 13 payments: ['stripe'], 14 testing: ['vitest', 'playwright'], 15 }, 16 17 agents: { 18 enabled: 'all', // or array of specific agents 19 }, 20 21 quality: { 22 preCommit: { 23 lint: true, 24 format: true, 25 types: true, 26 }, 27 prePush: { 28 tests: true, 29 coverage: 80, 30 }, 31 }, 32 33 paths: { 34 context: 'CLAUDE.md', 35 todo: 'todo.md', 36 prd: 'tasks/prd.json', 37 }, 38};

.mcp.json#

1{ 2 "mcpServers": { 3 "bootspring": { 4 "command": "npx", 5 "args": ["bootspring", "mcp"], 6 "env": { 7 "BOOTSPRING_API_KEY": "${BOOTSPRING_API_KEY}" 8 } 9 } 10 } 11}

CLAUDE.md#

Auto-generated project context file. See Context Generation.

Stack Detection#

Bootspring automatically detects your tech stack by scanning:

FileDetection
next.config.*Next.js
vite.config.*Vite
prisma/schema.prismaPrisma
drizzle.config.*Drizzle
package.json (deps)Various packages
tsconfig.jsonTypeScript
tailwind.config.*Tailwind CSS
vitest.config.*Vitest
playwright.config.*Playwright

Post-Initialization#

After initialization:

  1. Add API Key (if using Pro features):

    export BOOTSPRING_API_KEY=bsk_your_key
  2. Start Development:

    bootspring status # Check everything is set up bootspring agent list # See available agents
  3. Customize Config: Edit bootspring.config.js to customize behavior.

Common Issues#

Existing Config#

Error: bootspring.config.js already exists Use --force to overwrite

Solution: Use --force to overwrite or delete the existing file.

Not a Project Root#

Warning: No package.json found

Solution: Run from your project root directory.

Detection Incorrect#

If stack detection is wrong, use --stack to specify:

bootspring init --stack nextjs,prisma,clerk