@vpxa/aikit 0.1.355 → 0.1.356

package/scaffold/dist/definitions/prompts.mjs

@@ -1,11 +1,11 @@
-const e={ask:{description:`Quick research question — find answer using AI Kit + web search`,agent:`Researcher-Alpha`,tools:[`search`,`web_search`,`web_fetch`,`knowledge`,`present`],content:`## Quick Research
+const e={ask:{description:`Quick research question — find answer using AI Kit + web search`,agent:`Researcher-Alpha`,intent:`Quick research question using AI Kit + web search`,tools:[`search`,`web_search`,`web_fetch`,`knowledge`,`present`],content:`## Quick Research
 
 1. **AI Kit Recall** — Search the AI Kit index for existing answers
 2. **Web Search** — If AI Kit has no relevant results, search the web
 3. **Synthesize** — Combine findings into a clear, concise answer
 4. **Remember** — If the answer is broadly useful, persist it with \`knowledge({ action: "remember", ... })\`
 
-**Always cite sources** — AI Kit entries, file paths, or URLs.`},debug:{description:`Systematic error diagnosis: reproduce → trace → diagnose → fix → verify`,agent:`Debugger`,tools:[`search`,`symbol`,`trace`,`blast_radius`,`check`,`test_run`,`parse_output`,`knowledge`,`present`],content:'## Debug Workflow\n\n1. **Parse Error** — Use `parse_output` on the error message/stack trace\n2. **AI Kit Recall** — Search for known issues matching this pattern\n3. **Reproduce** — Run the failing command/test to confirm\n4. **Trace** — Use `symbol` and `trace` to follow the call chain\n5. **Diagnose** — Form hypothesis, gather evidence\n6. **Fix** — Implement minimal fix\n7. **Verify** — `check` + `test_run` to confirm fix and no regressions\n8. **Remember** — Persist the fix with `knowledge({ action: "remember", category: "troubleshooting", ... })`'},implement:{description:`Full lifecycle implementation: plan → build → review → commit`,agent:`Orchestrator`,tools:[`search`,`scope_map`,`forge_ground`,`check`,`test_run`,`blast_radius`,`knowledge`,`audit`,`present`],content:`## Implementation Pipeline
+**Always cite sources** — AI Kit entries, file paths, or URLs.`},debug:{description:`Systematic error diagnosis: reproduce → trace → diagnose → fix → verify`,agent:`Debugger`,tools:[`search`,`symbol`,`trace`,`blast_radius`,`check`,`test_run`,`parse_output`,`knowledge`,`present`],intent:`Systematic error diagnosis and fix workflow`,content:'## Debug Workflow\n\n1. **Parse Error** — Use `parse_output` on the error message/stack trace\n2. **AI Kit Recall** — Search for known issues matching this pattern\n3. **Reproduce** — Run the failing command/test to confirm\n4. **Trace** — Use `symbol` and `trace` to follow the call chain\n5. **Diagnose** — Form hypothesis, gather evidence\n6. **Fix** — Implement minimal fix\n7. **Verify** — `check` + `test_run` to confirm fix and no regressions\n8. **Remember** — Persist the fix with `knowledge({ action: "remember", category: "troubleshooting", ... })`'},implement:{description:`Full lifecycle implementation: plan → build → review → commit`,agent:`Orchestrator`,tools:[`search`,`scope_map`,`forge_ground`,`check`,`test_run`,`blast_radius`,`knowledge`,`audit`,`present`],intent:`Full lifecycle implementation with quality gates`,content:`## Implementation Pipeline
 
 Follow the Orchestrator's full workflow:
 
@@ -16,7 +16,7 @@ Follow the Orchestrator's full workflow:
 
 **🛑 MANDATORY STOPS** — After plan, after each batch, after completion.
 
-Refer to the Orchestrator agent's full instructions for the detailed workflow.`},plan:{description:`Create a detailed TDD implementation plan without executing it`,agent:`Planner`,tools:[`search`,`scope_map`,`forge_ground`,`forge_classify`,`file_summary`,`analyze`,`knowledge`,`present`],content:`## Planning Workflow
+Refer to the Orchestrator agent's full instructions for the detailed workflow.`},plan:{description:`Create a detailed TDD implementation plan without executing it`,agent:`Planner`,tools:[`search`,`scope_map`,`forge_ground`,`forge_classify`,`file_summary`,`analyze`,`knowledge`,`present`],intent:`Create detailed TDD implementation plan`,content:`## Planning Workflow
 
 1. **AI Kit Recall** — Search for past plans, architecture decisions
 2. **FORGE Ground** — Classify tier, scope map, seed unknowns
@@ -25,7 +25,7 @@ Refer to the Orchestrator agent's full instructions for the detailed workflow.`}
 5. **Dependency Graph** — Group into parallel batches
 6. **Present** — Show plan with open questions
 
-**🛑 MANDATORY STOP** — Wait for user approval. Do NOT implement.`},design:{description:`Collaborative design session — explore ideas, refine requirements, produce a design spec`,agent:`Orchestrator`,tools:[`search`,`scope_map`,`file_summary`,`knowledge`,`forge_classify`,`present`],content:`## Design Session
+**🛑 MANDATORY STOP** — Wait for user approval. Do NOT implement.`},design:{description:`Collaborative design session — explore ideas, refine requirements, produce a design spec`,agent:`Orchestrator`,intent:`Collaborative design exploration session`,tools:[`search`,`scope_map`,`file_summary`,`knowledge`,`forge_classify`,`present`],content:`## Design Session
 
 Enter Phase 0 (Design Gate) directly — the user is requesting a design session.
 
@@ -34,7 +34,7 @@ Enter Phase 0 (Design Gate) directly — the user is requesting a design session
 3. If Advanced Mode, use the full Multi-Model Decision Protocol (3-phase: research → peer review → verdict, defined in Orchestrator instructions) for unresolved technical choices
 4. Terminal state: brainstorming skill invokes writing-plans skill
 
-**🛑 HARD GATE** — Do NOT skip brainstorming. Do NOT write code. Design first.`},review:{description:`Dual-model code + architecture review pipeline`,agent:`Orchestrator`,tools:[`search`,`blast_radius`,`check`,`test_run`,`analyze`,`knowledge`,`present`],content:`## Review Pipeline
+**🛑 HARD GATE** — Do NOT skip brainstorming. Do NOT write code. Design first.`},review:{description:`Dual-model code + architecture review pipeline`,agent:`Orchestrator`,intent:`Multi-model code and architecture review pipeline`,tools:[`search`,`blast_radius`,`check`,`test_run`,`analyze`,`knowledge`,`present`],content:`## Review Pipeline
 
 ### Step 1: Scope
 Identify changed files and their blast radius.
@@ -52,7 +52,7 @@ Merge findings from both reviewers:
 - **Disagreements**: Contradicting verdicts → present both to user
 
 ### Step 5: Report
-Present unified review with: verdict, findings by severity, recommended actions.`},"flow-add":{description:`Install a new flow from a git URL or local path — with interactive error recovery`,agent:`Orchestrator`,tools:[`flow`,`search`,`present`],content:`## Flow Installation Assistant
+Present unified review with: verdict, findings by severity, recommended actions.`},"flow-add":{description:`Install a new flow from a git URL or local path — with interactive error recovery`,agent:`Orchestrator`,intent:`Install a flow from git URL or local path`,tools:[`flow`,`search`,`present`],content:`## Flow Installation Assistant
 
 Install a development flow from a git repository or local directory.
 
@@ -61,7 +61,7 @@ Provide a git URL or local path:
 - \`https://github.com/org/my-flow.git\`
 - \`git@github.com:org/my-flow.git\`
 - \`./path/to/local/flow\`
-- \`C:\\Users\\name\\flows\\my-flow\`
+- \`C:\\path\\to\\flow\`
 
 ### Workflow
 
@@ -130,7 +130,7 @@ If \`flow({ action: 'add', source })\` succeeds cloning but returns a format/str
 ### Post-Install
 After successful installation:
 - Show the flow name, steps, and description via \`present\`
-- Remind user they can start it with \`flow({ action: 'start', name, topic })\``},"flow-manage":{description:`List, inspect, update, and remove installed flows`,agent:`Orchestrator`,tools:[`flow`,`present`],content:`## Flow Management
+- Remind user they can start it with \`flow({ action: 'start', name, topic })\``},"flow-manage":{description:`List, inspect, update, and remove installed flows`,agent:`Orchestrator`,intent:`List, inspect, update, and remove installed flows`,tools:[`flow`,`present`],content:`## Flow Management
 
 Manage your installed development flows.
 
@@ -148,7 +148,7 @@ Manage your installed development flows.
 1. If no specific action requested, start with \`flow({ action: 'list' })\` and present overview
 2. Use \`present\` to display flow information in a clear table/card format
 3. For updates, warn if there's an active flow that might be affected
-4. For removals, confirm with user before proceeding`},"flow-create":{description:`Create a new flow from scratch or migrate an existing workflow to aikit format`,agent:`Orchestrator`,tools:[`flow`,`search`,`present`],content:`## Flow Creation Assistant
+4. For removals, confirm with user before proceeding`},"flow-create":{description:`Create a new flow from scratch or migrate an existing workflow to aikit format`,agent:`Orchestrator`,intent:`Create or migrate development flows`,tools:[`flow`,`search`,`present`],content:`## Flow Creation Assistant
 
 Create a new development flow or migrate an existing workflow to the aikit flow format.
 
@@ -222,343 +222,14 @@ Each step README should include:
 - **Inputs** — What context/artifacts from prior steps are needed
 - **Instructions** — Detailed steps for the agent to follow
 - **Output** — What artifact(s) to produce and where to save them
-- **Acceptance criteria** — How to know the step is complete`},docs:{description:`Deep codebase understanding — analyze, learn, document, and visualize the entire project as an interactive knowledge graph`,agent:`Orchestrator`,tools:[`onboard`,`analyze`,`audit`,`produce_knowledge`,`graph`,`measure`,`blast_radius`,`search`,`symbol`,`trace`,`dead_symbols`,`file_summary`,`digest`,`knowledge`,`present`,`check`,`test_run`,`git_context`],content:`## Understand & Document — Full Codebase Intelligence
+- **Acceptance criteria** — How to know the step is complete`},docs:{description:`Deep codebase understanding — analyze, learn, document, and visualize the entire project as an interactive knowledge graph`,agent:`Orchestrator`,intent:`Deep codebase understanding and documentation generation`,tools:[`onboard`,`analyze`,`audit`,`produce_knowledge`,`graph`,`measure`,`blast_radius`,`search`,`symbol`,`trace`,`dead_symbols`,`file_summary`,`digest`,`knowledge`,`present`,`check`,`test_run`,`git_context`],content:`## Deep Codebase Understanding Pipeline
 
-Turn this codebase into a deeply understood, richly documented, and visually explorable project.
-"Understand Anything" philosophy: **graphs that teach > graphs that impress.**
+1. **Load the \`docs\` skill** — contains full workflow for analysis, knowledge graph, and documentation generation
+2. **Load the \`c4-architecture\` skill** — for architecture diagrams and interactive viewers
+3. **Check status** — \`status({ includePrelude: true })\` to verify onboard state
+4. **Scan codebase** — \`onboard({ path: ".", update: true })\` if stale, then parallel analyze calls
+5. **For docs > markdown docs**: Follow the docs skill's 4-phase workflow (Scan → Investigate → Populate → Validate)
+6. **For docs > interactive viewers**: Follow docs skill's generation-pipeline.md Phases 4c + 6 for C4/tour HTML generation
+7. **Present results** — Document index, architecture overview, concerns board
 
-This is NOT just documentation generation — it is a full **analyze → understand → learn → document → present** pipeline.
-
-### Phase 1: Deep Scan (parallel analysis)
-
-Run all analysis tools in parallel to build a comprehensive baseline:
-
-1. **Onboard** — \`onboard({ path: "." })\` if not already done (check \`status()\` first)
-2. **Structure** — \`analyze({ items: [{aspect: "structure", path: "."}] })\`
-3. **Dependencies** — \`analyze({ items: [{aspect: "dependencies", path: "."}] })\`
-4. **Symbols** — \`analyze({ items: [{aspect: "symbols", path: "."}] })\`
-5. **Patterns** — \`analyze({ items: [{aspect: "patterns", path: "."}] })\`
-6. **Entry Points** — \`analyze({ items: [{aspect: "entry_points", path: "."}] })\`
-7. **Diagrams** — \`analyze({ items: [{aspect: "diagram", path: "."}] })\`
-8. **Health Audit** — \`audit({ path: "." })\`
-9. **Complexity** — \`measure({ path: "." })\`
-10. **Git Context** — \`git_context({ include_diff: true })\`
-11. **Dead Symbols** — \`dead_symbols({ path: "." })\`
-
-Stash all results for later phases.
-
-### Phase 2: Knowledge Graph Construction
-
-Build a navigable knowledge graph of the codebase:
-
-1. **Discover modules** — \`graph({ action: 'find_nodes' })\` to get all indexed modules
-2. **Map relationships** — For key modules, \`graph({ action: 'neighbors', node_id, direction: 'both' })\`
-3. **Trace critical paths** — Use \`trace({ items: [{start: "<entry-point>", direction: "forward"}] })\` on each entry point
-4. **Identify layers** — Classify modules into architectural layers (API, Service, Domain, Data, Infrastructure, UI, Utility, Config)
-5. **Detect communities** — \`graph({ action: 'detect_communities' })\` to find natural module clusters
-6. **Symbol deep-dive** — For each public API/export, \`symbol({ items: [{name}] })\` to understand usage
-
-Persist the graph structure and layer classification.
-
-### Phase 3: Multi-Agent Understanding (parallel dispatch)
-
-Dispatch Researcher agents **in parallel** to deeply understand different aspects:
-
-**Researcher-Alpha** — Architecture & Design Patterns:
-- What architectural style is used? (layered, hexagonal, microservice, monolith)
-- What design patterns appear? (repository, factory, strategy, observer, etc.)
-- How is data flow organized? (request lifecycle, event pipeline, etc.)
-
-**Researcher-Beta** — Business Logic & Domain:
-- What are the core business domains/bounded contexts?
-- What are the key business flows and processes?
-- What domain entities and value objects exist?
-- How is business logic separated from infrastructure?
-
-**Researcher-Gamma** — Integration & Infrastructure:
-- What external services, APIs, databases are used?
-- How is authentication/authorization handled?
-- What is the deployment topology?
-- What monitoring, logging, observability exists?
-
-**Researcher-Delta** — Quality & Concerns:
-- What is the test coverage strategy?
-- What tech debt or code smells exist?
-- What security concerns should be noted?
-- What performance bottlenecks are visible?
-- What are the highest-complexity files?
-
-### Phase 4: Document Everything
-
-Load the \`docs\` skill and generate comprehensive documentation:
-
-1. **Project Knowledge** (7 architecture docs):
-   - \`docs/architecture/stack.md\` — Language, runtime, frameworks, all dependencies
-   - \`docs/architecture/structure.md\` — Directory layout, entry points, key files
-   - \`docs/architecture/design.md\` — Layers, patterns, data flow, component boundaries
-   - \`docs/architecture/conventions.md\` — Naming, formatting, error handling, imports
-   - \`docs/architecture/integrations.md\` — External APIs, databases, auth, monitoring
-   - \`docs/architecture/testing.md\` — Test frameworks, file organization, mocking
-   - \`docs/architecture/concerns.md\` — Tech debt, security risks, performance issues
-
-2. **Component Docs** — For each major module/component:
-   - \`docs/architecture/components/{name}.md\` — Purpose, API, design decisions, data flow
-
-3. **Reference Docs**:
-   - \`docs/reference/api.md\` — API surface, endpoints, schemas
-   - \`docs/reference/configuration.md\` — Config options, environment variables
-
-4. **Guides**:
-   - \`docs/guides/onboarding.md\` — Guided tour for new developers (dependency-ordered walkthrough)
-   - \`docs/guides/architecture-tour.md\` — Visual architecture walkthrough
-
-5. **Project Overview**:
-   - \`docs/README.md\` — Index linking all docs, project summary
-
-6. **Persist Knowledge** — \`produce_knowledge({ path: "." })\` + \`knowledge({ action: "remember", ... })\` for key findings
-
-7. **AGENTS.md** — Generate an agent-friendly project context file at the repo root:
-   - Project overview, architecture style, key modules
-   - Build/test/run commands
-   - Coding conventions and patterns in use
-   - Key entry points and data flows
-   - Known concerns and tech debt
-
-> **Interactive HTML viewers** (C4 diagrams, code tour walkthroughs) are generated by the \`/aikit-docs-site\` command. Use it after this command to produce interactive explorable documentation.
-
-### Phase 5: Interactive Presentation
-
-Present the understanding as a rich interactive dashboard using \`present\`:
-
-1. **Architecture Overview** — Mermaid diagram of system layers and component relationships
-2. **Dependency Graph** — Module dependency visualization
-3. **Metrics Dashboard** — File count, complexity distribution, test coverage, health score
-4. **Knowledge Map** — Key modules with descriptions, organized by architectural layer
-5. **Guided Tour** — Recommended reading order for codebase onboarding
-6. **Concerns Board** — Tech debt, dead code, security risks as a status board
-7. **Business Domain Map** — Domain entities and their relationships
-
-Use the \`c4-architecture\` skill for generating proper C4 architecture diagrams (Context, Container, Component levels).
-
-### Output Summary
-
-After all phases complete, present a final summary to the user:
-- Total files analyzed, modules discovered, patterns detected
-- Architecture style and key design decisions identified
-- Number of docs generated and their locations
-- Top concerns and recommendations
-- Links to the interactive dashboard
-
-### Rules
-
-- **Every claim must be traceable** to source files or tool output
-- **Never infer or assume** — only document what is verifiable
-- **Mark unknowns** with \`[TODO]\` and intent-dependent decisions with \`[ASK USER]\`
-- **Delegate to specialists**: architecture diagrams → \`c4-architecture\` skill, ADRs → \`adr-skill\`
-- **Compress between phases** — use \`digest\` and \`stash\` to manage context
-- **🛑 STOP after Phase 5** — present results and ask user for feedback before any follow-up work`},"docs-site":{description:`Generate interactive HTML documentation — C4 architecture viewers and code tour walkthroughs with browser verification`,agent:`Orchestrator`,tools:[`onboard`,`analyze`,`produce_knowledge`,`graph`,`search`,`symbol`,`trace`,`file_summary`,`digest`,`knowledge`,`browser`,`present`,`check`,`git_context`,`measure`],content:`## Generate Interactive Documentation Viewers
-
-Create interactive HTML documentation using C4 architecture viewers and code tour walkthroughs.
-
-> **Prerequisite:** Run \`/aikit-docs\` first to generate the base markdown documentation and AGENTS.md.
-
-### Phase 1: Analyze Project
-
-\`\`\`
-onboard({ path: "." })                           # If not done (check status() first)
-analyze({ items: [{aspect: "structure", path: "."}] })      # Directory layout
-analyze({ items: [{aspect: "dependencies", path: "."}] })   # Module graph
-analyze({ items: [{aspect: "entry_points", path: "."}] })   # API surface
-analyze({ items: [{aspect: "diagram", path: "."}] })        # Architecture diagram data
-graph({ action: "find_nodes" })                  # Module graph for C4 mapping
-graph({ action: "detect_communities" })          # Natural module clusters
-\`\`\`
-
-Stash results for use in subsequent phases.
-
-### Phase 2: Generate C4 Architecture Data
-
-Create C4 JSON data files for each architectural level. Save to \`docs/architecture/interactive/\`.
-
-**Required schema — MUST match exactly:**
-
-\`\`\`json
-{
-  "title": "Project Name - C4 Level",
-  "description": "What this diagram shows",
-  "layout": { "direction": "DOWN", "spacing": 80, "layerSpacing": 120 },
-  "nodes": [
-    {
-      "id": "unique-string-id",
-      "type": "person|system|container|component|database|queue|external",
-      "label": "Display Name",
-      "description": "What this element does",
-      "technology": "Language/framework",
-      "parentId": "optional-boundary-id"
-    }
-  ],
-  "edges": [
-    {
-      "id": "unique-edge-id",
-      "source": "source-node-id",
-      "target": "target-node-id",
-      "label": "Relationship description",
-      "technology": "Protocol/transport"
-    }
-  ]
-}
-\`\`\`
-
-**C4 levels to generate:**
-1. \`system-context.json\` — External actors + the system as a black box
-2. \`containers.json\` — Major deployable units (services, databases, frontends)
-3. \`{component-name}-components.json\` — Internal structure of key containers
-
-**Critical rules:**
-- Top-level keys are \`nodes\` and \`edges\` (NOT \`elements\`/\`relationships\`)
-- Every edge MUST have a unique \`id\` field (ELK crashes without it)
-- Node \`type\` MUST be one of: person, system, container, component, database, queue, external
-- \`layout.direction\` MUST be: DOWN, UP, LEFT, or RIGHT
-- \`parentId\` references must point to existing node IDs (or omit entirely)
-
-### Phase 3: Generate Tour Data
-
-Create code tour JSON files. Save to \`docs/tours/interactive/\`.
-
-**Required schema — MUST match exactly:**
-
-\`\`\`json
-{
-  "title": "Tour Title",
-  "description": "What this tour teaches",
-  "estimatedTime": "15 min",
-  "steps": [
-    {
-      "stepNumber": 1,
-      "id": "kebab-case-step-id",
-      "title": "Step Title",
-      "file": "relative/path/to/file.ts",
-      "line": 42,
-      "explanation": "What this code does and why it matters",
-      "learnsConcept": "Concept name",
-      "duration": "2 min",
-      "notes": "Optional additional context"
-    }
-  ],
-  "dependencies": [
-    { "source": "step-id-1", "target": "step-id-2" }
-  ]
-}
-\`\`\`
-
-**Tours to generate:**
-1. \`architecture-overview.json\` — High-level system walkthrough (entry points → core logic → outputs)
-2. \`onboarding.json\` — New developer guided tour (most important files in dependency order)
-3. Additional tours for complex subsystems with >5 modules
-
-**Critical rules:**
-- Step content field is \`explanation\` (NOT \`description\`)
-- Every step needs \`id\` (kebab-case) and \`stepNumber\` (integer, 1-based)
-- \`learnsConcept\` is the concept tag (NOT \`highlights\`)
-- \`dependencies\` array uses step \`id\` values in \`{source, target}\` objects
-- Root MUST have \`title\`, \`description\`, \`estimatedTime\`
-
-### Phase 4: Inject Data into HTML Templates
-
-Use PowerShell to inject JSON data into the viewer template HTML files.
-
-**Template locations:**
-- C4 viewer: \`C:\\Users\\AnVPX\\.copilot\\skills\\c4-architecture\\assets\\c4-viewer.html\` (tag: \`id="diagram-data"\`)
-- Tour viewer: \`C:\\Users\\AnVPX\\.copilot\\skills\\docs\\assets\\tour-viewer.html\` (tag: \`id="tour-data"\`)
-
-**Injection procedure (for EACH JSON file):**
-
-\`\`\`powershell
-$template = [System.IO.File]::ReadAllText("TEMPLATE_PATH")
-$startTag = '<script type="application/json" id="TARGET_ID">'
-$startIdx = $template.IndexOf($startTag)
-if ($startIdx -lt 0) { throw "Tag not found" }
-$contentStart = $startIdx + $startTag.Length
-$endIdx = $template.IndexOf('<\/script>', $contentStart)
-
-$before = $template.Substring(0, $contentStart)
-$after = $template.Substring($endIdx)
-$data = Get-Content "JSON_PATH" -Raw
-
-$output = $before + [char]10 + $data + [char]10 + $after
-[System.IO.File]::WriteAllText("OUTPUT_PATH", $output, [System.Text.Encoding]::UTF8)
-\`\`\`
-
-**Output file layout:**
-\`\`\`
-docs/
-  architecture/interactive/
-    system-context.json        # Data
-    system-context.html        # Injected viewer (from c4-viewer.html)
-    containers.json
-    containers.html
-  tours/interactive/
-    architecture-overview.json # Data
-    architecture-overview.html # Injected viewer (from tour-viewer.html)
-    onboarding.json
-    onboarding.html
-\`\`\`
-
-**Rules:**
-- JSON + HTML MUST be siblings in the same \`interactive/\` directory
-- NEVER use \`inject-viewer.mjs\` — use the PowerShell procedure above
-- Verify \`$startIdx -ge 0\` before proceeding
-
-### Phase 5: Browser Verification (MANDATORY)
-
-**Every generated HTML file MUST be tested before presenting to user.**
-
-\`\`\`
-# 1. Serve the docs folder
-run_in_terminal("npx -y serve docs -l 4000 --no-clipboard", mode: "async")
-
-# 2. Open each viewer
-browser({ action: 'open', url: 'http://localhost:4000/architecture/interactive/system-context.html', mode: 'ui', waitUntil: 'networkidle' })
-
-# 3. Read accessibility snapshot
-browser({ action: 'read', pageId: '<id>', readMode: 'snapshot' })
-
-# 4. Verify content renders:
-#    C4: nodes with labels, edges, Zoom In/Out/Fit buttons, Mini Map
-#    Tour: step numbers + titles, Prev/Next buttons, explanation text, file paths
-
-# 5. If blank or errors → fix JSON schema → re-inject → re-test
-
-# 6. Clean up
-browser({ action: 'session', sessionAction: 'close', pageId: '<id>' })
-kill_terminal(<serve-terminal-id>)
-\`\`\`
-
-**Verification checklist:**
-
-| Viewer | Must see in snapshot | Failure indicator |
-|--------|---------------------|-------------------|
-| C4 | Node labels, edge groups, Zoom/Fit buttons, Mini Map | Empty page, "Error", no nodes |
-| Tour | Step numbers + titles, Prev/Next, explanation text | Blank panel, "undefined", no steps |
-
-### Phase 6: Present Results
-
-After ALL viewers pass verification:
-
-1. List all generated files (JSON + HTML) with descriptions
-2. Provide the serve command: \`npx -y serve docs -l 4000 --no-clipboard\`
-3. List all viewer URLs (e.g., \`http://localhost:4000/architecture/interactive/system-context.html\`)
-4. Note any issues found during verification
-
-### Critical Rules
-
-1. **NEVER skip browser verification** — a valid JSON can still produce a broken viewer
-2. **NEVER use \`file:///\` URLs** — CORS blocks ES modules; always serve via HTTP
-3. **NEVER use \`inject-viewer.mjs\`** — use the PowerShell injection procedure
-4. **NEVER use \`elements\`/\`relationships\`** — the ReactFlow viewer uses \`nodes\`/\`edges\`
-5. **NEVER omit \`id\` on edges** — ELK layout throws null errors
-6. **NEVER use \`description\` in tour steps** — template reads \`explanation\`
-7. **ALWAYS use \`npx -y\`** — without \`-y\` the command hangs on install prompt
-8. **ALWAYS include \`layout\` object in C4 JSON** — ELK crashes without direction/spacing
-9. **ALWAYS verify \`$startIdx -ge 0\`** before injection — missing tag = wrong template
-10. **All data must come from AI Kit analysis tools** — never fabricate architecture`}};export{e as PROMPTS};
+**Already provided by skills:** Phase detail (scan tools, knowledge graph construction, multi-agent dispatch, 7-doc templates, quality checklists). Load the \`docs\` skill and follow its workflow.`},"docs-site":{description:`Generate interactive HTML documentation — C4 architecture viewers and code tour walkthroughs with browser verification`,agent:`Orchestrator`,intent:`Generate interactive HTML documentation (C4 viewers + code tours)`,tools:[`onboard`,`analyze`,`produce_knowledge`,`graph`,`search`,`symbol`,`trace`,`file_summary`,`digest`,`knowledge`,`browser`,`present`,`check`,`git_context`,`measure`],content:"## Interactive Documentation Viewers\n\nGenerate C4 architecture viewers and code tour walkthroughs using maintained viewer assets.\n\n1. **Load the `c4-architecture` skill** — C4 JSON schema, viewer injection script, ELK auto-layout\n2. **Load the `docs` skill** — tour JSON schema, viewer injection, line validation\n3. **For C4 diagrams**: Follow c4-architecture skill workflow → generate JSON → use `scripts/inject-viewer.mjs` to inject into `assets/c4-viewer.html`\n4. **For code tours**: Follow docs skill tour-generation.md → generate tour JSON → use `scripts/inject-viewer.mjs` to inject into tour viewer\n5. **Browser verification**: Open each HTML via `serve` + `browser` tool to verify rendering\n6. **Serve**: `npx -y serve docs -l 4000 --no-clipboard`\n\n**JSON schemas, viewer rules, injection scripts, and verification checklist are in the loaded skills** — never hardcode them in commands."}};export{e as PROMPTS};

package/scaffold/dist/definitions/tools.mjs

@@ -1 +1 @@
-const e=`analyze.audit.blast_radius.changelog.check.checkpoint.codemod.config.data_transform.dead_symbols.delegate.describe_tool.diff_parse.digest.encode.env.eval.evidence_map.file_summary.find.flow.forge_classify.forge_ground.git_context.graph.guide.health.http.knowledge.lane.list_tools.lookup.measure.onboard.parse_output.present.process.produce_knowledge.queue.regex_test.reindex.rename.replay.restore.schema_validate.scope_map.search.search_tools.session_digest.signal.stash.status.symbol.test_run.time.trace.watch.web_fetch.web_search.workset`.split(`.`),t={orchestrator:[`memory`,`runCommand`,`switchAgent`,`newWorkspace`,`reviewPlan`,`killTerminal`,`createTask`,`terminal`,`terminalSel`,`lastCommand`,`problems`,`readFile`,`subagent`,`search`,`web`,`todo`,`searchSubagent`,`textSearch`,`browser`,`askQuestions`,`resolveMemoryFileUri`],researcher:[`terminal`,`problems`,`readFile`,`lastCommand`,`subagent`,`search`,`web`,`browser`],reviewer:[`terminal`,`problems`,`readFile`,`lastCommand`,`subagent`,`search`,`web`,`browser`],codeAgent:[`createTask`,`terminal`,`problems`,`readFile`,`lastCommand`,`subagent`,`createFile`,`editFiles`,`rename`,`createDirectory`,`search`,`todo`,`browser`],debugger:[`terminal`,`problems`,`readFile`,`terminalSel`,`lastCommand`,`subagent`,`createFile`,`editFiles`,`search`,`browser`],refactor:[`terminal`,`problems`,`readFile`,`lastCommand`,`subagent`,`createFile`,`editFiles`,`rename`,`createDirectory`,`search`,`browser`],explorer:[`problems`,`readFile`,`search`,`fileSearch`,`listDir`,`textSearch`,`browser`],planner:[`terminal`,`problems`,`readFile`,`reviewPlan`,`memory`,`askQuestions`,`resolveMemoryFileUri`,`lastCommand`,`subagent`,`createFile`,`editFiles`,`rename`,`createDirectory`,`search`,`web`,`todo`,`searchSubagent`,`browser`],security:[`terminal`,`problems`,`readFile`,`subagent`,`search`,`web`,`browser`],documenter:[`terminal`,`problems`,`readFile`,`lastCommand`,`subagent`,`createFile`,`editFiles`,`rename`,`createDirectory`,`search`,`web`,`browser`]},n={terminal:[`Bash`],problems:[`Read`],readFile:[`Read`],lastCommand:[`Bash`],subagent:[],createFile:[`Write`],editFiles:[`Edit`],rename:[`Write`],createDirectory:[`Write`],search:[`Read`],web:[`WebFetch`,`WebSearch`],todo:[`TodoRead`,`TodoWrite`],memory:[],runCommand:[`Bash`],switchAgent:[],newWorkspace:[`Bash`],reviewPlan:[],killTerminal:[`Bash`],createTask:[`Bash`],terminalSel:[`Bash`],fileSearch:[`Read`],listDir:[`Read`],textSearch:[`Read`],searchSubagent:[],browser:[],askQuestions:[],resolveMemoryFileUri:[]};export{e as AIKIT_TOOLS,n as CLAUDE_CODE_TOOL_MAP,t as IDE_CAPABILITIES};
+const e=`analyze.audit.blast_radius.browser.changelog.check.checkpoint.codemod.config.data_transform.dead_symbols.delegate.describe_tool.diff_parse.digest.encode.env.eval.evidence_map.file_summary.find.flow.forge_classify.forge_ground.git_context.graph.guide.health.http.knowledge.lane.list_tools.lookup.measure.onboard.parse_output.present.process.produce_knowledge.queue.regex_test.reindex.rename.replay.restore.schema_validate.scope_map.search.search_tools.session_digest.signal.stash.status.symbol.test_run.time.trace.watch.web_fetch.web_search.workset`.split(`.`),t={orchestrator:[`memory`,`runCommand`,`switchAgent`,`newWorkspace`,`reviewPlan`,`killTerminal`,`createTask`,`terminal`,`terminalSel`,`lastCommand`,`problems`,`readFile`,`subagent`,`search`,`web`,`todo`,`searchSubagent`,`textSearch`,`browser`,`askQuestions`,`resolveMemoryFileUri`],researcher:[`terminal`,`problems`,`readFile`,`lastCommand`,`subagent`,`search`,`web`,`browser`],reviewer:[`terminal`,`problems`,`readFile`,`lastCommand`,`subagent`,`search`,`web`,`browser`],codeAgent:[`createTask`,`terminal`,`problems`,`readFile`,`lastCommand`,`subagent`,`createFile`,`editFiles`,`rename`,`createDirectory`,`search`,`todo`,`browser`],debugger:[`terminal`,`problems`,`readFile`,`terminalSel`,`lastCommand`,`subagent`,`createFile`,`editFiles`,`search`,`browser`],refactor:[`terminal`,`problems`,`readFile`,`lastCommand`,`subagent`,`createFile`,`editFiles`,`rename`,`createDirectory`,`search`,`browser`],explorer:[`problems`,`readFile`,`search`,`fileSearch`,`listDir`,`textSearch`,`browser`],planner:[`terminal`,`problems`,`readFile`,`reviewPlan`,`memory`,`askQuestions`,`resolveMemoryFileUri`,`lastCommand`,`subagent`,`createFile`,`editFiles`,`rename`,`createDirectory`,`search`,`web`,`todo`,`searchSubagent`,`browser`],security:[`terminal`,`problems`,`readFile`,`subagent`,`search`,`web`,`browser`],documenter:[`terminal`,`problems`,`readFile`,`lastCommand`,`subagent`,`createFile`,`editFiles`,`rename`,`createDirectory`,`search`,`web`,`browser`]},n={terminal:[`Bash`],problems:[`Read`],readFile:[`Read`],lastCommand:[`Bash`],subagent:[],createFile:[`Write`],editFiles:[`Edit`],rename:[`Write`],createDirectory:[`Write`],search:[`Read`],web:[`WebFetch`,`WebSearch`],todo:[`TodoRead`,`TodoWrite`],memory:[],runCommand:[`Bash`],switchAgent:[],newWorkspace:[`Bash`],reviewPlan:[],killTerminal:[`Bash`],createTask:[`Bash`],terminalSel:[`Bash`],fileSearch:[`Read`],listDir:[`Read`],textSearch:[`Read`],searchSubagent:[],browser:[],askQuestions:[],resolveMemoryFileUri:[]};export{e as AIKIT_TOOLS,n as CLAUDE_CODE_TOOL_MAP,t as IDE_CAPABILITIES};

package/scaffold/vitest.config.mjs

@@ -0,0 +1,8 @@
+import { defineConfig } from 'vitest/config';
+
+export default defineConfig({
+  test: {
+    include: ['scaffold/__tests__/prompts-quality.test.mjs'],
+    exclude: ['**/node_modules/**'],
+  },
+});

package/packages/cli/dist/init-DFhk2_8C.js

@@ -1,7 +0,0 @@
-import{c as e,l as t,n,o as r,r as i,t as a}from"./scaffold-BNPHP-QC.js";import{a as o,i as s,m as c,n as l,o as u,r as d,t as f}from"./templates-CztsaGb2.js";import{appendFileSync as p,existsSync as m,mkdirSync as h,readFileSync as g,unlinkSync as _,writeFileSync as v}from"node:fs";import{basename as y,resolve as b}from"node:path";import{homedir as x}from"node:os";import{AIKIT_PATHS as S,EMBEDDING_DEFAULTS as C,isUserInstalled as w}from"../../core/dist/index.js";function T(e){return m(b(e,`.cursor`))?`cursor`:m(b(e,`.claude`))?`claude-code`:m(b(e,`.windsurf`))?`windsurf`:m(b(e,`.zed`))?`zed`:m(b(e,`.idea`))?`intellij`:m(b(e,`.opencode`))?`opencode`:m(b(e,`AGENTS.md`))?`hermes`:`copilot`}function E(e){let t=[];return m(b(e,`.cursor`))&&t.push(`cursor`),(m(b(e,`.claude`))||m(b(e,`CLAUDE.md`)))&&t.push(`claude-code`),m(b(e,`.windsurf`))&&t.push(`windsurf`),m(b(e,`.zed`))&&t.push(`zed`),m(b(e,`.idea`))&&t.push(`intellij`),m(b(e,`.gemini`))&&t.push(`gemini-cli`),(m(b(e,`.codex`))||m(b(e,`codex.md`)))&&t.push(`codex-cli`),(m(b(e,`.opencode`))||m(b(e,`OPENCODE.md`)))&&t.push(`opencode`),t.push(`copilot`),t.push(`hermes`),[...new Set(t)]}function D(e){return{servers:{[e]:{...s}}}}function O(e){let{type:t,...n}=s;return{mcpServers:{[e]:n}}}function k(e){let{type:t,...n}=s;return{context_servers:{[e]:{...n}}}}function A(e){let{type:t,...n}=s;return{mcp:{[e]:{type:`local`,command:[n.command,...n.args]}}}}const j={scaffoldDir:`general`,writeMcpConfig(e,t){let n=b(e,`.vscode`),r=b(n,`mcp.json`);m(r)||(h(n,{recursive:!0}),v(r,`${JSON.stringify(D(t),null,2)}\n`,`utf-8`),console.log(`  Created .vscode/mcp.json`))},writeInstructions(e,t){let n=b(e,`.github`),r=b(n,`copilot-instructions.md`);h(n,{recursive:!0}),v(r,l(y(e),t),`utf-8`),console.log(`  Updated .github/copilot-instructions.md`)},writeAgentsMd(e,t){v(b(e,`AGENTS.md`),f(y(e),t),`utf-8`),console.log(`  Updated AGENTS.md`)}};function M(e){let{type:t,...n}=s;return{mcpServers:{[e]:{command:n.command,args:[...n.args]}}}}const N=`Orchestrator`;function P(e){return{...M(e),agent:N}}function F(e,t){let n=t??b(x(),`.claude`),r=b(n,`settings.json`),i=M(e);if(!m(r)){h(n,{recursive:!0});let t=P(e);v(r,`${JSON.stringify(t,null,2)}\n`,`utf-8`),console.log(`  Created ${r} — MCP server + default agent`);return}try{let e=JSON.parse(g(r,`utf-8`));e.mcpServers={...e.mcpServers||{},...i.mcpServers},e.agent=N,v(r,`${JSON.stringify(e,null,2)}\n`,`utf-8`),console.log(`  Updated ${r} — MCP server + default agent`)}catch{console.warn(`  ⚠ ${r} contains invalid JSON — skipping config merge`)}}const I={scaffoldDir:`general`,writeMcpConfig(e,t){F(t);let n=b(e,`.mcp.json`);m(n)||(v(n,`${JSON.stringify(O(t),null,2)}\n`,`utf-8`),console.log(`  Created .mcp.json`))},writeInstructions(e,t){let n=b(e,`CLAUDE.md`),r=y(e);v(n,`${l(r,t)}\n---\n\n${f(r,t)}`,`utf-8`),console.log(`  Updated CLAUDE.md`)},writeAgentsMd(e,t){}},L={scaffoldDir:`general`,writeMcpConfig(e,t){let n=b(e,`.cursor`),r=b(n,`mcp.json`);m(r)||(h(n,{recursive:!0}),v(r,`${JSON.stringify(O(t),null,2)}\n`,`utf-8`),console.log(`  Created .cursor/mcp.json`))},writeInstructions(e,t){let n=b(e,`.cursor`,`rules`),r=b(n,`aikit.mdc`);h(n,{recursive:!0});let i=y(e);v(r,`${l(i,t)}\n---\n\n${f(i,t)}`,`utf-8`),console.log(`  Updated .cursor/rules/aikit.mdc`);let a=b(n,`kb.mdc`);m(a)&&a!==r&&(_(a),console.log(`  Removed legacy .cursor/rules/kb.mdc`))},writeAgentsMd(e,t){}},R={scaffoldDir:`general`,writeMcpConfig(e,t){let n=b(e,`.vscode`),r=b(n,`mcp.json`);m(r)||(h(n,{recursive:!0}),v(r,`${JSON.stringify(D(t),null,2)}\n`,`utf-8`),console.log(`  Created .vscode/mcp.json (Windsurf-compatible)`))},writeInstructions(e,t){let n=b(e,`.windsurfrules`),r=y(e);v(n,`${l(r,t)}\n---\n\n${f(r,t)}`,`utf-8`),console.log(`  Updated .windsurfrules`)},writeAgentsMd(e,t){}},z={scaffoldDir:`general`,writeMcpConfig(e,t){let n=b(e,`.zed`),r=b(n,`settings.json`);if(h(n,{recursive:!0}),!m(r))v(r,`${JSON.stringify(k(t),null,2)}\n`,`utf-8`),console.log(`  Created .zed/settings.json`);else{let e;try{e=JSON.parse(g(r,`utf-8`))}catch{console.warn(`  ⚠ .zed/settings.json contains invalid JSON — skipping MCP config merge`);return}e.context_servers?.[t]||(e.context_servers={...e.context_servers,...k(t).context_servers},v(r,`${JSON.stringify(e,null,2)}\n`,`utf-8`),console.log(`  Updated .zed/settings.json with context_servers`))}},writeInstructions(e,t){let n=b(e,`.rules`),r=y(e);v(n,`${l(r,t)}\n---\n\n${f(r,t)}`,`utf-8`),console.log(`  Updated .rules`)},writeAgentsMd(e,t){}},B={scaffoldDir:`general`,writeMcpConfig(e,t){let n=b(e,`mcp.json`);m(n)||(v(n,`${JSON.stringify(O(t),null,2)}\n`,`utf-8`),console.log(`  Created mcp.json`))},writeInstructions(e,t){let n=b(e,`.aiassistant`,`rules`),r=b(n,`aikit.md`);h(n,{recursive:!0});let i=y(e);v(r,`${l(i,t)}\n---\n\n${f(i,t)}`,`utf-8`),console.log(`  Updated .aiassistant/rules/aikit.md`)},writeAgentsMd(e,t){}},V={scaffoldDir:`general`,writeMcpConfig(e,t){let n=b(e,`.opencode`),r=b(n,`opencode.json`);m(r)||(h(n,{recursive:!0}),v(r,`${JSON.stringify(A(t),null,2)}\n`,`utf-8`),console.log(`  Created .opencode/opencode.json`))},writeInstructions(e,t){let n=b(e,`OPENCODE.md`),r=y(e);v(n,`${l(r,t)}\n---\n\n${f(r,t)}`,`utf-8`),console.log(`  Updated OPENCODE.md`)},writeAgentsMd(e,t){}},H={scaffoldDir:`general`,writeMcpConfig(e,t){},writeInstructions(e,t){let n=b(e,`AGENTS.md`),r=y(e);v(n,`${l(r,t)}\n---\n\n${f(r,t)}`,`utf-8`),console.log(`  Updated AGENTS.md (Hermes)`)},writeAgentsMd(e,t){}};function U(e){switch(e){case`copilot`:return j;case`claude-code`:return I;case`cursor`:return L;case`windsurf`:return R;case`zed`:return z;case`intellij`:return B;case`opencode`:return V;case`hermes`:return H;case`gemini-cli`:case`codex-cli`:return j}}const W={serverName:o,sources:[{path:`.`,excludePatterns:[`**/node_modules/**`,`**/dist/**`,`**/build/**`,`**/.git/**`,`**/${S.data}/**`,`**/coverage/**`,`**/*.min.js`,`**/package-lock.json`,`**/pnpm-lock.yaml`]}],indexing:{chunkSize:1500,chunkOverlap:200,minChunkSize:100},embedding:{model:C.model,dimensions:C.dimensions},store:{backend:`sqlite-vec`,path:S.data},curated:{path:S.aiCurated}};function G(e,t){let n=b(e,`aikit.config.json`);return m(n)&&!t?(console.log(`aikit.config.json already exists. Use --force to overwrite.`),!1):(v(n,`${JSON.stringify(W,null,2)}\n`,`utf-8`),console.log(`  Created aikit.config.json`),!0)}function K(e){let t=b(e,`.gitignore`),n=[{dir:`.flows/`,label:`AI Kit flow runs`}];if(m(t)){let e=g(t,`utf-8`),r=n.filter(t=>!e.includes(t.dir));r.length>0&&(p(t,`\n${r.map(e=>`# ${e.label}\n${e.dir}`).join(`
-`)}\n`,`utf-8`),console.log(`  Added ${r.map(e=>e.dir).join(`, `)} to .gitignore`))}else v(t,`${n.map(e=>`# ${e.label}\n${e.dir}`).join(`
-`)}\n`,`utf-8`),console.log(`  Created .gitignore with AI Kit entries`)}function q(){return W.serverName}const J=[`decisions`,`patterns`,`conventions`,`troubleshooting`];function Y(e){let t=b(e,`.ai`,`curated`);m(t)||(h(t,{recursive:!0}),console.log(`  Created .ai/curated/`));for(let e of J){let n=b(t,e);m(n)||h(n,{recursive:!0})}console.log(`  Created .ai/curated/{${J.join(`,`)}}/`)}function X(e){switch(e){case`zed`:return`zed`;case`intellij`:return`intellij`;case`claude-code`:return`claude-code`;case`gemini-cli`:return`gemini`;case`codex-cli`:return`codex`;case`opencode`:return`opencode`;case`hermes`:return`hermes`;default:return`copilot`}}async function Z(n){let i=process.cwd();if(!G(i,n.force))return;K(i);let a=q(),o=U(T(i));o.writeMcpConfig(i,a),o.writeInstructions(i,a),o.writeAgentsMd(i,a);let s=c(),l=JSON.parse(g(b(s,`package.json`),`utf-8`)).version;await t(i,s,[...u],l,n.force),await r(i,s,[...d],l,n.force);let f=E(i),p=new Set;for(let t of f){let r=X(t);p.has(r)||(p.add(r),await e(i,s,r,l,n.force))}Y(i),console.log(`
-AI Kit initialized! Next steps:`),console.log(`  aikit reindex  Index your codebase`),console.log(`  aikit search   Search indexed content`),console.log(`  aikit serve    Start MCP server for IDE integration`),w()&&console.log(`
-Note: User-level AI Kit is also installed. This workspace uses its own local data store.`)}async function Q(e){w()?await $(e):await Z(e)}async function $(t){let n=process.cwd(),i=q(),a=U(T(n));a.writeInstructions(n,i),a.writeAgentsMd(n,i);let o=c(),s=JSON.parse(g(b(o,`package.json`),`utf-8`)).version,l=E(n),u=new Set;for(let r of l){let i=X(r);u.has(i)||(u.add(i),await e(n,o,i,s,t.force))}await r(n,o,[...d],s,t.force),Y(n),K(n),console.log(`
-Workspace scaffolded for user-level AI Kit! Files added:`),console.log(`  Instruction files (AGENTS.md, copilot-instructions.md, etc.)`),console.log(`  .ai/curated/ directories`),console.log(`  .github/agents/ & .github/prompts/`),console.log(`
-The user-level AI Kit server will auto-index this workspace when opened in your IDE.`)}async function ee(){let e=process.cwd(),t=E(e),r=c(),o=[...await i(e,r,[...u])],s=new Set;for(let i of t){let t=X(i);s.has(t)||(s.add(t),o.push(...await n(e,r,t)))}o.push(...await a(e,r,[...d]));let l={summary:{total:o.length,new:o.filter(e=>e.status===`new`).length,outdated:o.filter(e=>e.status===`outdated`).length,current:o.filter(e=>e.status===`current`).length},files:o};console.log(JSON.stringify(l,null,2))}export{ee as guideProject,Z as initProject,$ as initScaffoldOnly,Q as initSmart};