cm-how-it-work

Name: cm-how-it-work
Author: tody-agent

47stars23forks

How to install cm-how-it-work?

tody-agent/codymaster/cm-how-it-work

$npx -y skills add tody-agent/codymaster --skill cm-how-it-work

Installs into the current project.

Summary

Complete guide to vibe coding with the CodyMaster skill kit — from idea to deploy. Covers the full workflow, skills used at each phase, and common use cases. Read this first if you are new; reference it whenever you're unsure which skill to invoke.

Files · 1

View on GitHub

SKILL.md

1	# CodyMaster Kit — The Ultimate Vibe Coding Guide
2
3	## Overview
4
5	The CodyMaster (CM) kit transforms ideas into production code through 13 specialized, optimized skills. This workflow ensures the highest quality, absolute security, and maximum execution speed.
6
7	```
8	💡 Idea → 🔍 Analysis → 📐 Design → 🧪 Test-first (TDD) → 💻 Code → ✅ Verify → 🚀 Deploy → 🔄 Iterate
9	```
10
11	---
12
13	## Workflow
14
15	### Phase 0: Identity & Safety 🔒
16	> Rule #1: Always verify identity before performing any action that could change the project state.
17
18	- Skill: `cm-identity-guard`
19	- When: At the start of a work session, before git push, deploy, or database operations.
20	- Action: Run `node check-identity.js` (or similar script) to verify GitHub/Cloudflare/Supabase accounts.
21
22	---
23
24	### Phase 0.3: Knowledge Infrastructure Setup 🧠
25	> For large codebases, establish the memory foundation before planning.
26
27	- Skills: `cm-codeintell` + `cm-dockit` + `cm-deep-search` + `cm-notebooklm`
28	- When: When onboarding to a new codebase or starting a massive refactoring initiative.
29	- Action:
30	1. Scan structure with `cm-codeintell` to build the Skeleton Index.
31	2. Generate missing architectural docs with `cm-dockit`.
32	3. Index the docs for fast local retrieval with `cm-deep-search` (qmd).
33	4. Sync high-value patterns to the Cloud Brain with `cm-notebooklm`.
34	- Output: A fully indexed 5-tier memory ecosystem ready for precise, low-token AI problem solving.
35
36	---
37
38	### Phase 0.5: Strategic Analysis 🔍
39	> For complex initiatives and enhancements on existing products.
40
41	- Skills: `cm-brainstorm-idea` + `cm-codeintell`
42	- When: When the task is complex and requires multi-dimensional analysis (tech, product, design, business) before planning.
43	- Action:
44	1. Scan codebase with code intelligence (AST graph + architecture diagram via `cm-codeintell`).
45	2. Interview user and analyze with 9 Windows (TRIZ).
46	3. Propose 2-3 options, evaluate multi-dimensionally, recommend the best option.
47	- Output: OpenSpec `openspec/changes/[initiative]/proposal.md` — qualified problem + recommended option → passes to `cm-planning`.
48
49	---
50
51	### Phase 1: Planning & Design 📐
52	> Understand the 'Job to be Done' (JTBD) and architecture before writing code.
53
54	- Skill: `cm-planning` (Combines brainstorming + writing-plans)
55	- Action:
56	1. Brainstorm requirements and analyze i18n.
57	2. Propose architecture and tech stack.
58	3. Write detailed OpenSpec docs (`openspec/changes/[init]/design.md` and `tasks.md`).
59	- Output: Design docs and execution plan (OpenSpec tasks) approved by user.
60
61	---
62
63	### Phase 2: Implementation (TDD & Execution) 💻
64	> Turn the plan into actual source code safely.
65
66	- Skills:
67	- `cm-tdd`: Red-Green-Refactor cycle. No production code without a failing test first.
68	- `cm-execution`: Execute plans intelligently (Manual, Parallel, or Subagent mode).
69	- `cm-project-bootstrap`: For new projects — setup repo, i18n, SEO, and deploy pipeline from Day 0.
70	- `cm-git-worktrees`: Isolate different work items to avoid state mixing.
71
72	---
73
74	### Phase 3: Quality Control & Verification ✅
75	> Prove with evidence, not words.
76
77	- Skills:
78	- `cm-quality-gate`: Setup test infrastructure (`test:gate`) and verify output before claiming "done".
79	- `cm-debugging`: When tests fail, use systematic investigation framework to find root cause.
80	- `cm-code-review`: Professional request and feedback review process.
81
82	---
83
84	### Phase 4: Safe Deployment 🚀
85	> Ship code without fear of incidents.
86
87	- Skills:
88	- `cm-safe-deploy`: Run 8-gate pipeline (Secret → Syntax → Test → Build → Deploy → Smoke).
89	- `cm-safe-i18n`: Translate and synchronize languages consistently across the entire project.
90	- `cm-terminal`: Monitor all terminal commands to detect errors immediately.
91
92	---
93
94	## CodyMaster Kit — 34 Skills Summary
95
96	### 🔧 Engineering
97	\| Skill \| Primary Function \|
98	\|-------\|-----------------\|
99	\| `cm-tdd` \| Strict Red-Green-Refactor TDD — no code without failing test first. \|
100	\| `cm-debugging` \| Systematic 5-phase error investigation (root cause first). \|
101	\| `cm-quality-gate` \| 6-gate verification: static analysis → blind review → ship. \|
102	\| `cm-test-gate` \| Setup 4-layer test infrastructure (unit → integration → e2e → security). \|
103	\| `cm-code-review` \| Manage PR lifecycle: request → receive feedback → complete branch. \|
104	\| `cm-codeintell` \| AST knowledge graph + architecture diagrams + smart context (30% fewer tokens). \|
105
106	### ⚙️ Operations
107	\| Skill \| Primary Function \|
108	\|-------\|-----------------\|
109	\| `cm-safe-deploy` \| Multi-gate deploy pipeline with rollback strategy. \|
110	\| `cm-identity-guard` \| Verify acco

People who liked this also viewed

6 picks

Type

cm-how-it-work

47stars23forks

View on GitHub

How to install cm-how-it-work?

tody-agent/codymaster/cm-how-it-work

$npx -y skills add tody-agent/codymaster --skill cm-how-it-work

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# CodyMaster Kit — The Ultimate Vibe Coding Guide
2
3	## Overview
4
5	The CodyMaster (CM) kit transforms ideas into production code through 13 specialized, optimized skills. This workflow ensures the highest quality, absolute security, and maximum execution speed.
6
7	```
8	💡 Idea → 🔍 Analysis → 📐 Design → 🧪 Test-first (TDD) → 💻 Code → ✅ Verify → 🚀 Deploy → 🔄 Iterate
9	```
10
11	---
12
13	## Workflow
14
15	### Phase 0: Identity & Safety 🔒
16	> Rule #1: Always verify identity before performing any action that could change the project state.
17
18	- Skill: `cm-identity-guard`
19	- When: At the start of a work session, before git push, deploy, or database operations.
20	- Action: Run `node check-identity.js` (or similar script) to verify GitHub/Cloudflare/Supabase accounts.
21
22	---
23
24	### Phase 0.3: Knowledge Infrastructure Setup 🧠
25	> For large codebases, establish the memory foundation before planning.
26
27	- Skills: `cm-codeintell` + `cm-dockit` + `cm-deep-search` + `cm-notebooklm`
28	- When: When onboarding to a new codebase or starting a massive refactoring initiative.
29	- Action:
30	1. Scan structure with `cm-codeintell` to build the Skeleton Index.
31	2. Generate missing architectural docs with `cm-dockit`.
32	3. Index the docs for fast local retrieval with `cm-deep-search` (qmd).
33	4. Sync high-value patterns to the Cloud Brain with `cm-notebooklm`.
34	- Output: A fully indexed 5-tier memory ecosystem ready for precise, low-token AI problem solving.
35
36	---
37
38	### Phase 0.5: Strategic Analysis 🔍
39	> For complex initiatives and enhancements on existing products.
40
41	- Skills: `cm-brainstorm-idea` + `cm-codeintell`
42	- When: When the task is complex and requires multi-dimensional analysis (tech, product, design, business) before planning.
43	- Action:
44	1. Scan codebase with code intelligence (AST graph + architecture diagram via `cm-codeintell`).
45	2. Interview user and analyze with 9 Windows (TRIZ).
46	3. Propose 2-3 options, evaluate multi-dimensionally, recommend the best option.
47	- Output: OpenSpec `openspec/changes/[initiative]/proposal.md` — qualified problem + recommended option → passes to `cm-planning`.
48
49	---
50
51	### Phase 1: Planning & Design 📐
52	> Understand the 'Job to be Done' (JTBD) and architecture before writing code.
53
54	- Skill: `cm-planning` (Combines brainstorming + writing-plans)
55	- Action:
56	1. Brainstorm requirements and analyze i18n.
57	2. Propose architecture and tech stack.
58	3. Write detailed OpenSpec docs (`openspec/changes/[init]/design.md` and `tasks.md`).
59	- Output: Design docs and execution plan (OpenSpec tasks) approved by user.
60
61	---
62
63	### Phase 2: Implementation (TDD & Execution) 💻
64	> Turn the plan into actual source code safely.
65
66	- Skills:
67	- `cm-tdd`: Red-Green-Refactor cycle. No production code without a failing test first.
68	- `cm-execution`: Execute plans intelligently (Manual, Parallel, or Subagent mode).
69	- `cm-project-bootstrap`: For new projects — setup repo, i18n, SEO, and deploy pipeline from Day 0.
70	- `cm-git-worktrees`: Isolate different work items to avoid state mixing.
71
72	---
73
74	### Phase 3: Quality Control & Verification ✅
75	> Prove with evidence, not words.
76
77	- Skills:
78	- `cm-quality-gate`: Setup test infrastructure (`test:gate`) and verify output before claiming "done".
79	- `cm-debugging`: When tests fail, use systematic investigation framework to find root cause.
80	- `cm-code-review`: Professional request and feedback review process.
81
82	---
83
84	### Phase 4: Safe Deployment 🚀
85	> Ship code without fear of incidents.
86
87	- Skills:
88	- `cm-safe-deploy`: Run 8-gate pipeline (Secret → Syntax → Test → Build → Deploy → Smoke).
89	- `cm-safe-i18n`: Translate and synchronize languages consistently across the entire project.
90	- `cm-terminal`: Monitor all terminal commands to detect errors immediately.
91
92	---
93
94	## CodyMaster Kit — 34 Skills Summary
95
96	### 🔧 Engineering
97	\| Skill \| Primary Function \|
98	\|-------\|-----------------\|
99	\| `cm-tdd` \| Strict Red-Green-Refactor TDD — no code without failing test first. \|
100	\| `cm-debugging` \| Systematic 5-phase error investigation (root cause first). \|
101	\| `cm-quality-gate` \| 6-gate verification: static analysis → blind review → ship. \|
102	\| `cm-test-gate` \| Setup 4-layer test infrastructure (unit → integration → e2e → security). \|
103	\| `cm-code-review` \| Manage PR lifecycle: request → receive feedback → complete branch. \|
104	\| `cm-codeintell` \| AST knowledge graph + architecture diagrams + smart context (30% fewer tokens). \|
105
106	### ⚙️ Operations
107	\| Skill \| Primary Function \|
108	\|-------\|-----------------\|
109	\| `cm-safe-deploy` \| Multi-gate deploy pipeline with rollback strategy. \|
110	\| `cm-identity-guard` \| Verify acco

People who liked this also viewed

6 picks

Type