
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- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads ln-700-project-bootstrap automatically when relevant.
- 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
| Aspect | CREATE | TRANSFORM |
|---|---|---|
| Input | Empty directory or target stack config | Existing project (Replit, StackBlitz, CodeSandbox, Glitch, custom) |
| Detection | No source files found | Source files + optional platform config detected |
| ln-820 | SKIP (no deps to upgrade) | RUN (upgrade existing deps) |
| ln-720 | SCAFFOLD + GENERATE | RESTRUCTURE + MIGRATE |
| ln-724 | SKIP (no artifacts) | CONDITIONAL (if platform detected) |
| ln-730–780 | RUN (same for both modes) | RUN (same for both modes) |
Overview
| Aspect | Details |
|---|---|
| Input | Empty directory (CREATE) or source project (TRANSFORM) |
| Output | Production-ready project with all infrastructure |
| Delegations | ln-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
| Condition | Mode | Action |
|---|---|---|
| Empty directory (no source files) | CREATE | Ask user for target stack, project name, entities |
| Source files found | TRANSFORM | Auto-detect stack, scan for platform artifacts |
| Ambiguous (few files, unclear) | ASK | Present both options, let user choose |
Step 0.1: CREATE Mode — User Input
| Parameter | Required | Default | Example |
|---|---|---|---|
| Project name | Yes | — | MyApp |
| Target backend | Yes | — | .NET / Node.js / Python |
| Target frontend | Yes | — | React / Vue / Angular / Svelte |
| Database | Yes | — | PostgreSQL / MongoDB / MySQL |
| Main entities | No | User, Role (starter) | User, Product, Order |
Step 0.2: Idempotency Pre-flight
If target directory contains existing files:
- Detect existing structure (package.json, .csproj, etc.)
- Warn user: "Target directory is not empty. Existing files may be overwritten."
- 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:
| Order | Skill | Purpose | CREATE mode | TRANSFORM mode | Depends On |
|---|---|---|---|---|---|
| 1 | ln-820 | Upgrade dependencies | SKIP | RUN | — |
| 2 | ln-720 | Structure (SCAFFOLD/RESTRUCTURE) | RUN (SCAFFOLD) | RUN (RESTRUCTURE) | ln-820 |
| 3 | ln-730 | Setup Docker/CI | RUN | RUN | ln-720 |
| 4 | ln-740 | Configure quality tools | RUN | RUN | ln-720 |
| 5 | ln-760 | Security scanning | RUN | RUN | ln-820 |
| 6 | ln-770 | Crosscutting concerns | RUN | RUN | ln-720 |
| 7 | ln-780 | Build and verify | RUN | RUN | All above |
Delegation Protocol
For each L2 coordinator:
-
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 -
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}") -
Collect result:
Status: success | partial | failed FilesCreated: [...] FilesModified: [...] Warnings: [...] Errors: [...] -
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.
| # | Category | Check | Source |
|---|---|---|---|
| 1 | Structure | Clean Architecture layers present | ln-720 result |
| 2 | Dependencies | All packages installed, no version conflicts | ln-820 result |
| 3 | DevOps | Docker builds, CI pipeline valid | ln-730 result |
| 4 | Quality | Linters/formatters configured and pass | ln-740 result |
| 5 | Security | No hardcoded secrets, scanning configured | ln-760 result |
| 6 | Build | Project compiles/builds without errors | ln-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
| Error | Action |
|---|---|
| Dependency conflict | Try with --legacy-peer-deps |
| Build failure | Log error, suggest fix, continue |
| Test failure | Log warning, continue with --allow-failures |
| Docker build fail | Suggest Dockerfile fixes |
Fatal Errors
| Error | Action | Mode |
|---|---|---|
| No package.json (TRANSFORM) | Abort: "Not a Node.js project" | TRANSFORM |
| Unsupported stack | Abort: "Stack not supported: {stack}" | Both |
| Permission denied | Abort: "Cannot write to {path}" | Both |
| No stack selected | Abort: "Target stack required for CREATE mode" | CREATE |
| Conflicting files | Abort if user chose "Abort" in pre-flight | CREATE |
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
| Skill | Integration |
|---|---|
| references/research_methodology.md | Standards research during ln-720 |
| references/documentation_creation.md | Guide generation during ln-720 |
| ln-100-documents-pipeline | Call after bootstrap for docs |
| ln-310-multi-agent-validator | Validate generated tasks |
References
MANDATORY READ: Load these files at the phases indicated:
references/stack_detection.md— Phase 0 detection rules and patternsreferences/templates/transformation_plan_template.md— Phase 1 plan templatereferences/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, treatargsas$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.
| Phase | Worker | Context |
|---|---|---|
| 3.1 | ln-820-dependency-upgrader | Shared (Skill tool) — upgrade existing deps (TRANSFORM only) |
| 3.2 | ln-720-structure-migrator | Shared (Skill tool) — scaffold or restructure to Clean Architecture |
| 3.3 | ln-730-devops-setup | Shared (Skill tool) — Docker, CI/CD, environment config |
| 3.4 | ln-740-quality-setup | Shared (Skill tool) — linters, pre-commit, test infrastructure |
| 3.5 | ln-760-security-setup | Shared (Skill tool) — security scanning and hardening |
| 3.6 | ln-770-crosscutting-setup | Shared (Skill tool) — logging, error handling, CORS, health |
| 3.7 | ln-780-bootstrap-verifier | Shared (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
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.
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.
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.
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.
ln-634-test-coverage-auditor
levnikolaevich/claude-code-skills
Open the skill to read its SKILL.md instructions.
Popular other skills
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.
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.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.