MCPInstall

ln-700-project-bootstrap

Bootstraps projects to production-ready structure. Use when creating new or transforming existing projects.

Installs
384
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-700-project-bootstrap
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads ln-700-project-bootstrap automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Paths: File paths (references/, ../ln-*) are relative to this skill directory.

ln-700-project-bootstrap

Type: L1 Top Orchestrator Category: 7XX Project Bootstrap

Universal project bootstrapper with two modes: CREATE (generate production-ready project from scratch) or TRANSFORM (migrate existing prototype from any platform to production structure). Output: Clean Architecture, Docker, CI/CD, quality tooling.


Mode Selection

AspectCREATETRANSFORM
InputEmpty directory or target stack configExisting project (Replit, StackBlitz, CodeSandbox, Glitch, custom)
DetectionNo source files foundSource files + optional platform config detected
ln-820SKIP (no deps to upgrade)RUN (upgrade existing deps)
ln-720SCAFFOLD + GENERATERESTRUCTURE + MIGRATE
ln-724SKIP (no artifacts)CONDITIONAL (if platform detected)
ln-730–780RUN (same for both modes)RUN (same for both modes)

Overview

AspectDetails
InputEmpty directory (CREATE) or source project (TRANSFORM)
OutputProduction-ready project with all infrastructure
Delegationsln-820 (conditional) -> ln-720 -> ln-730 -> ln-740 -> ln-760 -> ln-770 -> ln-780

Workflow

Phase 0: Analyze (Tech Detection)
    |
    v
Phase 1: Plan (Generate Transformation Plan)
    |
    v
Phase 2: Confirm (User Approval)
    |
    v
Phase 3: Execute (Delegate to L2 Coordinators)
    |
    +---> ln-820: Dependency Upgrader
    +---> ln-720: Structure Migrator
    +---> ln-730: DevOps Setup
    +---> ln-740: Quality Setup
    +---> ln-760: Security Setup
    +---> ln-770: Crosscutting Setup
    +---> ln-780: Bootstrap Verifier
    |
    v
Phase 4: Report (Summary of Changes)

Phase 0: Technology Detection

Step 0.0: Mode Detection

ConditionModeAction
Empty directory (no source files)CREATEAsk user for target stack, project name, entities
Source files foundTRANSFORMAuto-detect stack, scan for platform artifacts
Ambiguous (few files, unclear)ASKPresent both options, let user choose

Step 0.1: CREATE Mode — User Input

ParameterRequiredDefaultExample
Project nameYes—MyApp
Target backendYes—.NET / Node.js / Python
Target frontendYes—React / Vue / Angular / Svelte
DatabaseYes—PostgreSQL / MongoDB / MySQL
Main entitiesNoUser, Role (starter)User, Product, Order

Step 0.2: Idempotency Pre-flight

If target directory contains existing files:

  1. Detect existing structure (package.json, .csproj, etc.)
  2. Warn user: "Target directory is not empty. Existing files may be overwritten."
  3. Ask: Overwrite (replace all) / Merge (keep existing, add missing) / Abort

Step 0.3: Technology Detection (TRANSFORM mode) / Stack Config (CREATE mode)

Analyze project to detect tech stack before delegations.

Detection Rules

Frontend:
  React:
    - package.json contains "react"
    - Files: *.tsx, *.jsx with React imports
  Vue:
    - package.json contains "vue"
    - Files: *.vue
  Angular:
    - package.json contains "@angular/core"
    - Files: *.component.ts
  Svelte:
    - package.json contains "svelte"
    - Files: *.svelte

Backend:
  .NET:
    - *.csproj files exist
    - *.sln files exist
  Node.js:
    - package.json + (express|fastify|nest|koa)
    - tsconfig.json or jsconfig.json
  Python:
    - requirements.txt OR pyproject.toml OR setup.py
    - (fastapi|flask|django) in dependencies
  Go:
    - go.mod exists

Database:
  PostgreSQL:
    - DATABASE_URL contains "postgres"
    - docker-compose.yml contains "postgres"
  MongoDB:
    - MONGODB_URI in env
    - docker-compose.yml contains "mongo"
  MySQL:
    - DATABASE_URL contains "mysql"

ORM:
  Drizzle: drizzle.config.ts exists
  Prisma: prisma/schema.prisma exists
  EF Core: *.csproj references Microsoft.EntityFrameworkCore
  SQLAlchemy: "sqlalchemy" in requirements

Detection Output

Detected Stack:
  Frontend:
    Framework: React
    Version: 19.x
    Build Tool: Vite
    UI Library: shadcn/ui
    State: React Query

  Backend:
    Current: Node.js + Express
    Target: .NET 10 (user preference)
    ORM: Drizzle -> EF Core

  Database:
    Type: PostgreSQL
    Version: 17

  Structure:
    Type: Monolith (Prototype)
    Origin: replit | stackblitz | codesandbox | glitch | custom
    Target: Clean Architecture

Phase 1: Generate Transformation Plan

Based on detected stack, create detailed plan:

# Bootstrap Transformation Plan

## Source Analysis
- Frontend: React 19 + Vite + TypeScript
- Backend: Express + Drizzle (to be replaced with .NET)
- Database: PostgreSQL 17

## Transformations

### 1. Dependencies (ln-820)
- Upgrade React 18 -> 19
- Upgrade Vite 5 -> 6
- Add missing peer dependencies

### 2. Structure (ln-720)
- Move frontend to src/frontend/
- Create .NET backend: MyApp.Api, MyApp.Domain, etc.
- Migrate mock data from Drizzle to MockData classes

### 3. DevOps (ln-730)
- Create Dockerfile.frontend (multi-stage)
- Create Dockerfile.backend (.NET SDK)
- Create docker-compose.yml
- Create .github/workflows/ci.yml

### 4. Quality (ln-740)
- Configure ESLint (flat config)
- Add Prettier
- Setup Husky + lint-staged
- Create test infrastructure (Vitest, xUnit)

### 5. Security (ln-760)
- Scan for hardcoded secrets
- Run npm audit
- Create SECURITY.md

### 6. Crosscutting (ln-770)
- Configure Serilog logging
- Add GlobalExceptionMiddleware
- Configure CORS policy
- Add /health endpoints
- Enable Swagger

### 7. Verification (ln-780)
- Build all projects
- Run tests
- Start Docker containers
- Verify health checks

## Estimated Changes
- Files created: ~45
- Files modified: ~12
- Files deleted: ~8 (replaced backend)

Phase 2: User Confirmation

Present plan and ask for approval:

Bootstrap Plan Ready!

Summary:
- Frontend: React 19 (upgrade from 18)
- Backend: .NET 10 (replacing Node.js)
- Docker: Multi-container setup
- CI/CD: GitHub Actions
- Quality: ESLint, Prettier, Husky

Proceed with bootstrap? [Y/n]

If user declines, ask for modifications.


Phase 3: Execute Delegations

Sequential delegation to L2 coordinators:

OrderSkillPurposeCREATE modeTRANSFORM modeDepends On
1ln-820Upgrade dependenciesSKIPRUN—
2ln-720Structure (SCAFFOLD/RESTRUCTURE)RUN (SCAFFOLD)RUN (RESTRUCTURE)ln-820
3ln-730Setup Docker/CIRUNRUNln-720
4ln-740Configure quality toolsRUNRUNln-720
5ln-760Security scanningRUNRUNln-820
6ln-770Crosscutting concernsRUNRUNln-720
7ln-780Build and verifyRUNRUNAll above

Delegation Protocol

For each L2 coordinator:

  1. Prepare context:

    Stack:
      frontend: { framework, version, buildTool }
      backend: { framework, version }
      database: { type, version }
    
    Paths:
      root: /project
      frontend: /project/src/frontend
      backend: /project/src/MyApp.Api
    
    Options:
      skipTests: false
      allowFailures: false
    
  2. Invoke skill: Pass context as input

    Skill(skill: "ln-820-dependency-upgrader", args: "{projectPath} --mode TRANSFORM")
    Skill(skill: "ln-720-structure-migrator", args: "{projectPath} --mode {CREATE|TRANSFORM}")
    Skill(skill: "ln-730-devops-setup", args: "{projectPath}")
    Skill(skill: "ln-740-quality-setup", args: "{projectPath}")
    Skill(skill: "ln-760-security-setup", args: "{projectPath}")
    Skill(skill: "ln-770-crosscutting-setup", args: "{projectPath}")
    Skill(skill: "ln-780-bootstrap-verifier", args: "{projectPath}")
    
  3. Collect result:

    Status: success | partial | failed
    FilesCreated: [...]
    FilesModified: [...]
    Warnings: [...]
    Errors: [...]
    
  4. Handle errors:

    • Log error details
    • Ask user: continue or abort?
    • If abort, rollback if possible

Phase 4: Generate Report

Bootstrap Completeness Assessment

Context: Final verification that bootstrap produced a working project, not just files.

#CategoryCheckSource
1StructureClean Architecture layers presentln-720 result
2DependenciesAll packages installed, no version conflictsln-820 result
3DevOpsDocker builds, CI pipeline validln-730 result
4QualityLinters/formatters configured and passln-740 result
5SecurityNo hardcoded secrets, scanning configuredln-760 result
6BuildProject compiles/builds without errorsln-780 result

Completeness Score = count of PASS / 6

  • 6/6: Bootstrap complete
  • 4-5/6: Bootstrap complete with warnings (list failing categories)
  • <4/6: Bootstrap incomplete — list blocking issues for user action

Summary Report

Final summary after all delegations:

Bootstrap Complete!

Duration: 24 minutes 32 seconds

Changes Summary:
  Files Created: 47
  Files Modified: 15
  Files Deleted: 9

By Category:
  Dependencies:
    - Upgraded 23 packages
    - No breaking changes detected

  Structure:
    - Created 5 .NET projects
    - Restructured frontend (12 components extracted)
    - Migrated 8 mock data files

  DevOps:
    - Created Dockerfile.frontend
    - Created Dockerfile.backend
    - Created docker-compose.yml
    - Created .github/workflows/ci.yml

  Quality:
    - Configured ESLint + Prettier
    - Installed Husky hooks
    - Created 3 test files

  Security:
    - Scanned 156 files
    - Found 0 secrets
    - 2 vulnerability warnings (low severity)

  Crosscutting:
    - Configured Serilog
    - Added error handling
    - CORS enabled for localhost
    - Health checks at /health
    - Swagger at /swagger

Verification:
  Build: SUCCESS
  Tests: 42 passed, 0 failed
  Docker: 3 containers running
  Health: All endpoints responding

Next Steps:
  1. Open http://localhost:3000 (frontend)
  2. Open http://localhost:5000/swagger (API docs)
  3. Run 'git add . && git commit -m "Bootstrap complete"'

Error Handling

Recoverable Errors

ErrorAction
Dependency conflictTry with --legacy-peer-deps
Build failureLog error, suggest fix, continue
Test failureLog warning, continue with --allow-failures
Docker build failSuggest Dockerfile fixes

Fatal Errors

ErrorActionMode
No package.json (TRANSFORM)Abort: "Not a Node.js project"TRANSFORM
Unsupported stackAbort: "Stack not supported: {stack}"Both
Permission deniedAbort: "Cannot write to {path}"Both
No stack selectedAbort: "Target stack required for CREATE mode"CREATE
Conflicting filesAbort if user chose "Abort" in pre-flightCREATE

Configuration

Skill Options

Options:
  # Backend replacement
  targetBackend: ".NET" | "Node" | "Python" | "keep"

  # Frontend refactoring depth
  frontendRefactoring: "minimal" | "moderate" | "full"

  # Docker setup
  dockerEnabled: true
  dockerRegistry: null  # Optional: ghcr.io/user

  # CI/CD
  cicdProvider: "github" | "azure" | "gitlab" | "none"

  # Quality tools
  linterConfig: "recommended" | "strict"
  precommitHooks: true

  # Verification
  runTests: true
  startContainers: true
  keepContainersRunning: true

Environment Variables

# Optional: Override detection
BOOTSTRAP_FRONTEND=react
BOOTSTRAP_BACKEND=dotnet
BOOTSTRAP_DB=postgres

# Optional: Skip steps
SKIP_DEPENDENCIES=false
SKIP_DOCKER=false
SKIP_TESTS=false

Integration with Existing Skills

SkillIntegration
references/research_methodology.mdStandards research during ln-720
references/documentation_creation.mdGuide generation during ln-720
ln-100-documents-pipelineCall after bootstrap for docs
ln-310-multi-agent-validatorValidate generated tasks

References

MANDATORY READ: Load these files at the phases indicated:

  • references/stack_detection.md — Phase 0 detection rules and patterns
  • references/templates/transformation_plan_template.md — Phase 1 plan template
  • references/verification_checklist.md — Phase 3 verification steps

TodoWrite format (mandatory):

- Invoke ln-820-dependency-upgrader (conditional TRANSFORM) (pending)
- Invoke ln-720-structure-migrator (pending)
- Invoke ln-730-devops-setup (pending)
- Invoke ln-740-quality-setup (pending)
- Invoke ln-760-security-setup (pending)
- Invoke ln-770-crosscutting-setup (pending)
- Invoke ln-780-bootstrap-verifier (pending)
- Generate completion report (pending)

Worker Invocation (MANDATORY)

Host Skill Invocation: Skill(skill: "...", args: "...") is mandatory delegation.

  • Claude: call the Skill tool exactly as shown.
  • Codex: if no Skill tool exists, locate the named skill in available skills, read its SKILL.md, treat args as $ARGUMENTS, execute that skill workflow, then return here with its result/artifact.
  • Do not inline worker logic or mark the worker complete without executing the target skill.
PhaseWorkerContext
3.1ln-820-dependency-upgraderShared (Skill tool) — upgrade existing deps (TRANSFORM only)
3.2ln-720-structure-migratorShared (Skill tool) — scaffold or restructure to Clean Architecture
3.3ln-730-devops-setupShared (Skill tool) — Docker, CI/CD, environment config
3.4ln-740-quality-setupShared (Skill tool) — linters, pre-commit, test infrastructure
3.5ln-760-security-setupShared (Skill tool) — security scanning and hardening
3.6ln-770-crosscutting-setupShared (Skill tool) — logging, error handling, CORS, health
3.7ln-780-bootstrap-verifierShared (Skill tool) — build, test, Docker verification

All workers: Invoke via Skill tool — workers see coordinator context.

Definition of Done

  • Tech stack detected (or user-specified for CREATE mode) and plan generated
  • All L2 coordinators delegated and completed (ln-820 through ln-780)
  • Bootstrap completeness score 4/6 or higher
  • Final summary report presented to user

Phase 5: Meta-Analysis

Optional reference: load references/meta_analysis_protocol.md only when the user asks for post-run meta-analysis or protocol-formatted run reflection.

Skill type: execution-orchestrator. When requested, run after all phases complete. Output to chat using the execution-orchestrator format.


Version: 2.0.0 Last Updated: 2026-02-07

FAQ

What does the ln-700-project-bootstrap skill do?

Bootstraps projects to production-ready structure. Use when creating new or transforming existing projects.

How do I install ln-700-project-bootstrap?

Run npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-700-project-bootstrap in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ln-700-project-bootstrap/ (personal) or .claude/skills/ln-700-project-bootstrap/ (project).

Which AI agents can use ln-700-project-bootstrap?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is ln-700-project-bootstrap safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains ln-700-project-bootstrap?

It is published by levnikolaevich in levnikolaevich/claude-code-skills. It has 384 recorded installs.

More from levnikolaevich/claude-code-skills

View all →

ln-100-documents-pipeline

levnikolaevich/claude-code-skills

Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.

Docs & Writing479 installs

ln-620-codebase-auditor

levnikolaevich/claude-code-skills

Open the skill to read its SKILL.md instructions.

ln-775-api-docs-generator

levnikolaevich/claude-code-skills

Configures Swagger/OpenAPI documentation for backend APIs. Use when adding interactive API docs to a project.

Backend & APIs432 installs

ln-624-code-quality-auditor

levnikolaevich/claude-code-skills

Checks cyclomatic complexity, nesting, long methods, god classes, O(n2), N+1 queries, constants management. Use when auditing code quality.

413 installs

ln-782-test-runner

levnikolaevich/claude-code-skills

Executes all test suites and reports results with coverage. Use when verifying that test infrastructure works after bootstrap.

Testing & QA412 installs

ln-634-test-coverage-auditor

levnikolaevich/claude-code-skills

Open the skill to read its SKILL.md instructions.

Testing & QA401 installs

Popular other skills

View category →

hyperframes-cli

heygen-com/hyperframes

The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.

1.3M installs

triage

mattpocock/skills

Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

1M installs

ask-matt

mattpocock/skills

Ask which skill or flow fits your situation. A router over the skills in this repo.

778.4K installs

to-questionnaire

mattpocock/skills

Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

508.9K installs

wait-what

mattpocock/skills

Stop. That last message did not land: re-pitch it.

459.7K installs

loop-me

mattpocock/skills

Grill me about specs for the workflows I want to build, within this workspace.

447.9K installs