.claude/skills/bootstrap/SKILL.md
Bootstrap new projects with research, tech stack, design, planning, and implementation. Modes: full (interactive), auto (default), fast (skip research), parallel (multi-agent).
npx skillsauth add haidonglethqb/CloudSchool ck:bootstrapInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
End-to-end project bootstrapping from idea to running code.
Principles: YAGNI, KISS, DRY | Token efficiency | Concise reports
/bootstrap <user-requirements>
Flags (optional, default --auto):
| Flag | Mode | Thinking | User Gates | Planning Skill | Cook Skill |
|------|------|----------|------------|----------------|------------|
| --full | Full interactive | Ultrathink | Every phase | --hard | (interactive) |
| --auto | Automatic | Ultrathink | Design only | --auto | --auto |
| --fast | Quick | Think hard | None | --fast | --auto |
| --parallel | Multi-agent | Ultrathink | Design only | --parallel | --parallel |
Example:
/bootstrap "Build a SaaS dashboard with auth" --fast
/bootstrap "E-commerce platform with Stripe" --parallel
[Git Init] → [Research?] → [Tech Stack?] → [Design?] → [Planning] → [Implementation] → [Test] → [Review] → [Docs] → [Onboard] → [Final]
Each mode loads a specific workflow reference + shared phases.
If no flag provided, default to --auto.
Load the appropriate workflow reference:
--full: Load references/workflow-full.md--auto: Load references/workflow-auto.md--fast: Load references/workflow-fast.md--parallel: Load references/workflow-parallel.mdAll modes share: Load references/shared-phases.md for implementation through final report.
Check if Git initialized. If not:
--full: Ask user if they want to init → git-manager subagent (main branch)git-manager subagent (main branch)After early phases (research, tech stack, design), trigger downstream skills:
Activate ck:plan skill with mode-appropriate flag:
--full → /ck:plan --hard <requirements> (thorough research + validation)--auto → /ck:plan --auto <requirements> (auto-detect complexity)--fast → /ck:plan --fast <requirements> (skip research)--parallel → /ck:plan --parallel <requirements> (file ownership + dependency graph)Planning skill outputs a plan path. Pass this to cook.
Activate ck:cook skill with the plan path and mode-appropriate flag:
--full → /ck:cook <plan-path> (interactive review gates)--auto → /ck:cook --auto <plan-path> (skip review gates)--fast → /ck:cook --auto <plan-path> (skip review gates)--parallel → /ck:cook --parallel <plan-path> (multi-agent execution)Elite software engineering expert specializing in system architecture and technical decisions. Brutally honest about feasibility and trade-offs.
./docs directory./plans directory using naming from ## Naming sectionreferences/workflow-full.md - Full interactive workflowreferences/workflow-auto.md - Auto workflow (default)references/workflow-fast.md - Fast workflowreferences/workflow-parallel.md - Parallel workflowreferences/shared-phases.md - Common phases (implementation → final report)development
Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes (kubectl, Helm). Use for serverless, containers, CI/CD, GitOps, security audit.
development
Debug systematically with root cause analysis before fixes. Use for bugs, test failures, unexpected behavior, performance issues, call stack tracing, multi-layer validation, log analysis, CI/CD failures, database diagnostics, system investigation.
data-ai
Conversion copywriting formulas, headline templates, email copy patterns, landing page structures, CTA optimization, and writing style extraction. Activate for writing high-converting copy, crafting headlines, email campaigns, landing pages, or applying custom writing styles from assets/writing-styles/ directory.
tools
ALWAYS activate this skill before implementing EVERY feature, plan, or fix.