ck:bootstrap
Bootstrap new projects with research, tech stack, design, planning, and implementation. Modes: full (interactive), auto (default), fast (skip research), parallel (multi-agent).
- License 许可
- MIT
- 最近更新
- 2026-03-20
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- ck:bootstrap
- license
- MIT
- description
- Bootstrap new projects with research, tech stack, design, planning, and implementation. Modes: full (interactive), auto (default), fast (skip research), parallel (multi-agent).
- argument-hint
- [requirements] [--full|--auto|--fast|--parallel]
02 资源文件 5
- 参考文档references/shared-phases.md2.1 KB
- 参考文档references/workflow-auto.md1.8 KB
- 参考文档references/workflow-fast.md1.9 KB
- 参考文档references/workflow-full.md2.3 KB
- 参考文档references/workflow-parallel.md2.3 KB
03 SKILL.md 正文
Bootstrap - New Project Scaffolding
End-to-end project bootstrapping from idea to running code.
Principles: YAGNI, KISS, DRY | Token efficiency | Concise reports
Usage
/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
Workflow Overview
[Git Init] → [Research?] → [Tech Stack?] → [Design?] → [Planning] → [Implementation] → [Test] → [Review] → [Docs] → [Onboard] → [Final]
Each mode loads a specific workflow reference + shared phases.
Mode Detection
If no flag provided, default to --auto.
Load the appropriate workflow reference:
--full: Loadreferences/workflow-full.md--auto: Loadreferences/workflow-auto.md--fast: Loadreferences/workflow-fast.md--parallel: Loadreferences/workflow-parallel.md
All modes share: Load references/shared-phases.md for implementation through final report.
Step 0: Git Init (ALL modes)
Check if Git initialized. If not:
--full: Ask user if they want to init →git-managersubagent (mainbranch)- Others: Auto-init via
git-managersubagent (mainbranch)
Skill Triggers (MANDATORY)
After early phases (research, tech stack, design), trigger downstream skills:
Planning Phase
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.
Implementation Phase
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)
Role
Elite software engineering expert specializing in system architecture and technical decisions. Brutally honest about feasibility and trade-offs.
Critical Rules
- Activate relevant skills from catalog during the process
- Keep all research reports ≤150 lines
- All docs written to
./docsdirectory - Plans written to
./plansdirectory using naming from## Namingsection - DO NOT implement code directly — delegate through planning + cook skills
- Sacrifice grammar for concision in reports
- List unresolved questions at end of reports
References
references/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)
04 同仓库更多 Skills
ck:web-testing
Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
ck:web-frameworks
Build with Next.js (App Router, RSC, SSR, ISR), Turborepo monorepos. Use for React apps, server rendering, build optimization, caching strategies, shared dependencies.
ck:ui-styling
Style UIs with shadcn/ui components (Radix UI + Tailwind CSS). Use for accessible components, themes, dark mode, responsive layouts, design systems, color customization.
ck:threejs
Build 3D web apps with Three.js (WebGL/WebGPU). 556 searchable examples, 60 API classes, 20 use cases. Actions: create 3D scene, load model, add animation, implement physics, build VR/XR. Topics: GLTF loader, PBR materials, particle effects, shadows, post-processing, compute shaders, TSL. Integrations: WebGPU, physics engines, spatial audio.
ck:sequential-thinking
Apply step-by-step analysis for complex problems with revision capability. Use for multi-step reasoning, hypothesis verification, adaptive planning, problem decomposition, course correction.
ck:research
Research technical solutions, analyze architectures, gather requirements thoroughly. Use for technology evaluation, best practices research, solution design, scalability/security/maintainability analysis.