@codebakers/mcp 5.5.7 → 5.5.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/CLAUDE.md +96 -80
  2. package/dist/cli.js +1 -1
  3. package/package.json +1 -1
package/CLAUDE.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # 🍞 CodeBakers V5
2
2
 
3
- **Version:** 5.5.7
3
+ **Version:** 5.5.8
4
4
 
5
5
  > Conversational AI development - Build apps by chatting naturally
6
6
 
@@ -36,90 +36,106 @@ The `codebakers_start` tool shows:
36
36
 
37
37
  ---
38
38
 
39
- ## 🔥 MANDATORY WORKFLOW - AFTER BRANDED INTRO
39
+ ## 💬 How CodeBakers Works (For You - The AI)
40
40
 
41
- **AFTER showing the branded introduction, you MUST follow this workflow:**
41
+ **After showing the branded introduction, the user chooses how to work:**
42
42
 
43
- ### Step 1: Check Context (ALWAYS)
44
- ```
45
- codebakers_get_context
46
- ```
47
- This tells you current phase, what's done, what's blocking, what's next.
43
+ 1. **"Build it FOR me"** = Autonomous mode (you do everything, just update them)
44
+ 2. **"Build it WITH me"** = Collaborative mode (ask before each major step)
45
+ 3. **"TEACH me"** = Educational mode (explain everything as you go)
46
+
47
+ **Respect their choice. Different users want different experiences.**
48
+
49
+ ---
50
+
51
+ ## 📋 The CodeBakers Method (7 Phases)
52
+
53
+ **You follow these phases, but HOW you follow them depends on the user's choice (FOR/WITH/TEACH):**
48
54
 
49
- ### Step 2: Follow Phase-Specific Workflow
55
+ ### Phase 0: Domain Research & Specification
50
56
 
51
- **Phase 0: No Spec Yet**
57
+ **What happens:**
52
58
  1. User describes what they want to build
53
- 2. **IMMEDIATELY run**: `codebakers_generate_spec(description)`
54
- 3. Show them the features
55
- 4. **Ask**: "Sound good? Ready for the next step?"
56
- 5. **Guide to Phase 1**: "Next, I need to understand your users and workflows better..."
57
-
58
- **Phase 1: Need Interview**
59
- 1. **IMMEDIATELY run**: `codebakers_run_interview(description)`
60
- 2. This creates:
61
- - `project-profile.md` (user personas, goals)
62
- - `FLOWS.md` (user workflows)
63
- - `BRAIN.md` (business logic)
64
- 3. Tell user: "I've mapped out your user flows and business logic!"
65
- 4. **Guide to Phase 2**: "Now I need to see what you want it to look like..."
66
-
67
- **Phase 2: Need Mockups**
68
- 1. **FIRST: Create folder structure if it doesn't exist:**
69
- - Create `refs/design/` folder (this is WHERE mockups go)
70
- - Create `.codebakers/` folder (this is WHERE analysis goes)
71
- 2. **Tell user they have 3 options:**
72
- - Upload designs to `refs/design/` folder
73
- - Have you generate mockups
74
- - Draw sketches and upload photos
75
- 3. **When they upload/provide mockups:**
76
- - Run `codebakers_validate_mockups`
77
- - Run `codebakers_fix_mockups` if needed
78
- - Run `codebakers_verify_mockups`
79
- 3. **When mockups are perfect:**
80
- - Run `codebakers_analyze_mockups_deep`
81
- - Run `codebakers_generate_schema`
82
- - Run `codebakers_map_dependencies`
83
- - Run `codebakers_generate_store_contracts`
84
- 4. **Guide to Phase 3**: "Everything's mapped out! Ready to start building?"
85
-
86
- **Phase 3: Build Features**
87
- 1. Run `codebakers_builder({mode: "full"})`
88
- 2. This automatically:
89
- - Generates migrations
90
- - Creates API routes
91
- - Builds stores
92
- - Creates components
93
- - Writes tests
94
- 3. Show progress updates
95
- 4. **Guide to Phase 4**: "All features built! Let me run quality checks..."
96
-
97
- **Phase 4: Quality Gates**
98
- 1. Run `codebakers_validate_accessibility`
99
- 2. Run `codebakers_optimize_performance`
100
- 3. Run `codebakers_scan_security`
101
- 4. Fix any issues found
102
- 5. **Guide to Phase 5**: "Quality checks passed! Ready to deploy?"
103
-
104
- **Phase 5: Deployment**
105
- 1. Run `codebakers_setup_github` (if not done)
106
- 2. Run `codebakers_setup_supabase` (if not done)
107
- 3. Run `codebakers_setup_vercel` (if not done)
108
- 4. Run `codebakers_deploy_vercel`
109
- 5. **Guide to Phase 6**: "Your app is live! Want me to generate docs?"
110
-
111
- **Phase 6: Documentation & Support**
112
- 1. Run `codebakers_generate_docs`
113
- 2. Run `codebakers_generate_chatbot` (optional)
114
- 3. Tell user: "All done! Your app is deployed with full documentation!"
115
-
116
- ### Critical Rules:
117
- - **ALWAYS check context first** with `codebakers_get_context`
118
- - **ALWAYS follow the phase workflow** - don't skip steps
119
- - **ALWAYS use the enforcement tools** (validate, check gates, etc.)
120
- - **ALWAYS guide user to next step** - don't leave them hanging
121
-
122
- **The user should never have to ask "what's next?" - YOU always tell them.**
59
+ 2. You run `codebakers_generate_spec(description)`
60
+ 3. This creates PROJECT-SPEC.md with Gates 0-5:
61
+ - Gate 0: Identity (name, mission, users)
62
+ - Gate 1: Entities (data objects)
63
+ - Gate 2: State Changes (actions)
64
+ - Gate 3: Permissions (who can do what)
65
+ - Gate 4: Dependencies (external services)
66
+ - Gate 5: Integrations (third-party)
67
+ 4. **WAIT for user approval before Phase 1**
68
+
69
+ **Conversational approach:**
70
+ - FOR mode: Generate spec, show summary, ask "Ready to design the UI?"
71
+ - WITH mode: Show spec, ask "Want to adjust anything before we move on?"
72
+ - TEACH mode: Explain each gate, why it matters, what decisions were made
73
+
74
+ ---
75
+
76
+ ### Phase 1: UI Mockup & Design
77
+
78
+ **What happens:**
79
+ 1. User needs mockups for EVERY screen
80
+ 2. Give them 3 options:
81
+ - Upload designs from Figma/tools to `refs/design/`
82
+ - Have you generate mockups based on spec
83
+ - Draw sketches / take photos and upload
84
+ 3. All screens must be mocked (empty, loading, error, success states)
85
+ 4. **WAIT for user approval of mockups before Phase 2**
86
+
87
+ **Conversational approach:**
88
+ - FOR mode: "I'll generate mockups for all screens. Give me 5 minutes..."
89
+ - WITH mode: "Want to upload designs or should I create mockups?"
90
+ - TEACH mode: "Mockups are critical because Phase 2 extracts the database schema FROM them. Let me show you..."
91
+
92
+ ---
93
+
94
+ ### Phase 2: Mock Analysis, Schema & Dependencies
95
+
96
+ **What happens:**
97
+ 1. Create folder structure: `refs/design/` and `.codebakers/`
98
+ 2. Run `codebakers_validate_mockups` → fix issues
99
+ 3. Run `codebakers_analyze_mockups_deep` → extract ALL data from mockups
100
+ 4. Run `codebakers_generate_schema` → create database schema from analysis
101
+ 5. Run `codebakers_map_dependencies` → map ALL dependencies
102
+ 6. Run `codebakers_generate_store_contracts` → define state management
103
+ 7. **WAIT for verification before Phase 3**
104
+
105
+ **This is the CORE of CodeBakers Method:**
106
+ - Schema comes FROM mockups, not abstract design
107
+ - Dependencies mapped BEFORE coding
108
+ - Zero surprises during build
109
+
110
+ **Conversational approach:**
111
+ - FOR mode: Run all silently, show: "Analysis complete! Found 8 tables, 24 dependencies..."
112
+ - WITH mode: Show mockup analysis, ask "Does this data structure make sense?"
113
+ - TEACH mode: "I'm analyzing each mockup to find every piece of data displayed. For example, this user card shows: name, email, avatar..."
114
+
115
+ ---
116
+
117
+ ### Phase 3-6: Build, Test, Deploy
118
+
119
+ **Phase 3:** Foundation (auth, database setup)
120
+ **Phase 4:** Features (run `codebakers_builder`)
121
+ **Phase 5:** Quality gates (accessibility, performance, security)
122
+ **Phase 6:** Deployment (Vercel + Supabase)
123
+
124
+ **Conversational approach based on mode:**
125
+ - FOR mode: Build autonomously, show progress updates
126
+ - WITH mode: Ask before major decisions
127
+ - TEACH mode: Explain each step
128
+
129
+ ---
130
+
131
+ ## ⚙️ Key Principles
132
+
133
+ 1. **ALWAYS run `codebakers_get_context` first** - know current state
134
+ 2. **ALWAYS respect user's mode** (FOR/WITH/TEACH)
135
+ 3. **ALWAYS wait for approval** at phase gates (spec, mockups, before build)
136
+ 4. **NEVER skip phases** - the order matters
137
+ 5. **Mockups drive everything** - Phase 2 extracts schema FROM mockups
138
+ 6. **Be conversational** - hide technical complexity, guide naturally
123
139
 
124
140
  ---
125
141
 
package/dist/cli.js CHANGED
@@ -31,7 +31,7 @@ async function main() {
31
31
  await init();
32
32
  break;
33
33
  case 'version':
34
- console.log('CodeBakers MCP Server v5.5.7');
34
+ console.log('CodeBakers MCP Server v5.5.8');
35
35
  break;
36
36
  default:
37
37
  console.error(`Unknown command: ${command}`);
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@codebakers/mcp",
3
- "version": "5.5.7",
3
+ "version": "5.5.8",
4
4
  "description": "CodeBakers Method MCP Server - Complete autonomous app builder with context-aware consulting",
5
5
  "main": "dist/index.js",
6
6
  "type": "module",