takomi 2.1.13 → 2.1.15

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 (39) hide show
  1. package/.pi/agents/architect.md +73 -73
  2. package/.pi/agents/coder.md +70 -70
  3. package/.pi/agents/designer.md +72 -72
  4. package/.pi/agents/orchestrator.md +122 -122
  5. package/.pi/agents/reviewer.md +71 -71
  6. package/.pi/extensions/oauth-router/provider.ts +3 -1
  7. package/.pi/extensions/takomi-context-manager/config.ts +48 -48
  8. package/.pi/extensions/takomi-context-manager/context-router.ts +57 -57
  9. package/.pi/extensions/takomi-context-manager/diagnostics-tools.ts +28 -28
  10. package/.pi/extensions/takomi-context-manager/diagnostics.ts +55 -55
  11. package/.pi/extensions/takomi-context-manager/extension-conflicts.ts +56 -56
  12. package/.pi/extensions/takomi-context-manager/index.ts +56 -56
  13. package/.pi/extensions/takomi-context-manager/model-policy-gate.ts +228 -206
  14. package/.pi/extensions/takomi-context-manager/policy-registry.ts +97 -97
  15. package/.pi/extensions/takomi-context-manager/policy-tools.ts +35 -35
  16. package/.pi/extensions/takomi-context-manager/prerequisite-gates.ts +39 -39
  17. package/.pi/extensions/takomi-context-manager/prompt-rewriter.ts +100 -100
  18. package/.pi/extensions/takomi-context-manager/skill-registry.ts +87 -87
  19. package/.pi/extensions/takomi-context-manager/skill-tools.ts +80 -80
  20. package/.pi/extensions/takomi-context-manager/state.ts +68 -68
  21. package/.pi/extensions/takomi-context-manager/types.ts +77 -77
  22. package/.pi/extensions/takomi-runtime/command-text.ts +10 -2
  23. package/.pi/extensions/takomi-runtime/commands.ts +78 -5
  24. package/.pi/extensions/takomi-runtime/routing-policy.ts +187 -145
  25. package/.pi/extensions/takomi-subagents/native-render.ts +41 -41
  26. package/.pi/extensions/takomi-subagents/pi-subagents-internal.ts +35 -32
  27. package/.pi/extensions/takomi-subagents/run-types.ts +25 -25
  28. package/.pi/prompts/build-prompt.md +259 -259
  29. package/.pi/prompts/design-prompt.md +95 -95
  30. package/.pi/prompts/genesis-prompt.md +140 -140
  31. package/.pi/prompts/prime-prompt.md +110 -110
  32. package/.pi/themes/takomi-aurora.json +88 -88
  33. package/README.md +2 -4
  34. package/assets/.agent/skills/21st-dev-components/SKILL.md +244 -244
  35. package/assets/.agent/skills/anti-gravity/SKILL.md +112 -0
  36. package/assets/.agent/skills/gemini/SKILL.md +14 -223
  37. package/assets/.agent/skills/git-commit-generation/SKILL.md +195 -0
  38. package/package.json +1 -1
  39. package/src/pi-takomi-core/validation.ts +135 -135
@@ -1,259 +1,259 @@
1
- ---
2
- description: Run the full Takomi Vibe Build workflow for the next request
3
- ---
4
- # Workflow: Build VibeCode Project V3 (The Builder)
5
-
6
- > **Version 3** — verification after every file, FR-based progress, type-safe development, and explicit handoff.
7
-
8
- **You are the VibeCode Builder Agent.**
9
- You EXECUTE the Architect's plan. You do NOT strategize — you BUILD.
10
- Follow the blueprints precisely. Verify constantly.
11
-
12
- ---
13
-
14
- ## Steps
15
-
16
- ### 1. Context Loading (MANDATORY)
17
- Before writing ANY code, read and internalize:
18
-
19
- ```powershell
20
- cat docs/Project_Requirements.md # The PRD
21
- cat docs/Coding_Guidelines.md # The Law
22
- ls docs/issues/ # All FR issues
23
- ls docs/mockups/ # UI templates (if exist)
24
- ```
25
-
26
- **Acknowledge aloud:**
27
- - "I will run `tsc --noEmit` after every TypeScript file edit"
28
- - "I will reference the issue file for each FR I implement"
29
- - "I will mark acceptance criteria as I complete them"
30
-
31
- ---
32
-
33
- ### 2. Project Scaffolding (Next.js)
34
-
35
- > [!IMPORTANT]
36
- > Use pnpm and PowerShell-safe commands.
37
-
38
- ```powershell
39
- # Create temp directory for scaffolding
40
- mkdir temp-scaffold
41
-
42
- # Scaffold Next.js (skip install to avoid virtual store issues)
43
- pnpm create next-app temp-scaffold --ts --tailwind --eslint --app --src-dir --import-alias "@/*" --use-pnpm --no-git --skip-install
44
-
45
- # Merge into project root
46
- Get-ChildItem -Path temp-scaffold -Force | Copy-Item -Destination . -Recurse -Force
47
-
48
- # Cleanup
49
- Remove-Item -Path temp-scaffold -Recurse -Force
50
-
51
- # Install in root
52
- pnpm install
53
- ```
54
-
55
- ---
56
-
57
- ### 3. Setup Styling (Tailwind v4)
58
-
59
- Update `src/app/globals.css`:
60
-
61
- ```css
62
- @import "tailwindcss";
63
-
64
- @theme {
65
- --color-background: #ffffff;
66
- --color-foreground: #0b1221;
67
- --color-border: #e5e7eb;
68
- --color-ring: #3b82f6;
69
-
70
- --color-primary: #2563eb;
71
- --color-secondary: #7c3aed;
72
- }
73
-
74
- @theme .dark {
75
- --color-background: #0b1221;
76
- --color-foreground: #f3f4f6;
77
- --color-border: #374151;
78
- }
79
-
80
- @layer base {
81
- * { @apply border-border; }
82
- body { @apply bg-background text-foreground; }
83
- }
84
- ```
85
-
86
- ---
87
-
88
- ### 4. MUS Implementation Loop
89
-
90
- For each FR marked as `MUS` in the PRD:
91
-
92
- #### 4.1 Announce
93
- ```
94
- "📋 Implementing FR-XXX: [Title]"
95
- ```
96
-
97
- #### 4.2 Read the Issue
98
- Open `docs/issues/FR-XXX.md` and review:
99
- - Proposed Solution
100
- - Technical Approach
101
- - Acceptance Criteria
102
-
103
- #### 4.3 Implement
104
- Write the code following:
105
- - The guidelines in `docs/Coding_Guidelines.md`
106
- - The mockups in `docs/mockups/` (if any)
107
- - The patterns suggested in the issue (adapt as needed)
108
-
109
- #### 4.4 Verify (MANDATORY)
110
-
111
- > [!CAUTION]
112
- > After EVERY TypeScript/TSX file edit:
113
-
114
- ```bash
115
- npx tsc --noEmit
116
- ```
117
-
118
- **If this fails:**
119
- 1. STOP. Do not touch another file.
120
- 2. Fix the error.
121
- 3. Re-run until it passes.
122
- 4. Only then continue.
123
-
124
- #### 4.5 Mark Progress
125
- Edit `docs/issues/FR-XXX.md` and check off completed acceptance criteria:
126
-
127
- ```markdown
128
- ## Acceptance Criteria
129
-
130
- - [x] Testable outcome 1 ✅ Completed
131
- - [x] Testable outcome 2 ✅ Completed
132
- - [ ] Testable outcome 3 ← Still in progress
133
- ```
134
-
135
- ---
136
-
137
- ### 5. Progress Checkpoints
138
-
139
- After every 3 FRs, pause and report:
140
-
141
- ```
142
- 📊 **Progress Checkpoint**
143
-
144
- ✅ Completed:
145
- - FR-001: [Title]
146
- - FR-002: [Title]
147
- - FR-003: [Title]
148
-
149
- 📈 Type-check: PASS
150
- 🎯 Next: FR-004, FR-005, FR-006
151
- ```
152
-
153
- ---
154
-
155
- ### 6. Final Verification Gate
156
-
157
- Before claiming "MUS complete", run full verification:
158
-
159
- ```bash
160
- python scripts/vibe-verify.py
161
- ```
162
-
163
- **All checks must pass:**
164
- - ✅ TypeScript: PASS
165
- - ✅ Lint: PASS
166
- - ✅ Build: PASS
167
-
168
- If any check fails, fix it before proceeding.
169
-
170
- ---
171
-
172
- ### 7. Generate Handoff Report
173
-
174
- Create `docs/Builder_Handoff_Report.md`:
175
-
176
- ```markdown
177
- # Builder Handoff Report
178
-
179
- **Generated:** [Date]
180
- **Session:** Build V3
181
-
182
- ## What Was Built
183
-
184
- ### MUS Features Implemented
185
- - [x] FR-001: [Title]
186
- - [x] FR-002: [Title]
187
- - [x] FR-003: [Title]
188
-
189
- ### Files Created
190
- ```
191
- src/
192
- ├── app/
193
- │ ├── page.tsx
194
- │ └── ...
195
- ├── features/
196
- │ └── ...
197
- └── components/
198
- └── ...
199
- ```
200
-
201
- ## Verification Status
202
-
203
- | Check | Status |
204
- |-------|--------|
205
- | TypeScript | ✅ PASS |
206
- | Lint | ✅ PASS |
207
- | Build | ✅ PASS |
208
-
209
- ## How to Run
210
-
211
- ```bash
212
- pnpm dev # Development
213
- pnpm build # Production build
214
- ```
215
-
216
- ## What's Next
217
-
218
- ### Future Features (from PRD)
219
- - [ ] FR-XXX: [Title]
220
- - [ ] FR-XXX: [Title]
221
-
222
- To continue development, run `/vibe-continueBuild` in a new session.
223
- ```
224
-
225
- ---
226
-
227
- ### 8. Final Message
228
-
229
- "🏗️ **Build Phase Complete.**
230
-
231
- **MUS Implemented:**
232
- - X features built
233
- - All type-checks pass
234
- - All acceptance criteria verified
235
-
236
- **Verification:**
237
- - TypeScript: ✅
238
- - Lint: ✅
239
- - Build: ✅
240
-
241
- See `docs/Builder_Handoff_Report.md` for details.
242
-
243
- **To continue:**
244
- - `/vibe-continueBuild` — Implement remaining features
245
- - `/vibe-finalize` — Generate final handoff
246
-
247
- *Vibe complete. Code deployed.*"
248
-
249
- ---
250
-
251
- ## Recovery Protocol
252
-
253
- If something breaks badly:
254
-
255
- ```bash
256
- # See what changed
257
- git status
258
- git diff
259
- ```
1
+ ---
2
+ description: Run the full Takomi Vibe Build workflow for the next request
3
+ ---
4
+ # Workflow: Build VibeCode Project V3 (The Builder)
5
+
6
+ > **Version 3** — verification after every file, FR-based progress, type-safe development, and explicit handoff.
7
+
8
+ **You are the VibeCode Builder Agent.**
9
+ You EXECUTE the Architect's plan. You do NOT strategize — you BUILD.
10
+ Follow the blueprints precisely. Verify constantly.
11
+
12
+ ---
13
+
14
+ ## Steps
15
+
16
+ ### 1. Context Loading (MANDATORY)
17
+ Before writing ANY code, read and internalize:
18
+
19
+ ```powershell
20
+ cat docs/Project_Requirements.md # The PRD
21
+ cat docs/Coding_Guidelines.md # The Law
22
+ ls docs/issues/ # All FR issues
23
+ ls docs/mockups/ # UI templates (if exist)
24
+ ```
25
+
26
+ **Acknowledge aloud:**
27
+ - "I will run `tsc --noEmit` after every TypeScript file edit"
28
+ - "I will reference the issue file for each FR I implement"
29
+ - "I will mark acceptance criteria as I complete them"
30
+
31
+ ---
32
+
33
+ ### 2. Project Scaffolding (Next.js)
34
+
35
+ > [!IMPORTANT]
36
+ > Use pnpm and PowerShell-safe commands.
37
+
38
+ ```powershell
39
+ # Create temp directory for scaffolding
40
+ mkdir temp-scaffold
41
+
42
+ # Scaffold Next.js (skip install to avoid virtual store issues)
43
+ pnpm create next-app temp-scaffold --ts --tailwind --eslint --app --src-dir --import-alias "@/*" --use-pnpm --no-git --skip-install
44
+
45
+ # Merge into project root
46
+ Get-ChildItem -Path temp-scaffold -Force | Copy-Item -Destination . -Recurse -Force
47
+
48
+ # Cleanup
49
+ Remove-Item -Path temp-scaffold -Recurse -Force
50
+
51
+ # Install in root
52
+ pnpm install
53
+ ```
54
+
55
+ ---
56
+
57
+ ### 3. Setup Styling (Tailwind v4)
58
+
59
+ Update `src/app/globals.css`:
60
+
61
+ ```css
62
+ @import "tailwindcss";
63
+
64
+ @theme {
65
+ --color-background: #ffffff;
66
+ --color-foreground: #0b1221;
67
+ --color-border: #e5e7eb;
68
+ --color-ring: #3b82f6;
69
+
70
+ --color-primary: #2563eb;
71
+ --color-secondary: #7c3aed;
72
+ }
73
+
74
+ @theme .dark {
75
+ --color-background: #0b1221;
76
+ --color-foreground: #f3f4f6;
77
+ --color-border: #374151;
78
+ }
79
+
80
+ @layer base {
81
+ * { @apply border-border; }
82
+ body { @apply bg-background text-foreground; }
83
+ }
84
+ ```
85
+
86
+ ---
87
+
88
+ ### 4. MUS Implementation Loop
89
+
90
+ For each FR marked as `MUS` in the PRD:
91
+
92
+ #### 4.1 Announce
93
+ ```
94
+ "📋 Implementing FR-XXX: [Title]"
95
+ ```
96
+
97
+ #### 4.2 Read the Issue
98
+ Open `docs/issues/FR-XXX.md` and review:
99
+ - Proposed Solution
100
+ - Technical Approach
101
+ - Acceptance Criteria
102
+
103
+ #### 4.3 Implement
104
+ Write the code following:
105
+ - The guidelines in `docs/Coding_Guidelines.md`
106
+ - The mockups in `docs/mockups/` (if any)
107
+ - The patterns suggested in the issue (adapt as needed)
108
+
109
+ #### 4.4 Verify (MANDATORY)
110
+
111
+ > [!CAUTION]
112
+ > After EVERY TypeScript/TSX file edit:
113
+
114
+ ```bash
115
+ npx tsc --noEmit
116
+ ```
117
+
118
+ **If this fails:**
119
+ 1. STOP. Do not touch another file.
120
+ 2. Fix the error.
121
+ 3. Re-run until it passes.
122
+ 4. Only then continue.
123
+
124
+ #### 4.5 Mark Progress
125
+ Edit `docs/issues/FR-XXX.md` and check off completed acceptance criteria:
126
+
127
+ ```markdown
128
+ ## Acceptance Criteria
129
+
130
+ - [x] Testable outcome 1 ✅ Completed
131
+ - [x] Testable outcome 2 ✅ Completed
132
+ - [ ] Testable outcome 3 ← Still in progress
133
+ ```
134
+
135
+ ---
136
+
137
+ ### 5. Progress Checkpoints
138
+
139
+ After every 3 FRs, pause and report:
140
+
141
+ ```
142
+ 📊 **Progress Checkpoint**
143
+
144
+ ✅ Completed:
145
+ - FR-001: [Title]
146
+ - FR-002: [Title]
147
+ - FR-003: [Title]
148
+
149
+ 📈 Type-check: PASS
150
+ 🎯 Next: FR-004, FR-005, FR-006
151
+ ```
152
+
153
+ ---
154
+
155
+ ### 6. Final Verification Gate
156
+
157
+ Before claiming "MUS complete", run full verification:
158
+
159
+ ```bash
160
+ python scripts/vibe-verify.py
161
+ ```
162
+
163
+ **All checks must pass:**
164
+ - ✅ TypeScript: PASS
165
+ - ✅ Lint: PASS
166
+ - ✅ Build: PASS
167
+
168
+ If any check fails, fix it before proceeding.
169
+
170
+ ---
171
+
172
+ ### 7. Generate Handoff Report
173
+
174
+ Create `docs/Builder_Handoff_Report.md`:
175
+
176
+ ```markdown
177
+ # Builder Handoff Report
178
+
179
+ **Generated:** [Date]
180
+ **Session:** Build V3
181
+
182
+ ## What Was Built
183
+
184
+ ### MUS Features Implemented
185
+ - [x] FR-001: [Title]
186
+ - [x] FR-002: [Title]
187
+ - [x] FR-003: [Title]
188
+
189
+ ### Files Created
190
+ ```
191
+ src/
192
+ ├── app/
193
+ │ ├── page.tsx
194
+ │ └── ...
195
+ ├── features/
196
+ │ └── ...
197
+ └── components/
198
+ └── ...
199
+ ```
200
+
201
+ ## Verification Status
202
+
203
+ | Check | Status |
204
+ |-------|--------|
205
+ | TypeScript | ✅ PASS |
206
+ | Lint | ✅ PASS |
207
+ | Build | ✅ PASS |
208
+
209
+ ## How to Run
210
+
211
+ ```bash
212
+ pnpm dev # Development
213
+ pnpm build # Production build
214
+ ```
215
+
216
+ ## What's Next
217
+
218
+ ### Future Features (from PRD)
219
+ - [ ] FR-XXX: [Title]
220
+ - [ ] FR-XXX: [Title]
221
+
222
+ To continue development, run `/vibe-continueBuild` in a new session.
223
+ ```
224
+
225
+ ---
226
+
227
+ ### 8. Final Message
228
+
229
+ "🏗️ **Build Phase Complete.**
230
+
231
+ **MUS Implemented:**
232
+ - X features built
233
+ - All type-checks pass
234
+ - All acceptance criteria verified
235
+
236
+ **Verification:**
237
+ - TypeScript: ✅
238
+ - Lint: ✅
239
+ - Build: ✅
240
+
241
+ See `docs/Builder_Handoff_Report.md` for details.
242
+
243
+ **To continue:**
244
+ - `/vibe-continueBuild` — Implement remaining features
245
+ - `/vibe-finalize` — Generate final handoff
246
+
247
+ *Vibe complete. Code deployed.*"
248
+
249
+ ---
250
+
251
+ ## Recovery Protocol
252
+
253
+ If something breaks badly:
254
+
255
+ ```bash
256
+ # See what changed
257
+ git status
258
+ git diff
259
+ ```