@vpxa/aikit 0.1.1 → 0.1.2

package/scaffold/flows/aikit-basic/skills/implement/SKILL.md

@@ -1,105 +1,105 @@
----
-name: implement
-description: Write code following the assessment plan, using TDD practices where applicable.
----
-
-# Implementation
-
-## Purpose
-
-Execute the implementation plan from the assessment, writing production code and tests.
-
-## Inputs
-
-- `.spec/<slug>/assessment.md` — the approach, affected files, and risks
-
-## Process
-
-1. **Read assessment** — Load `.spec/<slug>/assessment.md` and internalize the approach
-2. **Set up tests first** — Where applicable, write failing tests that define success
-3. **Implement changes** — Follow the approach steps sequentially
-   - One logical change per commit-worthy chunk
-   - Stay within the assessed file scope — do not expand without re-assessment
-4. **Run validation** — `check({})` for type/lint errors, `test_run({})` for test results
-5. **Fix issues** — Iterate until `check` and `test_run` pass (max 3 rounds)
-6. **Document progress** — Write progress artifact with what was done and any deviations
-
-## Outputs
-
-Produce `.spec/<slug>/progress.md` with:
-
-```markdown
-# Implementation Progress: <task title>
-
-## Changes Made
-<list of files changed with brief description>
-
-## Tests
-<tests added or modified>
-
-## Deviations from Assessment
-<any changes to the original plan and why>
-
-## Validation
-- check: PASS/FAIL
-- test_run: PASS/FAIL (<N> passed, <M> failed)
-
-## Notes
-<anything the reviewer should know>
-```
-
-## Agents
-
-| Agent | Role |
-|-------|------|
-| **Implementer** | Primary code writer — follows TDD, writes production code and tests |
-| **Frontend** | UI/UX specialist — use when changes involve React components, styling, or responsive design |
-
-Dispatch Implementer for backend/logic changes, Frontend for UI changes. Both can run in parallel if working on different files.
-
-## Foundation Integration
-
-Load these skills BEFORE executing this step:
-
-| Skill | Purpose | When |
-|-------|---------|------|
-| `aikit` | Core MCP tools — search, analyze, remember, validate | Always (auto-loaded) |
-| `present` | Rich rendering for any structured output — assessments, reports, comparisons, reviews, status boards, tables, charts, and all artifact content | Use for ANY output that benefits from rich rendering, not just dashboards |
-| `multi-agents-development` | Dispatch templates, task decomposition, review pipeline patterns | Before dispatching any subagent |
-| `brainstorming` | Structured ideation for design/creative decisions | Before any design choice or new feature exploration |
-
-### Presentation Rules
-- Use `present` for **any output** that benefits from rich rendering — not limited to dashboards
-- Assessments, reports, comparisons, reviews, status boards → `present({ format: "html" })`
-- Tables, charts, progress tracking, code review findings → always present
-- Artifact content and summaries → present with structured layout
-- Only use plain text for brief confirmations and simple questions
-
-### Orchestrator Dispatch Protocol
-
-Follow the `multi-agents-development` skill patterns for dispatch:
-
-1. **Independence Check** before parallelizing:
-   - Same files? → sequential
-   - Shared mutable state? → sequential
-   - Execution-order dependent? → sequential
-   - Need shared new types? → define contract first, then parallel
-   - All clear? → **parallel dispatch**
-
-2. **Subagent Context Template** (each dispatch includes):
-   - **Scope**: exact files + boundary (do NOT touch)
-   - **Goal**: acceptance criteria, testable
-   - **Arch Context**: actual code snippets via `compact()`/`digest()`
-   - **Constraints**: patterns, conventions, anti-patterns
-   - **Self-Review**: checklist before declaring DONE
-
-3. **Status Protocol**: `DONE` | `DONE_WITH_CONCERNS` | `NEEDS_CONTEXT` | `BLOCKED`
-4. **Max 2 retries** per task — then escalate to user
-
-## Completion Criteria
-
-- [ ] All assessment steps implemented
-- [ ] `check({})` passes (no type/lint errors)
-- [ ] `test_run({})` passes (no test failures)
-- [ ] No files modified outside assessed scope
-- [ ] `.spec/<slug>/progress.md` written
+---
+name: implement
+description: Write code following the assessment plan, using TDD practices where applicable.
+---
+
+# Implementation
+
+## Purpose
+
+Execute the implementation plan from the assessment, writing production code and tests.
+
+## Inputs
+
+- `.spec/<slug>/assessment.md` — the approach, affected files, and risks
+
+## Process
+
+1. **Read assessment** — Load `.spec/<slug>/assessment.md` and internalize the approach
+2. **Set up tests first** — Where applicable, write failing tests that define success
+3. **Implement changes** — Follow the approach steps sequentially
+   - One logical change per commit-worthy chunk
+   - Stay within the assessed file scope — do not expand without re-assessment
+4. **Run validation** — `check({})` for type/lint errors, `test_run({})` for test results
+5. **Fix issues** — Iterate until `check` and `test_run` pass (max 3 rounds)
+6. **Document progress** — Write progress artifact with what was done and any deviations
+
+## Outputs
+
+Produce `.spec/<slug>/progress.md` with:
+
+```markdown
+# Implementation Progress: <task title>
+
+## Changes Made
+<list of files changed with brief description>
+
+## Tests
+<tests added or modified>
+
+## Deviations from Assessment
+<any changes to the original plan and why>
+
+## Validation
+- check: PASS/FAIL
+- test_run: PASS/FAIL (<N> passed, <M> failed)
+
+## Notes
+<anything the reviewer should know>
+```
+
+## Agents
+
+| Agent | Role |
+|-------|------|
+| **Implementer** | Primary code writer — follows TDD, writes production code and tests |
+| **Frontend** | UI/UX specialist — use when changes involve React components, styling, or responsive design |
+
+Dispatch Implementer for backend/logic changes, Frontend for UI changes. Both can run in parallel if working on different files.
+
+## Foundation Integration
+
+Load these skills BEFORE executing this step:
+
+| Skill | Purpose | When |
+|-------|---------|------|
+| `aikit` | Core MCP tools — search, analyze, remember, validate | Always (auto-loaded) |
+| `present` | Rich rendering for any structured output — assessments, reports, comparisons, reviews, status boards, tables, charts, and all artifact content | Use for ANY output that benefits from rich rendering, not just dashboards |
+| `multi-agents-development` | Dispatch templates, task decomposition, review pipeline patterns | Before dispatching any subagent |
+| `brainstorming` | Structured ideation for design/creative decisions | Before any design choice or new feature exploration |
+
+### Presentation Rules
+- Use `present` for **any output** that benefits from rich rendering — not limited to dashboards
+- Assessments, reports, comparisons, reviews, status boards → `present({ format: "html" })`
+- Tables, charts, progress tracking, code review findings → always present
+- Artifact content and summaries → present with structured layout
+- Only use plain text for brief confirmations and simple questions
+
+### Orchestrator Dispatch Protocol
+
+Follow the `multi-agents-development` skill patterns for dispatch:
+
+1. **Independence Check** before parallelizing:
+   - Same files? → sequential
+   - Shared mutable state? → sequential
+   - Execution-order dependent? → sequential
+   - Need shared new types? → define contract first, then parallel
+   - All clear? → **parallel dispatch**
+
+2. **Subagent Context Template** (each dispatch includes):
+   - **Scope**: exact files + boundary (do NOT touch)
+   - **Goal**: acceptance criteria, testable
+   - **Arch Context**: actual code snippets via `compact()`/`digest()`
+   - **Constraints**: patterns, conventions, anti-patterns
+   - **Self-Review**: checklist before declaring DONE
+
+3. **Status Protocol**: `DONE` | `DONE_WITH_CONCERNS` | `NEEDS_CONTEXT` | `BLOCKED`
+4. **Max 2 retries** per task — then escalate to user
+
+## Completion Criteria
+
+- [ ] All assessment steps implemented
+- [ ] `check({})` passes (no type/lint errors)
+- [ ] `test_run({})` passes (no test failures)
+- [ ] No files modified outside assessed scope
+- [ ] `.spec/<slug>/progress.md` written

package/scaffold/flows/aikit-basic/skills/verify/SKILL.md

@@ -1,96 +1,96 @@
----
-name: verify
-description: Review code changes, run tests, validate correctness and quality.
----
-
-# Verification
-
-## Purpose
-
-Validate that the implementation meets the original requirements, passes all quality gates, and introduces no regressions.
-
-## Inputs
-
-- `.spec/<slug>/assessment.md` — original requirements and approach
-- `.spec/<slug>/progress.md` — what was implemented and any deviations
-
-## Process
-
-1. **Load context** — Read assessment and progress artifacts
-2. **Code review** — Review all changed files for:
-   - Correctness against requirements
-   - Code quality and adherence to project conventions
-   - Error handling and edge cases
-   - No unnecessary changes (scope creep)
-3. **Run quality gates** — `check({})` + `test_run({})` must pass
-4. **Blast radius** — `blast_radius({ changed_files: [...] })` to assess impact
-5. **Security scan** — Check for OWASP Top 10 issues in changed code
-6. **Write report** — Document findings with PASS/FAIL verdict
-
-## Outputs
-
-Produce `.spec/<slug>/verify-report.md` with:
-
-```markdown
-# Verification Report: <task title>
-
-## Verdict: PASS | FAIL
-
-## Quality Gates
-- check: PASS/FAIL
-- test_run: PASS/FAIL (<N> passed, <M> failed)
-- blast_radius: <summary of impact>
-
-## Code Review Findings
-<issues found, if any, with severity>
-
-## Security
-<any security concerns>
-
-## Recommendation
-<APPROVE for commit / REQUEST CHANGES with specific items>
-```
-
-## Agents
-
-| Agent | Role |
-|-------|------|
-| **Code-Reviewer-Alpha** | Primary code reviewer — correctness, quality, conventions |
-| **Security** | Security specialist — vulnerability analysis, OWASP compliance |
-
-Run both in parallel — they review different aspects of the same changes.
-
-## Foundation Integration
-
-Load these skills BEFORE executing this step:
-
-| Skill | Purpose | When |
-|-------|---------|------|
-| `aikit` | Core MCP tools — search, analyze, remember, validate | Always (auto-loaded) |
-| `present` | Rich rendering for any structured output — assessments, reports, comparisons, reviews, status boards, tables, charts, and all artifact content | Use for ANY output that benefits from rich rendering, not just dashboards |
-| `multi-agents-development` | Dispatch templates, task decomposition, review pipeline patterns | Before dispatching any subagent |
-| `brainstorming` | Structured ideation for design/creative decisions | Before any design choice or new feature exploration |
-
-### Presentation Rules
-- Use `present` for **any output** that benefits from rich rendering — not limited to dashboards
-- Assessments, reports, comparisons, reviews, status boards → `present({ format: "html" })`
-- Tables, charts, progress tracking, code review findings → always present
-- Artifact content and summaries → present with structured layout
-- Only use plain text for brief confirmations and simple questions
-
-### FORGE Quality Gate
-
-After all reviews complete:
-1. `evidence_map({ action: "gate", task_id: "<slug>" })` → returns YIELD/HOLD/HARD_BLOCK
-2. YIELD → approved, proceed to commit
-3. HOLD → minor issues, fix then re-gate (max 3 rounds)
-4. HARD_BLOCK → critical issues, escalate to user
-
-## Completion Criteria
-
-- [ ] `check({})` passes
-- [ ] `test_run({})` passes
-- [ ] Code review complete with no blocking issues
-- [ ] Security review complete
-- [ ] Blast radius assessed
-- [ ] `.spec/<slug>/verify-report.md` written with clear PASS/FAIL verdict
+---
+name: verify
+description: Review code changes, run tests, validate correctness and quality.
+---
+
+# Verification
+
+## Purpose
+
+Validate that the implementation meets the original requirements, passes all quality gates, and introduces no regressions.
+
+## Inputs
+
+- `.spec/<slug>/assessment.md` — original requirements and approach
+- `.spec/<slug>/progress.md` — what was implemented and any deviations
+
+## Process
+
+1. **Load context** — Read assessment and progress artifacts
+2. **Code review** — Review all changed files for:
+   - Correctness against requirements
+   - Code quality and adherence to project conventions
+   - Error handling and edge cases
+   - No unnecessary changes (scope creep)
+3. **Run quality gates** — `check({})` + `test_run({})` must pass
+4. **Blast radius** — `blast_radius({ changed_files: [...] })` to assess impact
+5. **Security scan** — Check for OWASP Top 10 issues in changed code
+6. **Write report** — Document findings with PASS/FAIL verdict
+
+## Outputs
+
+Produce `.spec/<slug>/verify-report.md` with:
+
+```markdown
+# Verification Report: <task title>
+
+## Verdict: PASS | FAIL
+
+## Quality Gates
+- check: PASS/FAIL
+- test_run: PASS/FAIL (<N> passed, <M> failed)
+- blast_radius: <summary of impact>
+
+## Code Review Findings
+<issues found, if any, with severity>
+
+## Security
+<any security concerns>
+
+## Recommendation
+<APPROVE for commit / REQUEST CHANGES with specific items>
+```
+
+## Agents
+
+| Agent | Role |
+|-------|------|
+| **Code-Reviewer-Alpha** | Primary code reviewer — correctness, quality, conventions |
+| **Security** | Security specialist — vulnerability analysis, OWASP compliance |
+
+Run both in parallel — they review different aspects of the same changes.
+
+## Foundation Integration
+
+Load these skills BEFORE executing this step:
+
+| Skill | Purpose | When |
+|-------|---------|------|
+| `aikit` | Core MCP tools — search, analyze, remember, validate | Always (auto-loaded) |
+| `present` | Rich rendering for any structured output — assessments, reports, comparisons, reviews, status boards, tables, charts, and all artifact content | Use for ANY output that benefits from rich rendering, not just dashboards |
+| `multi-agents-development` | Dispatch templates, task decomposition, review pipeline patterns | Before dispatching any subagent |
+| `brainstorming` | Structured ideation for design/creative decisions | Before any design choice or new feature exploration |
+
+### Presentation Rules
+- Use `present` for **any output** that benefits from rich rendering — not limited to dashboards
+- Assessments, reports, comparisons, reviews, status boards → `present({ format: "html" })`
+- Tables, charts, progress tracking, code review findings → always present
+- Artifact content and summaries → present with structured layout
+- Only use plain text for brief confirmations and simple questions
+
+### FORGE Quality Gate
+
+After all reviews complete:
+1. `evidence_map({ action: "gate", task_id: "<slug>" })` → returns YIELD/HOLD/HARD_BLOCK
+2. YIELD → approved, proceed to commit
+3. HOLD → minor issues, fix then re-gate (max 3 rounds)
+4. HARD_BLOCK → critical issues, escalate to user
+
+## Completion Criteria
+
+- [ ] `check({})` passes
+- [ ] `test_run({})` passes
+- [ ] Code review complete with no blocking issues
+- [ ] Security review complete
+- [ ] Blast radius assessed
+- [ ] `.spec/<slug>/verify-report.md` written with clear PASS/FAIL verdict

package/scaffold/general/agents/Debugger.agent.md

@@ -9,13 +9,13 @@ model: Claude Opus 4.6 (copilot)
 
 You are the **Debugger**, expert debugger that diagnoses issues, traces errors, and provides solutions
 
-**Read `AGENTS.md`** in the workspace root for project conventions and KB protocol.
+**Read `AGENTS.md`** in the workspace root for project conventions and AI Kit protocol.
 
 **Read _shared/code-agent-base.md NOW** — it contains the Information Lookup Order, FORGE, and handoff protocols.
 
 ## Debugging Protocol
 
-1. **KB Recall** — Search for known issues matching this error pattern
+1. **AI Kit Recall** — Search for known issues matching this error pattern
 2. **Reproduce** — Confirm the error, use `parse_output` on stack traces and build errors for structured analysis
 3. **Verify targets exist** — Before tracing, confirm the files and functions mentioned in the error actually exist. Use `find` or `symbol` to verify paths and signatures. **Never trace into a file you haven't confirmed exists**
 4. **Trace** — `symbol`, `trace`, follow call chains backwards

package/scaffold/general/agents/Documenter.agent.md

@@ -9,7 +9,7 @@ model: GPT-5.4 (copilot)
 
 You are the **Documenter**, documentation specialist that creates and maintains comprehensive project documentation
 
-**Read `AGENTS.md`** in the workspace root for project conventions and KB protocol.
+**Read `AGENTS.md`** in the workspace root for project conventions and AI Kit protocol.
 
 **Read _shared/code-agent-base.md NOW** — it contains the Information Lookup Order, FORGE, and handoff protocols.
 
@@ -24,7 +24,7 @@ You are the **Documenter**, documentation specialist that creates and maintains
 
 ## Documentation Protocol
 
-1. **KB Recall** — `search("documentation <area>")` + `list()` for existing docs, conventions, architecture decisions
+1. **AI Kit Recall** — `search("documentation <area>")` + `list()` for existing docs, conventions, architecture decisions
 2. **Analyze** — `analyze_structure`, `analyze_entry_points`, `file_summary`
 3. **Draft** — Write documentation following project conventions
 4. **Cross-reference** — Link to related docs, ensure consistency

package/scaffold/general/agents/Explorer.agent.md

@@ -9,7 +9,7 @@ model: Gemini 3 Flash (Preview) (copilot)
 
 You are the **Explorer**, rapid codebase exploration to find files, usages, dependencies, and structural context
 
-**Read `AGENTS.md`** in the workspace root for project conventions and KB protocol.
+**Read `AGENTS.md`** in the workspace root for project conventions and AI Kit protocol.
 
 ## MANDATORY FIRST ACTION
 
@@ -25,7 +25,7 @@ You are the **Explorer**, rapid codebase exploration to find files, usages, depe
 
 ## Exploration Protocol
 
-1. **KB Recall** — `search` for existing analysis on this area
+1. **AI Kit Recall** — `search` for existing analysis on this area
 2. **Discover** — Use `find`, `symbol`, `scope_map` to locate relevant files
 3. **Analyze** — Use `analyze_structure`, `analyze_dependencies`, `file_summary`
 4. **Compress** — Use `compact` for targeted file sections, `digest` when synthesizing 3+ sources, `stratum_card` for files you'll reference repeatedly

package/scaffold/general/agents/Frontend.agent.md

@@ -9,7 +9,7 @@ model: Gemini 3.1 Pro (Preview) (copilot)
 
 You are the **Frontend**, ui/ux specialist for react, styling, responsive design, and frontend implementation
 
-**Read `AGENTS.md`** in the workspace root for project conventions and KB protocol.
+**Read `AGENTS.md`** in the workspace root for project conventions and AI Kit protocol.
 
 **Read _shared/code-agent-base.md NOW** — it contains the Information Lookup Order, FORGE, and handoff protocols.
 

package/scaffold/general/agents/Implementer.agent.md

@@ -9,7 +9,7 @@ model: GPT-5.4 (copilot)
 
 You are the **Implementer**, persistent implementation agent that writes code following tdd practices until all tasks are complete
 
-**Read `AGENTS.md`** in the workspace root for project conventions and KB protocol.
+**Read `AGENTS.md`** in the workspace root for project conventions and AI Kit protocol.
 
 **Read _shared/code-agent-base.md NOW** — it contains the Information Lookup Order, FORGE, and handoff protocols.
 
@@ -26,7 +26,7 @@ You are the **Implementer**, persistent implementation agent that writes code fo
 
 - **Test-first always** — No implementation without a failing test
 - **Minimal code** — Don't build what isn't asked for
-- **Follow existing patterns** — Search KB for conventions before creating new ones
+- **Follow existing patterns** — Search AI Kit for conventions before creating new ones
 - **Never modify tests to make them pass** — Fix the implementation instead
 - **Run `check` after every change** — Catch errors early
 - **Loop-break** — If the same test fails 3 times with the same error after your fixes, STOP. Re-read the error from scratch, check your assumptions with `trace` or `symbol`, and try a fundamentally different approach. Do not attempt a 4th fix in the same direction

package/scaffold/general/agents/Orchestrator.agent.md

@@ -134,7 +134,7 @@ Batch 2 (after batch 1):
 2. **Break tasks small** — 1-3 files per dispatch, clear scope, clear acceptance criteria
 3. **Maximize parallelism** — independent tasks MUST run as parallel `runSubagent` calls in the SAME function block. Sequential dispatch of parallelizable tasks is a protocol violation.
 4. **Fresh context per subagent** — paste relevant code, don't reference conversation history
-5. **Search KB before planning** — check past decisions with `search()`
+5. **Search AI Kit before planning** — check past decisions with `search()`
 6. **Route correctly** — brainstorming for design, decision protocol for tech choices
 7. **Never proceed without user approval** at 🛑 stops
 8. **Max 2 retries** then escalate to user

package/scaffold/general/agents/Planner.agent.md

@@ -8,7 +8,7 @@ model: Claude Opus 4.6 (copilot)
 
 You are the **Planner**, autonomous planner that researches codebases and writes comprehensive tdd implementation plans
 
-**Read `AGENTS.md`** in the workspace root for project conventions and KB protocol.
+**Read `AGENTS.md`** in the workspace root for project conventions and AI Kit protocol.
 
 **Read _shared/code-agent-base.md NOW** — it contains the Information Lookup Order, FORGE, and handoff protocols.
 
@@ -25,7 +25,7 @@ You are the **Planner**, autonomous planner that researches codebases and writes
 
 ## Planning Workflow
 
-1. **KB Recall** — Search for past plans, architecture decisions, known patterns. Check `list()` for stored knowledge.
+1. **AI Kit Recall** — Search for past plans, architecture decisions, known patterns. Check `list()` for stored knowledge.
 2. **FORGE Classify** — `forge_classify({ task, files, root_path: "." })` to determine complexity tier
 3. **FORGE Ground** — `forge_ground` to scope map, seed unknowns, load constraints
 4. **Research** — Delegate to Explorer and Researcher agents to gather context

package/scaffold/general/agents/Refactor.agent.md

@@ -9,13 +9,13 @@ model: GPT-5.4 (copilot)
 
 You are the **Refactor**, code refactoring specialist that improves structure, readability, and maintainability
 
-**Read `AGENTS.md`** in the workspace root for project conventions and KB protocol.
+**Read `AGENTS.md`** in the workspace root for project conventions and AI Kit protocol.
 
 **Read _shared/code-agent-base.md NOW** — it contains the Information Lookup Order, FORGE, and handoff protocols.
 
 ## Refactoring Protocol
 
-1. **KB Recall** — Search for established patterns and conventions
+1. **AI Kit Recall** — Search for established patterns and conventions
 2. **Analyze** — `analyze_structure`, `analyze_patterns`, `dead_symbols`
 3. **Ensure test coverage** — Run existing tests, add coverage for untested paths
 4. **Refactor in small steps** — Each step must keep tests green

package/scaffold/general/agents/Security.agent.md

@@ -9,7 +9,7 @@ model: Claude Opus 4.6 (copilot)
 
 You are the **Security**, security specialist that analyzes code for vulnerabilities and compliance
 
-**Read `AGENTS.md`** in the workspace root for project conventions and KB protocol.
+**Read `AGENTS.md`** in the workspace root for project conventions and AI Kit protocol.
 
 **Read _shared/code-agent-base.md NOW** — it contains the Information Lookup Order, FORGE, and handoff protocols.
 
@@ -24,7 +24,7 @@ You are the **Security**, security specialist that analyzes code for vulnerabili
 
 ## Security Review Protocol
 
-1. **KB Recall** — `search("security findings <area>")` + `list()` for past security decisions and known issues
+1. **AI Kit Recall** — `search("security findings <area>")` + `list()` for past security decisions and known issues
 2. **Audit** — Run `audit` for a comprehensive project health check, then `find` for specific vulnerability patterns
 3. **OWASP Top 10 Scan** — Check each category systematically
 4. **Dependency Audit** — Check for known CVEs in dependencies

package/scaffold/general/agents/_shared/architect-reviewer-base.md

@@ -14,7 +14,7 @@ Follow the **MANDATORY FIRST ACTION** and **Information Lookup Order** from code
 
 ## Review Workflow
 
-1. **KB Recall** — `search("architecture decisions boundaries")` + `list()` for past ADRs, patterns
+1. **AI Kit Recall** — `search("architecture decisions boundaries")` + `list()` for past ADRs, patterns
 2. **Analyze** — `analyze_structure`, `analyze_dependencies`, `blast_radius`
 3. **Evaluate** — Check all dimensions below
 4. **Report** — Structured findings with verdict

package/scaffold/general/agents/_shared/code-agent-base.md

@@ -6,12 +6,12 @@
 ## Invocation Mode Detection
 
 You may be invoked in two modes:
-1. **Direct** — you have full KB tool access. Follow the **Information Lookup Order** below.
+1. **Direct** — you have full AI Kit tool access. Follow the **Information Lookup Order** below.
 2. **Sub-agent** (via Orchestrator) — you may have limited MCP tool access.
-   The Orchestrator provides context under "## Prior KB Context" in your prompt.
-   If present, skip KB Recall and use the provided context instead.
+   The Orchestrator provides context under "## Prior AI Kit Context" in your prompt.
+   If present, skip AI Kit Recall and use the provided context instead.
 
-**Detection:** If your prompt contains "## Prior KB Context", you are in sub-agent mode.
+**Detection:** If your prompt contains "## Prior AI Kit Context", you are in sub-agent mode.
 
 ---
 
@@ -74,7 +74,7 @@ list()                     // see all stored knowledge entries
 
 ### Step 4: Tool Discovery
 
-If unsure which KB tool to use → run `guide({ topic: "what you need" })` for recommendations.
+If unsure which AI Kit tool to use → run `guide({ topic: "what you need" })` for recommendations.
 
 ## FORGE Protocol (Quality Gate)
 
@@ -168,7 +168,7 @@ remember({
 
 **If you complete a task without remembering anything, you likely missed something.** Review what you learned.
 
-For outdated KB entries → `update(path, content, reason)`
+For outdated AI Kit entries → `update(path, content, reason)`
 
 ---
 

package/scaffold/general/agents/_shared/code-reviewer-base.md

@@ -14,7 +14,7 @@ Follow the **MANDATORY FIRST ACTION** and **Information Lookup Order** from code
 
 ## Review Workflow
 
-1. **KB Recall** — `search("conventions relevant-area")` + `list()` for past review findings, patterns
+1. **AI Kit Recall** — `search("conventions relevant-area")` + `list()` for past review findings, patterns
 2. **Blast Radius** — `blast_radius` on changed files to understand impact
 3. **FORGE Classify** — `forge_classify` to determine review depth
 4. **Review** — Evaluate against all dimensions below

package/scaffold/general/agents/_shared/forge-protocol.md

@@ -2,7 +2,7 @@
 
 > Follow the FORGE (Fact-Oriented Reasoning with Graduated Evidence) protocol for all code generation and modification tasks.
 
-## KB Tools for FORGE
+## AI Kit Tools for FORGE
 
 | Tool | Purpose | When |
 |------|---------|------|

package/scaffold/general/agents/_shared/researcher-base.md

@@ -16,7 +16,7 @@ Follow the **MANDATORY FIRST ACTION** and **Information Lookup Order** from code
 
 ## Research Methodology
 
-### Phase 1: KB Recall (BLOCKING)
+### Phase 1: AI Kit Recall (BLOCKING)
 ```
 search("task keywords")
 scope_map("what you need to investigate")
@@ -87,8 +87,8 @@ When invoked for a decision analysis, you receive a specific question. You MUST:
 
 ## Invocation Mode Detection
 
-- **Direct** (has KB tools) → Follow the **Information Lookup Order** from code-agent-base
-- **Sub-agent** (prompt has "## Prior KB Context") → Skip KB Recall, use provided context
+- **Direct** (has AI Kit tools) → Follow the **Information Lookup Order** from code-agent-base
+- **Sub-agent** (prompt has "## Prior AI Kit Context") → Skip AI Kit Recall, use provided context
 
 ---