@vpxa/aikit 0.1.63 → 0.1.65

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 (47) hide show
  1. package/README.md +41 -1
  2. package/package.json +2 -2
  3. package/packages/cli/dist/constants-BjDyZo-l.js +1 -0
  4. package/packages/cli/dist/index.js +4 -4
  5. package/packages/cli/dist/{init-C0VZ6PkG.js → init-DBo2fDoM.js} +1 -1
  6. package/packages/cli/dist/{user-CDSf9aCI.js → user-CXIL0rVI.js} +1 -1
  7. package/packages/flows/dist/index.d.ts +111 -11
  8. package/packages/flows/dist/index.js +2 -2
  9. package/packages/indexer/dist/index.js +1 -1
  10. package/packages/server/dist/index.js +1 -1
  11. package/packages/server/dist/{server-BlBBxAQO.js → server-DFqOZEJC.js} +165 -165
  12. package/scaffold/definitions/agents.mjs +5 -0
  13. package/scaffold/definitions/bodies.mjs +65 -17
  14. package/scaffold/definitions/plugins.mjs +6 -0
  15. package/scaffold/definitions/protocols.mjs +7 -2
  16. package/scaffold/flows/_epilogue/steps/docs-sync/README.md +120 -0
  17. package/scaffold/flows/aikit-advanced/README.md +1 -1
  18. package/scaffold/flows/aikit-advanced/steps/execute/README.md +4 -4
  19. package/scaffold/flows/aikit-advanced/steps/plan/README.md +4 -4
  20. package/scaffold/flows/aikit-advanced/steps/spec/README.md +2 -2
  21. package/scaffold/flows/aikit-advanced/steps/task/README.md +4 -4
  22. package/scaffold/flows/aikit-advanced/steps/verify/README.md +7 -7
  23. package/scaffold/flows/aikit-basic/README.md +1 -1
  24. package/scaffold/flows/aikit-basic/steps/assess/README.md +2 -2
  25. package/scaffold/flows/aikit-basic/steps/implement/README.md +4 -4
  26. package/scaffold/flows/aikit-basic/steps/verify/README.md +4 -4
  27. package/scaffold/general/agents/Debugger.agent.md +8 -3
  28. package/scaffold/general/agents/Documenter.agent.md +46 -6
  29. package/scaffold/general/agents/Frontend.agent.md +7 -2
  30. package/scaffold/general/agents/Implementer.agent.md +8 -3
  31. package/scaffold/general/agents/Orchestrator.agent.md +25 -11
  32. package/scaffold/general/agents/Planner.agent.md +7 -2
  33. package/scaffold/general/agents/Refactor.agent.md +7 -2
  34. package/scaffold/general/agents/Security.agent.md +7 -2
  35. package/scaffold/general/agents/_shared/code-agent-base.md +7 -2
  36. package/scaffold/general/skills/aikit/SKILL.md +52 -15
  37. package/scaffold/general/skills/docs/SKILL.md +509 -0
  38. package/scaffold/general/skills/docs/references/diataxis-anti-patterns.md +147 -0
  39. package/scaffold/general/skills/docs/references/diataxis-compass.md +123 -0
  40. package/scaffold/general/skills/docs/references/diataxis-quadrants.md +192 -0
  41. package/scaffold/general/skills/docs/references/diataxis-quality.md +76 -0
  42. package/scaffold/general/skills/docs/references/diataxis-templates.md +120 -0
  43. package/scaffold/general/skills/docs/references/flow-artifacts-guide.md +70 -0
  44. package/scaffold/general/skills/docs/references/project-knowledge-gotchas.md +32 -0
  45. package/scaffold/general/skills/docs/references/project-knowledge-templates.md +281 -0
  46. package/scaffold/general/skills/docs/references/project-knowledge-workflow.md +80 -0
  47. package/packages/cli/dist/constants-D3v4VDf0.js +0 -1
@@ -0,0 +1,281 @@
1
+ # Project Knowledge Templates
2
+
3
+ Templates for the seven project knowledge documents in `docs/architecture/`. Use these to ensure consistent structure across projects.
4
+
5
+ ## stack.md
6
+
7
+ ```markdown
8
+ # Stack
9
+
10
+ ## Language and Runtime
11
+
12
+ | Item | Version | Notes |
13
+ |------|---------|-------|
14
+ | {language} | {version} | {notes} |
15
+
16
+ ## Frameworks
17
+
18
+ | Framework | Version | Role |
19
+ |-----------|---------|------|
20
+ | {name} | {version} | {role} |
21
+
22
+ ## Production Dependencies
23
+
24
+ | Package | Version | Purpose |
25
+ |---------|---------|---------|
26
+ | {name} | {version} | {purpose} |
27
+
28
+ ## Dev Tooling
29
+
30
+ | Tool | Version | Purpose |
31
+ |------|---------|---------|
32
+ | {name} | {version} | {purpose} |
33
+
34
+ ## Evidence
35
+
36
+ - `package.json` / `requirements.txt` / `go.mod` — dependency versions
37
+ - `tsconfig.json` / `pyproject.toml` — language configuration
38
+ ```
39
+
40
+ ## structure.md
41
+
42
+ ```markdown
43
+ # Structure
44
+
45
+ ## Directory Layout
46
+
47
+ ```
48
+ {root}/
49
+ ├── {dir}/ ← {purpose}
50
+ │ └── ...
51
+ └── {dir}/ ← {purpose}
52
+ ```
53
+
54
+ ## Entry Points
55
+
56
+ | Entry Point | Path | Type |
57
+ |-------------|------|------|
58
+ | {name} | `{path}` | CLI / HTTP / Library |
59
+
60
+ ## Key Files
61
+
62
+ | File | Purpose |
63
+ |------|---------|
64
+ | `{path}` | {purpose} |
65
+
66
+ ## Packages (monorepo only)
67
+
68
+ | Package | Path | Purpose |
69
+ |---------|------|---------|
70
+ | {name} | `{path}` | {purpose} |
71
+
72
+ ## Evidence
73
+
74
+ - `analyze_structure` output — directory tree
75
+ - `analyze_entry_points` output — entry points
76
+ ```
77
+
78
+ ## design.md
79
+
80
+ ```markdown
81
+ # Design
82
+
83
+ ## Architectural Pattern
84
+
85
+ {Pattern name} — {one-sentence description of how it applies here}.
86
+
87
+ ## Layers
88
+
89
+ | Layer | Directory | Responsibility |
90
+ |-------|-----------|----------------|
91
+ | {name} | `{path}` | {responsibility} |
92
+
93
+ ## Data Flow
94
+
95
+ ```
96
+ {source} → {transform} → {destination}
97
+ ```
98
+
99
+ {Brief description of primary data paths.}
100
+
101
+ ## Component Boundaries
102
+
103
+ | Component | Owns | Depends On |
104
+ |-----------|------|------------|
105
+ | {name} | {responsibility} | {dependencies} |
106
+
107
+ ## Key Patterns
108
+
109
+ | Pattern | Where Used | Purpose |
110
+ |---------|-----------|---------|
111
+ | {name} | `{path}` | {purpose} |
112
+
113
+ ## Evidence
114
+
115
+ - `analyze_structure` output — layers
116
+ - `analyze_patterns` output — design patterns
117
+ - `analyze_diagram` output — component diagrams
118
+ ```
119
+
120
+ ## conventions.md
121
+
122
+ ```markdown
123
+ # Conventions
124
+
125
+ ## Naming
126
+
127
+ | Element | Convention | Example |
128
+ |---------|-----------|---------|
129
+ | Files | {convention} | `{example}` |
130
+ | Functions | {convention} | `{example}` |
131
+ | Types/Interfaces | {convention} | `{example}` |
132
+ | Constants | {convention} | `{example}` |
133
+
134
+ ## Formatting
135
+
136
+ - Formatter: {tool} with {config file}
137
+ - Linter: {tool} with {config file}
138
+ - Line length: {limit}
139
+ - Indentation: {style}
140
+
141
+ ## Error Handling
142
+
143
+ {Describe the project's error handling pattern: throw/catch, Result type, error codes, etc.}
144
+
145
+ ## Import Conventions
146
+
147
+ | Import Type | Convention | Example |
148
+ |-------------|-----------|---------|
149
+ | Internal | {pattern} | `{example}` |
150
+ | External | {pattern} | `{example}` |
151
+ | Type-only | {pattern} | `{example}` |
152
+
153
+ ## Evidence
154
+
155
+ - `analyze_patterns` output — detected conventions
156
+ - Linter/formatter config files — enforced rules
157
+ ```
158
+
159
+ ## integrations.md
160
+
161
+ ```markdown
162
+ # Integrations
163
+
164
+ ## External APIs
165
+
166
+ | Service | Protocol | Auth | Config |
167
+ |---------|----------|------|--------|
168
+ | {name} | REST / gRPC / GraphQL | {auth method} | `{env var or config}` |
169
+
170
+ ## Databases
171
+
172
+ | Database | Driver | Connection | Usage |
173
+ |----------|--------|------------|-------|
174
+ | {name} | {driver package} | `{env var}` | {what it stores} |
175
+
176
+ ## Authentication
177
+
178
+ {Describe auth mechanism: JWT, OAuth, API keys, sessions, etc.}
179
+
180
+ ## Monitoring and Observability
181
+
182
+ | Tool | Purpose | Config |
183
+ |------|---------|--------|
184
+ | {name} | Logging / Metrics / Tracing | `{config}` |
185
+
186
+ ## CI/CD
187
+
188
+ | Platform | Config | Stages |
189
+ |----------|--------|--------|
190
+ | {name} | `{config file}` | {stages} |
191
+
192
+ ## Evidence
193
+
194
+ - `analyze_dependencies` output — external packages
195
+ - `.env.example` — required environment variables
196
+ - CI config files — pipeline definitions
197
+ ```
198
+
199
+ ## testing.md
200
+
201
+ ```markdown
202
+ # Testing
203
+
204
+ ## Framework
205
+
206
+ | Tool | Version | Purpose |
207
+ |------|---------|---------|
208
+ | {name} | {version} | Unit / Integration / E2E |
209
+
210
+ ## File Organization
211
+
212
+ | Pattern | Location | Example |
213
+ |---------|----------|---------|
214
+ | {convention} | `{path}` | `{example file}` |
215
+
216
+ ## Mocking Strategy
217
+
218
+ {Describe how mocks are created and used: manual, library, DI, etc.}
219
+
220
+ ## Coverage
221
+
222
+ - Target: {percentage or policy}
223
+ - Tool: {coverage tool}
224
+ - Config: `{config file}`
225
+
226
+ ## Running Tests
227
+
228
+ ```bash
229
+ {command to run all tests}
230
+ {command to run specific tests}
231
+ {command to run with coverage}
232
+ ```
233
+
234
+ ## Evidence
235
+
236
+ - `analyze_patterns` output — test patterns
237
+ - `test_run({})` output — test health
238
+ - Test config files — framework configuration
239
+ ```
240
+
241
+ ## concerns.md
242
+
243
+ ```markdown
244
+ # Concerns
245
+
246
+ ## Tech Debt
247
+
248
+ | Area | Description | Severity | Evidence |
249
+ |------|-------------|----------|----------|
250
+ | {area} | {description} | High / Medium / Low | `{file or tool}` |
251
+
252
+ ## Known Issues
253
+
254
+ | Issue | Impact | Workaround |
255
+ |-------|--------|------------|
256
+ | {issue} | {impact} | {workaround or "None"} |
257
+
258
+ ## Security Risks
259
+
260
+ | Risk | Severity | Mitigation |
261
+ |------|----------|------------|
262
+ | {risk} | {severity} | {mitigation} |
263
+
264
+ ## Performance Bottlenecks
265
+
266
+ | Area | Symptom | Evidence |
267
+ |------|---------|----------|
268
+ | {area} | {symptom} | `{file or metric}` |
269
+
270
+ ## High-Churn Files
271
+
272
+ | File | Recent Changes | Why |
273
+ |------|---------------|-----|
274
+ | `{path}` | {change count} | {reason} |
275
+
276
+ ## Evidence
277
+
278
+ - `audit()` output — health issues
279
+ - `dead_symbols({})` output — dead code
280
+ - `git_context({})` output — high-churn files
281
+ ```
@@ -0,0 +1,80 @@
1
+ # Project Knowledge — Workflow
2
+
3
+ Detailed workflow for acquiring and documenting project knowledge into `docs/architecture/`.
4
+
5
+ ## Four-Phase Workflow
6
+
7
+ ```
8
+ - [ ] Phase 1: Scan with AI Kit tools, read intent documents
9
+ - [ ] Phase 2: Investigate each documentation area
10
+ - [ ] Phase 3: Populate all seven docs in docs/architecture/
11
+ - [ ] Phase 4: Validate docs, present findings, resolve all [ASK USER] items
12
+ ```
13
+
14
+ ### Phase 1: Scan and Read Intent
15
+
16
+ ```
17
+ onboard({ path: "." }) # Full codebase scan
18
+ produce_knowledge({ path: "." }) # Comprehensive analysis
19
+ analyze_structure({ path: "." }) # Project layout, packages, layers
20
+ analyze_dependencies({ path: "." }) # All dependencies + import graph
21
+ ```
22
+
23
+ Then read `README`, `PRD`, `TRD`, `ROADMAP`, `SPEC`, `DESIGN` files if they exist.
24
+ Summarise the stated project intent before reading any source code.
25
+
26
+ ### Phase 2: Investigate
27
+
28
+ Use Phase 1 tool outputs to answer questions for each of the seven documents. Run additional targeted tools:
29
+
30
+ | Document | Investigation Tools |
31
+ |----------|-------------------|
32
+ | stack.md | `analyze_dependencies` → manifests, frameworks; `analyze_structure` → runtime signals |
33
+ | structure.md | `analyze_structure` → file tree, packages; `analyze_entry_points` → entry points, key files |
34
+ | design.md | `analyze_structure` → layers; `analyze_patterns` → design patterns; `analyze_diagram` → component diagrams |
35
+ | conventions.md | `analyze_patterns` → naming, formatting; `search("conventions")` → detected conventions |
36
+ | integrations.md | `analyze_dependencies` → external deps; `search("API\|database\|auth\|webhook")` → integration points |
37
+ | testing.md | `analyze_patterns` → test patterns; `search("test framework")` → test setup; `test_run({})` → test health |
38
+ | concerns.md | `audit({ path: "." })` → health issues; `dead_symbols({})` → dead code; `git_context({})` → high-churn files |
39
+
40
+ ### Phase 3: Populate Documents
41
+
42
+ Create each document in `docs/architecture/` in this order:
43
+
44
+ 1. **stack.md** — Language, runtime version, frameworks, production dependencies, dev tooling
45
+ 2. **structure.md** — Directory layout, entry points, key files, package organization
46
+ 3. **design.md** — Layers, architectural patterns, data flow, component boundaries
47
+ 4. **conventions.md** — Naming conventions, formatting rules, error handling patterns, import conventions
48
+ 5. **integrations.md** — External APIs, databases, auth providers, monitoring, CI/CD
49
+ 6. **testing.md** — Test frameworks, file organization, mocking strategy, coverage approach
50
+ 7. **concerns.md** — Tech debt, known bugs, security risks, performance bottlenecks, high-churn files
51
+
52
+ Rules:
53
+ - Use `[TODO]` for anything that cannot be determined from code
54
+ - Use `[ASK USER]` where the right answer requires team intent
55
+ - Include an "Evidence" section in each doc with file paths and tool receipts
56
+
57
+ ### Phase 4: Validate, Repair, Verify
58
+
59
+ Run this mandatory validation loop before finalizing:
60
+
61
+ 1. For each non-trivial claim, confirm at least one evidence reference exists
62
+ 2. If any required section is missing or unsupported → fix and re-validate
63
+ 3. Repeat until all seven docs pass
64
+
65
+ Validation pass criteria:
66
+ - No unsupported claims
67
+ - No empty required sections
68
+ - Unknowns use `[TODO]` rather than assumptions
69
+ - Team-intent gaps are explicitly marked `[ASK USER]`
70
+
71
+ Then present a summary, list every `[ASK USER]` item as a numbered question, and highlight any Intent vs. Reality divergences from Phase 1.
72
+
73
+ ## Focus Area Mode
74
+
75
+ If the user specifies a focus area (e.g., "architecture only" or "testing and concerns"):
76
+
77
+ 1. Always run Phase 1 in full
78
+ 2. Fully complete focus-area documents first
79
+ 3. For non-focus documents, keep required sections present and mark unknowns as `[TODO]`
80
+ 4. Still run the Phase 4 validation loop on all seven documents
@@ -1 +0,0 @@
1
- const e=`aikit`,t={type:`stdio`,command:`npx`,args:[`-y`,`@vpxa/aikit`,`serve`]},n=[`aikit`,`brainstorming`,`multi-agents-development`,`session-handoff`,`requirements-clarity`,`lesson-learned`,`c4-architecture`,`adr-skill`,`present`,`frontend-design`,`react`,`typescript`],r=[`aikit-basic`,`aikit-advanced`],i={"chat.agentFilesLocations":{"~/.claude/agents":!1},"github.copilot.chat.copilotMemory.enabled":!0,"chat.customAgentInSubagent.enabled":!0,"chat.useNestedAgentsMdFiles":!0,"chat.useAgentSkills":!0,"github.copilot.chat.switchAgent.enabled":!0,"workbench.browser.enableChatTools":!0,"chat.mcp.apps.enabled":!0,"chat.instructionsFilesLocations":{"~/.copilot/instructions":!0,".github/instructions":!0}};export{i as a,n as i,t as n,e as r,r as t};