ck:bootstrap
GitHub提供从构思到代码运行的端到端项目引导技能，支持全交互、自动、快速及多智能体并行模式，涵盖研究、技术选型、设计、规划与实现全流程。
Trigger Scenarios
Install
npx skills add phuc-nt/my-translator --skill ck:bootstrap -g -y
SKILL.md
Frontmatter
{
"name": "ck:bootstrap",
"license": "MIT",
"metadata": {
"author": "claudekit",
"version": "1.0.0"
},
"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]"
}
Bootstrap - New Project Scaffolding
End-to-end project bootstrapping from idea to running code.
Principles: YAGNI, KISS, DRY | Token efficiency | Concise reports
Usage
/ck: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:
/ck:bootstrap "Build a SaaS dashboard with auth" --fast
/ck: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
- Run
/ck:journalto write a concise technical journal entry upon completion
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)
Version History
- 3495f99 Current 2026-07-25 07:18
