@vpxa/aikit 0.1.74 → 0.1.75

package/scaffold/_preview/skills/aikit/SKILL.md

@@ -1,754 +0,0 @@
----
-name: aikit
-description: "Use the @vpxa/aikit AI Kit MCP server for codebase search, analysis, and persistent memory. Load this skill when using aikit_search, aikit_remember, aikit_analyze_*, or any aikit_* tool. Covers all 82 MCP tools: search (hybrid/semantic/keyword), code analysis (structure, dependencies, symbols, patterns, entry points, diagrams, blast radius), knowledge graph (auto-populated module/symbol/import graph with traversal), context management (worksets, stash, checkpoints, restore, lanes), code manipulation (rename, codemod, eval), knowledge management (remember/read/update/forget), web access (fetch, search, http), FORGE protocol (ground, classify, evidence map, stratum cards, digest), brainstorming (interactive ideation sessions), presentation (rich dashboards via present tool), onboarding (full codebase analysis in one call), and developer utilities (regex, encode, measure, changelog, schema-validate, snippet, env, time)."
-metadata:
-  category: cross-cutting
-  domain: general
-  applicability: always
-  inputs: [codebase]
-  outputs: [search-results, analysis, knowledge]
-  relatedSkills: [present]
----
-
-# @vpxa/aikit — AI Kit
-
-Local-first AI developer toolkit — 82 MCP tools for search, analysis, context compression, FORGE quality gates, knowledge management, code manipulation, execution, web access, brainstorming, presentation, and developer utilities.
-
-## When to Use
-
-- You need long-term memory across coding sessions
-- You want to search a codebase semantically (by meaning, not just keywords)
-- You need to compress large contexts to focus on what matters
-- You want structured output from build tools (tsc, vitest, biome, git)
-- You need to plan which files to read for a task
-- You want to safely explore refactors in isolated lanes
-- You need to rename symbols, apply codemods, or run code transformations
-- You want to fetch and read web pages or search the web
-- You need to make HTTP requests, test APIs, or debug endpoints
-- You want to test regex patterns, encode/decode data, or validate JSON schemas
-- You need code complexity metrics or a git changelog
-- You want to save and reuse code snippets across sessions
-
-## Skills Reference
-
-| Context | Skill | Load when |
-|---------|-------|----------|
-| Repository access recovery | `repo-access` | When encountering git auth failures, accessing private/enterprise repos, or when `web_fetch`/`http` returns auth errors on repository URLs. |
-
-## Architecture
-
-10-package monorepo published as a single npm package:
-
-```
-core → store → embeddings → chunker → indexer → analyzers → tools → server → cli → tui
-```
-
-- **MCP server**: 82 tools + 2 resources (via `@modelcontextprotocol/sdk`)
-- **CLI**: 45 commands (thin dispatcher + 10 command groups)
-- **Search**: Hybrid vector + keyword + RRF fusion
-- **Embeddings**: ONNX local (mxbai-embed-large-v1, 1024 dimensions)
-- **Vector store**: LanceDB (embedded, zero infrastructure)
-- **Chunking**: Tree-sitter AST (TS/JS/Python/Go/Rust/Java) + regex fallback
-- **TUI**: Ink/React dashboard for human monitoring (search, status, curated, activity log)
-
-## Session Protocol (MANDATORY)
-
-### Start (do ALL)
-```
-flow_status({})                                                # Check/resume active flow FIRST
-# If flow active → flow_read_instruction({ step }) → follow step instructions
-status({})                                                     # Check AI Kit health + onboard state
-# If onboard not run → onboard({ path: "." })                 # First-time codebase analysis
-flow_list({})                                                  # See available flows
-# Select flow based on task → flow_start({ flow: "<name>", topic: "<task>" })  # Start — creates .flows/{topic}/
-list()                                                         # See stored knowledge
-search({ query: "SESSION CHECKPOINT", origin: "curated" })     # Resume prior work
-```
-
-### During Session
-```
-search → scope_map → symbol → trace  (orient)
-check → test_run                             (validate changes)
-remember                                         (capture insights)
-```
-
-### End of Session
-```
-session_digest({ persist: true })                              # Auto-capture session activity
-remember({ title: "Session checkpoint: <topic>", content: "<what was done, decisions made, next steps>", category: "conventions" })
-```
-
-## Tool Catalog (82 tools)
-
-### Search & Discovery (8)
-| Tool | CLI | Purpose |
-|------|-----|---------|
-| `search` | `aikit search` | Hybrid/semantic/keyword search with `search_mode` param |
-| `find` | `aikit find` | Federated search: vector + FTS + glob + regex in one call. Use `mode: 'examples'` to find usage examples. |
-| `symbol` | `aikit symbol` | Resolve symbol definition, imports, and references |
-| `lookup` | `aikit lookup` | Full-file retrieval by path or record ID |
-| `scope_map` | `aikit scope-map` | Task-scoped reading plan with token estimates |
-| `trace` | `aikit trace` | Forward/backward flow tracing through call chains |
-| `dead_symbols` | `aikit dead-symbols` | Find exported symbols never imported — separates source (actionable) from docs (informational). Accepts `path` to scope the search. |
-| `file_summary` | `aikit summarize` | Structural overview of a file (exports, imports, functions) |
-
-### Code Analysis (7)
-| Tool | CLI | Purpose |
-|------|-----|---------|
-| `analyze_structure` | `aikit analyze structure` | Project structure overview |
-| `analyze_dependencies` | `aikit analyze deps` | Dependency graph with confidence |
-| `analyze_symbols` | `aikit analyze symbols` | Symbol extraction and cross-references |
-| `analyze_patterns` | `aikit analyze patterns` | Design pattern detection |
-| `analyze_entry_points` | `aikit analyze entry-points` | Find entry points: handlers, CDK constructs, test suites, package exports (walks workspace packages) |
-| `analyze_diagram` | `aikit analyze diagram` | Generate Mermaid diagrams |
-| `blast_radius` | `aikit analyze blast-radius` | Change impact analysis |
-
-### Context Management (6)
-| Tool | CLI | Purpose |
-|------|-----|---------|
-| `compact` | `aikit compact` | Compress text to relevant sections using embeddings (no LLM). Accepts `path` for server-side file read. |
-| `workset` | `aikit workset` | Named file set management (save/load/add/remove) |
-| `stash` | `aikit stash` | Named key-value store for session data |
-| `checkpoint` | `aikit checkpoint` | Save/restore session checkpoints |
-| `restore` | `aikit restore` | Restore a previously saved checkpoint |
-| `parse_output` | `aikit parse-output` | Parse tsc/vitest/biome/git output → structured JSON |
-
-### Code Manipulation (4)
-| Tool | CLI | Purpose |
-|------|-----|---------|
-| `rename` | `aikit rename` | Smart whole-word symbol rename across files (dry-run supported) |
-| `codemod` | `aikit codemod` | Regex-based code transformations with rules (dry-run supported) |
-| `diff_parse` | `aikit diff` | Parse unified diff → structured changes |
-| `data_transform` | `aikit transform` | JQ-like JSON transformations |
-
-### Execution & Validation (5)
-| Tool | CLI | Purpose |
-|------|-----|---------|
-| `eval` | `aikit eval` | Sandboxed JavaScript/TypeScript execution |
-| `check` | `aikit check` | Incremental typecheck + lint. `detail` param: summary (default, ~300 tokens), errors, full |
-| `test_run` | `aikit test` | Run tests with structured pass/fail results |
-| `batch` | `aikit batch` | Execute multiple operations in parallel |
-| `audit` | `aikit audit` | Unified project audit: structure, deps, patterns, health, dead symbols, check, entry points → synthesized report with score and recommendations. 6 round-trips → 1. |
-
-### Knowledge Management (6)
-| Tool | CLI | Purpose |
-|------|-----|---------|
-| `remember` | `aikit remember` | Store a curated knowledge entry |
-| `update` | `aikit update` | Update an existing entry |
-| `forget` | `aikit forget` | Delete an entry (requires reason) |
-| `read` | `aikit read` | Read a curated entry by path |
-| `list` | `aikit list` | List curated entries |
-| `produce_knowledge` | — | Auto-generate knowledge from analysis |
-
-### Auto-Knowledge (automatic background extraction)
-
-Auto-knowledge runs automatically in the background after every tool completion. It extracts useful facts from tool outputs and stores them in curated memory — no manual action required.
-
-**What gets captured:**
-
-| Extractor | Triggers on | What it stores |
-|-----------|-------------|----------------|
-| Test results | `check`, `test_run` | Framework detection (vitest/jest/mocha), test file naming patterns |
-| Environment | `env`, `config`, `status` | Node.js version, OS, workspace path, store backend, embedding model |
-| Research | `web_search`, `web_fetch`, `search` | Web research findings, fetched page summaries |
-| Conventions | `check`, `analyze_patterns`, `analyze_structure`, `onboard` | Linter/formatter, TypeScript strict mode, package manager, monorepo detection |
-| Build commands | `check`, `test_run` | Verified check results, test summaries, test runner commands |
-| Codebase insights | `analyze_*`, `scope_map`, `blast_radius`, `onboard` | Structure analysis, dependency info, entry points, impact analysis |
-| Tool failures | All tools (global) | Classified actionable errors (filters out transient network/ENOENT errors) |
-
-**Quality controls:**
-- **Quality gate**: Facts scored 0-1; only facts >= 0.3 are stored
-- **Dedup**: Checks existing curated titles + in-memory hash dedup
-- **TTL**: Transient facts (errors, blast radius, search context) automatically expire after 1-2 hours
-- **Session limit**: Maximum 50 auto-knowledge facts per session
-
-**Searching auto-knowledge:**
-Auto-knowledge facts are stored as regular curated entries. Search them with:
-```
-search({ query: "error patterns", origin: "curated" })
-search({ query: "conventions", origin: "curated" })
-list({ category: "conventions" })
-list({ tags: ["errors"] })
-```
-
-### Verified Lanes (1 tool, 6 actions)
-| Tool | CLI | Purpose |
-|------|-----|---------|
-| `lane` | `aikit lane` | Manage isolated file copies for parallel exploration |
-
-Lane actions: `create` (copy files to lane), `list`, `status` (modified/added/deleted), `diff` (line-level diff), `merge` (apply back to originals), `discard`.
-
-### Git & Environment (4)
-| Tool | CLI | Purpose |
-|------|-----|---------|
-| `git_context` | `aikit git` | Branch, status, recent commits |
-| `process` | `aikit proc` | Process supervisor (start/stop/logs) |
-| `watch` | `aikit watch` | Filesystem watcher |
-| `delegate` | `aikit delegate` | Delegate subtask to local Ollama model |
-
-### Web & Network (3)
-| Tool | CLI | Purpose |
-|------|-----|---------|
-| `web_fetch` | — | Fetch web page → markdown/raw/links/outline for LLM consumption |
-| `web_search` | — | Search the web via DuckDuckGo (no API key needed) |
-| `http` | — | Make HTTP requests for API testing/debugging |
-
-### Developer Utilities (8)
-| Tool | CLI | Purpose |
-|------|-----|---------|
-| `regex_test` | — | Test regex patterns with match/replace/split modes |
-| `encode` | — | Base64, URL, SHA-256, MD5, hex encode/decode, JWT decode |
-| `measure` | — | Code complexity metrics (cyclomatic, cognitive complexity, lines, functions) |
-| `changelog` | — | Generate changelog from git history (conventional commits) |
-| `schema_validate` | — | Validate JSON data against JSON Schema |
-| `snippet` | — | Save/get/search/delete persistent code snippets |
-| `env` | — | System and runtime environment info (sensitive values redacted) |
-| `time` | — | Date parsing, timezone conversion, duration math |
-
-### FORGE Quality Gates (5)
-| Tool | CLI | Purpose |
-|------|-----|---------|
-| `forge_ground` | — | Full Ground phase: classify tier, scope map, unknowns, constraints |
-| `forge_classify` | — | Quick tier classification (Floor/Standard/Critical) |
-| `evidence_map` | — | CRUD + Gate evaluation for verified/assumed/unknown claims. Safety gate tags (`provenance`/`commitment`/`coverage`) enable mandatory pre-YIELD checks |
-| `stratum_card` | — | Generate T1/T2 compressed context cards from files (10-100x token reduction) |
-| `digest` | — | Compress N text sources into token-budgeted summary |
-
-### System (9)
-| Tool | CLI | Purpose |
-|------|-----|---------|
-| `config` | `aikit config` | View or update project configuration (kb.config.json) |
-| `status` | `aikit status` | Index statistics |
-| `reindex` | `aikit reindex` | Rebuild index |
-| `health` | `aikit health` | Project health checks (package.json, tsconfig, lockfile, circular deps) |
-| `guide` | `aikit guide` | Tool discovery — given a goal, recommends tools and workflow order |
-| `onboard` | `aikit onboard` | Full codebase onboarding in one call (structure + deps + patterns + knowledge) |
-| `graph` | `aikit graph` | Query the auto-populated knowledge graph (modules, symbols, imports) |
-| `queue` | `aikit queue` | Task queue for sequential agent operations (create/push/next/done/fail) |
-| `replay` | `aikit replay` | View or clear the audit trail of tool invocations (action: list/clear) |
-
-### Flows (11)
-| Tool | CLI | Purpose |
-|------|-----|---------|
-| `flow_list` | `aikit flow list` | List available flows and active run |
-| `flow_info` | `aikit flow info` | Get flow details including steps and skill paths |
-| `flow_start` | `aikit flow start` | Start a flow with topic — creates `.flows/{topic-slug}/` run directory |
-| `flow_step` | `aikit flow step` | Advance, skip, or redo the current step |
-| `flow_status` | `aikit flow status` | Check active run including slug, runDir, artifactsPath |
-| `flow_read_instruction` | `aikit flow read-instruction` | Read instruction with `{{artifacts_path}}` and `{{run_dir}}` resolved |
-| `flow_reset` | `aikit flow reset` | Abandon the active flow (preserves run directory) |
-| `flow_runs` | `aikit flow runs` | List all flow runs (current and past) |
-| `flow_add` | `aikit flow add` | Add a custom flow from a directory |
-| `flow_update` | `aikit flow update` | Update an existing custom flow |
-| `flow_remove` | `aikit flow remove` | Remove a custom flow |
-
-### Presentation (1)
-| Tool | CLI | Purpose |
-|------|-----|---------|
-| `present` | — | Rich dashboards, charts, tables, timelines. Use `format: "browser"` then `openBrowserPage` to display. **In CLI mode (no VS Code chat), always use `format: "browser"`** — `html` UIResource is invisible in terminal. |
-
-### Brainstorming (1)
-| Tool | CLI | Purpose |
-|------|-----|---------|
-| `brainstorm` | — | Interactive brainstorming and ideation sessions with structured output |
-
-### Meta-Tools — Tool Discovery (3)
-| Tool | CLI | Purpose |
-|------|-----|---------|
-| `list_tools` | — | List all active AI Kit tools with names, titles, and categories. Accepts optional `category` filter. Use for initial tool discovery. |
-| `describe_tool` | — | Get detailed metadata for a specific tool (title, categories, annotations). Use after `list_tools` to understand a tool before calling it. |
-| `search_tools` | — | Search active tools by keyword across names, titles, and categories. Use when you know what you need but not the tool name. |
-
-### Session Management (1)
-| Tool | CLI | Purpose |
-|------|-----|---------|
-| `session_digest` | — | Generate a compressed digest of session activity (replay log, stash, checkpoints). Options: `scope` (tools/stash/all), `since`, `last`, `focus`, `mode` (deterministic/sampling), `tokenBudget`, `persist`. Use at session end for handoff or mid-session to review what happened. |
-
-## Flow System
-
-Flows are multi-step guided workflows that structure complex tasks. Each step has a skill file with detailed instructions, required artifacts, and agent assignments.
-
-### Built-in Flows
-
-| Flow | Steps | Use When |
-|------|-------|----------|
-| `aikit:basic` | assess → implement → verify | Bug fixes, config changes, small features |
-| `aikit:advanced` | spec → plan → task → execute → verify | New modules, cross-service changes, architectural work |
-
-### Flow Lifecycle
-
-```text
-flow_list()                          # See available flows
-flow_info({ flow: "aikit:basic" })   # View steps, skills, agents
-flow_start({ flow: "aikit:basic", topic: "Fix login bug" })  # Start — creates .flows/fix-login-bug/
-flow_read_instruction()              # Read current step's instructions ({{artifacts_path}} resolved)
-# ... do the work described in the instruction ...
-flow_step({ action: "next" })        # Advance to next step
-flow_step({ action: "skip" })        # Skip current step
-flow_step({ action: "redo" })        # Redo current step
-flow_status()                        # Check progress (includes slug, runDir, artifactsPath, phase, isEpilogue)
-flow_reset()                         # Abandon active flow
-flow_runs()                          # List all runs (current + past)
-# Epilogue steps (mandatory, injected after every flow):
-# After last flow step → _docs-sync epilogue runs automatically
-# flow_status() shows phase: 'after', isEpilogue: true during epilogue
-```
-
-Custom flow lifecycle management:
-
-```text
-flow_add({ source: ".github/flows/my-flow" })
-flow_update({ name: "my-flow" })
-flow_remove({ name: "my-flow" })
-```
-
-### Creating Custom Flows
-
-1. Create a directory under `.github/flows/<flow-name>/`
-2. Add `manifest.yaml`:
-
-```yaml
-name: my-flow
-version: "1.0.0"
-description: "My custom flow"
-artifacts_dir: .spec
-steps:
-  - id: design
-    name: Design
-    instruction: steps/design/README.md
-    description: "Create the design document"
-    produces: [design.md]
-    requires: []
-    agents: [Planner]
-  - id: implement
-    name: Implement
-    instruction: steps/implement/README.md
-    description: "Implement the design"
-    produces: [code]
-    requires: [design]
-    agents: [Implementer]
-agents:
-  - agents/planner.agent.md
-install: []
-```
-
-3. Add skill files under `.github/flows/<flow-name>/skills/<step-id>/SKILL.md`
-4. The flow appears in `flow_list()` automatically
-
-### How Flows Are Delivered
-
-- **Built-in flows** ship with the AI Kit MCP server in `scaffold/flows/`
-- `aikit init` copies them to `.github/flows/` in your workspace
-- At runtime, flow tools resolve paths to `.github/flows/` (workspace-local copies)
-- Custom flows placed in `.github/flows/` are discovered alongside built-in ones
-
-### Agent-Flow Integration
-
-- All code agents have a "Flows" section instructing them to check `flow_status()` first
-- If a flow is active, the agent follows the current step's instruction via `flow_read_instruction()`
-- After completing a step's work, advance with `flow_step({ action: "next" })`
-- The **Orchestrator** selects and starts flows; other agents follow them
-- The **Orchestrator** specifies `aikit` skill loading — all agents should load `aikit` skill to access flow tools
-
-## CRITICAL: Use AI Kit Tools Instead of Native IDE Tools
-
-AI Kit tools provide **10x richer output** than native IDE tools — with AST-analyzed call graphs, scope context, import classification, and cognitive complexity. **You MUST use AI Kit tools instead of native read/search tools.**
-
-### ⛔ PROHIBITED: Native File Reading
-
-**`read_file` / `read_file_raw` MUST NOT be used to understand code.** They waste tokens and miss structural information.
-
-The **ONLY** acceptable use of `read_file`: getting exact lines immediately before an edit (to verify the `old_str` for replacement). Even then, use `file_summary` first to identify which lines to read.
-
-### Tool Replacement Table
-
-| ❌ NEVER do this | ✅ Use AI Kit Tool | Why |
-|---|---|---|
-| `read_file` (full file) | `file_summary` | Exports, imports, call edges — **10x fewer tokens** |
-| `read_file` (specific section) | `compact({ path, query })` | Server-side read + extract — **5-20x reduction** |
-| `grep_search` / `textSearch` | `search` | Semantic + keyword hybrid across all indexed content |
-| `grep_search` for a symbol | `symbol` | Definition + references **with scope context** |
-| Multiple `read_file` calls | `digest` | Compresses multiple sources into token-budgeted summary |
-| `listDirectory` + `read_file` | `scope_map` | Identifies relevant files for a task automatically |
-| Manual code tracing | `trace` | AST call-graph traversal with scope context |
-| Line counting / `wc` | `measure` | Lines, complexity, **cognitive complexity**, functions |
-| Grep for unused exports | `dead_symbols` | AST-powered export detection with regex fallback |
-| Repeated file reads | `stratum_card` | Reusable compressed context — **10-100x reduction** |
-| `fetch_webpage` | `web_fetch` | Readability extract + token budget — richer output |
-| Web research / browsing | `web_search` | Structured web results without browser — **unique to KB** |
-
-### Decision Tree — How to Read Code
-
-```
-Need to understand a file?
-├─ Just structure?        → file_summary (exports, imports, call edges — ~50 tokens)
-├─ Specific section?      → compact({ path, query }) — 5-20x reduction
-├─ Multiple files?        → digest (multi-source compression — token-budgeted)
-├─ Repeated reference?    → stratum_card (T1/T2 card — 10-100x reduction)
-├─ Need exact lines to EDIT? → read_file (the ONLY acceptable use)
-└─ "I want to read the whole file" → ⛔ STOP. Use file_summary or compact instead.
-```
-
-### Decision Tree — Need Structural Relationships?
-
-When vector search and file reads don't answer the question (e.g. "who imports this?",
-"what does this depend on?", "how are these files connected?"), use `graph`:
-
-```
-Need to understand relationships between code?
-├─ Who imports / calls this?     → graph({action:'find_nodes', name_pattern}) → graph({action:'neighbors', node_id, direction:'incoming'})
-├─ What does this depend on?     → graph({action:'neighbors', node_id, direction:'outgoing'})
-├─ Full context for a symbol?    → graph({action:'symbol360', name})
-├─ Related files within N hops?  → graph({action:'traverse', node_id, max_depth:2})
-├─ Layer/module isolation check? → graph({action:'depth_traverse', node_id, max_depth:3})
-└─ Graph size/health?            → graph({action:'stats'})
-```
-
-**Use this BEFORE** reaching for `analyze_dependencies` (slower, less precise) or manually
-tracing via `symbol` + `trace` chains. The graph is auto-populated during indexing.
-
-### What AI Kit Tools Return (AST-Enhanced)
-
-These tools use Tree-sitter WASM to analyze source code at the AST level, providing structured data that raw file reads cannot:
-
-| Tool | Rich Output |
-|------|-------------|
-| `file_summary` | Imports classified as **external vs internal** (`isExternal` flag). **Call edges** between functions (e.g., `handleRequest() → validateInput() @ line 42`). `exported` flag on interfaces and types. Import count breakdown. |
-| `symbol` | References include **scope** — which function/class/method contains each usage (e.g., `referenced in processOrder() at auth-service.ts:55`). |
-| `trace` | **Call-graph edges** discovered via AST syntax tree, not text matching. Supports forward (who does X call?) and backward (who calls X?) tracing. Scope context on each node. |
-| `measure` | **Cognitive complexity** — weights nesting depth (nested `if` inside `for` inside `try` scores higher). More useful than cyclomatic complexity for understanding code difficulty. |
-| `dead_symbols` | **AST export enumeration** — catches `export default`, barrel re-exports (`export { x } from`), `export =`, and `export type`. Regex fallback for non-AST-supported languages. |
-
-### Example: `file_summary` Output
-
-```
-src/auth-service.ts
-Language: typescript | Lines: 180 | Estimated tokens: ~1400
-
-Imports (6): 3 external, 3 internal
-  - import { hash } from 'bcrypt'          [external]
-  - import { UserRepo } from './user-repo' [internal]
-
-Functions (4):
-  - authenticate @ line 22 [exported]
-  - validateToken @ line 55 [exported]
-  - hashPassword @ line 90
-  - generateJwt @ line 110
-
-Call edges (12 intra-file):
-  - authenticate() → hashPassword() @ line 35
-  - authenticate() → generateJwt() @ line 42
-  - validateToken() → UserRepo.findById() @ line 68
-
-Interfaces (2):
-  - AuthResult @ line 8 [exported]
-  - TokenPayload @ line 14
-```
-
-Compare: `read_file` would cost ~1400 tokens for raw text. `file_summary` gives structured data in ~120 tokens — **12x reduction** with richer information.
-
-## Search Strategy
-
-1. **Start broad**: `search({ query: "topic", search_mode: "hybrid" })`
-2. **Narrow**: Add `content_type`, `origin`, or `category` filters
-3. **Exact match**: Use `search_mode: "keyword"` for identifiers
-4. **Federated**: Use `find` to combine vector + glob + regex
-
-## Workflow Chains
-
-### Codebase Onboarding
-```
-analyze_structure({ path: "src/" })
-→ analyze_dependencies({ path: "src/" })
-→ analyze_entry_points({ path: "src/" })
-→ produce_knowledge({ path: "src/" })
-→ remember({ title: "Codebase onboarding complete", ... })
-```
-
-### Planning a Task
-```
-scope_map({ task: "implement user auth" })
-→ compact({ path: "src/auth.ts", query: "auth flow" })
-→ workset({ action: "save", name: "auth-task", files: [...] })
-```
-
-### Bug Investigation
-```
-parse_output({ output: <error> }) → symbol({ name: "failingFn" })
-→ trace({ symbol: "failingFn", direction: "backward" })
-→ blast_radius({ changed_files: ["suspect.ts"] })
-→ eval({ code: "hypothesis test" }) → check({ files: ["suspect.ts"] })
-```
-
-### Safe Refactor with Lanes
-```
-scope_map({ task: "rename UserService" })
-→ lane({ action: "create", name: "refactor", files: [...] })
-→ [make changes in lane files]
-→ lane({ action: "diff", name: "refactor" })
-→ check({}) → test_run({})
-→ lane({ action: "merge", name: "refactor" })
-```
-
-### Lane — isolated read-only exploration
-
-`lane({ action:'create', name })` creates an isolated copy of the workspace. Use to try approach A vs B WITHOUT touching canonical source. Other actions: `list`, `diff`, `delete`. Compare with `lane({ action:'diff', names:['a','b'] })`. Do NOT use `lane` for actual refactors — use `checkpoint` instead (`checkpoint` = reversible on canonical source; `lane` = isolated copies for comparison).
-
-### After Making Changes
-```
-blast_radius({ changed_files: ["src/auth.ts"] })
-→ check({}) → test_run({ grep: "auth" })
-→ reindex()
-→ remember({ title: "Implemented auth", content: "..." })
-```
-
-### Pre-Commit Validation
-```
-git_context({ diff: true })
-→ diff_parse({ diff: <staged diff> })
-→ blast_radius({ changed_files: [...] })
-→ check({}) → test_run({})
-```
-
----
-
-## Persistent Memory (Long-Term Knowledge)
-
-AI Kit provides cross-session persistent memory via a curated knowledge store. Use it to remember decisions, patterns, conventions, and context that should survive beyond the current conversation.
-
-### Writing to Memory
-
-| Tool | Purpose | Example |
-|------|---------|---------|
-| `remember` | Store a new knowledge entry | `remember({ title: "Auth uses JWT RS256", content: "All API auth uses RS256 JWT tokens issued by /auth/token. Refresh via httpOnly cookie.", category: "decisions" })` |
-| `update` | Modify an existing entry | `update({ id: "<entry-id>", content: "Updated: now also supports Ed25519" })` |
-| `produce_knowledge` | Auto-generate analysis entries from code | `produce_knowledge({ path: "src/" })` |
-
-**Categories** — use these to organize entries:
-- `conventions` — coding standards, naming rules, file organization
-- `decisions` — architecture decisions, technology choices, trade-offs made
-- `patterns` — recurring code patterns, design patterns in use
-- `context` — project context, domain knowledge, business rules
-- `session` — session checkpoints for resuming work
-
-### Reading from Memory
-
-| Tool | Purpose | Example |
-|------|---------|---------|
-| `list` | Browse all stored entries | `list()` or `list({ category: "decisions" })` |
-| `read` | Read a specific entry by ID | `read({ id: "<entry-id>" })` |
-| `search` | Find entries by content/query | `search({ query: "authentication", origin: "curated" })` |
-| `forget` | Remove an outdated entry | `forget({ id: "<entry-id>" })` |
-
-### When to Remember
-
-| Situation | What to store | Category |
-|-----------|--------------|----------|
-| Architecture decision made | Decision + rationale + alternatives considered | `decisions` |
-| Pattern discovered in codebase | Pattern description + example locations | `patterns` |
-| Convention established | Rule + enforcement approach | `conventions` |
-| Session ending | Checkpoint: what was done, what's next, blockers | `session` |
-| Bug root cause found | Root cause + fix approach + prevention strategy | `context` |
-| External API behavior learned | Behavior quirks, rate limits, gotchas | `context` |
-
-### Session Checkpoint Pattern
-
-At the END of every meaningful work session:
-```
-remember({
-  title: "Session checkpoint: <topic>",
-  content: "## Done\n- <completed items>\n\n## Decisions\n- <key decisions made>\n\n## Next\n- <pending work>\n\n## Blockers\n- <issues encountered>",
-  category: "session"
-})
-```
-
-At the START of the next session:
-```
-search({ query: "SESSION CHECKPOINT", origin: "curated" })    # Find last checkpoint
-list({ category: "session" })                                  # Browse all checkpoints
-```
-
-### Memory Best Practices
-
-1. **Remember decisions, not code** — store *why*, not *what*. Code changes; rationale persists.
-2. **Search before remembering** — avoid duplicates: `search({ query: "..." })` first.
-3. **Use categories** — structured categories enable filtered `list()` queries.
-4. **Checkpoint regularly** — don't wait for session end. Checkpoint at milestones.
-5. **Clean up** — `forget()` outdated entries. Memory is only valuable when accurate.
-6. **Cross-reference** — mention related entry titles in content for discoverability.
-
-## CLI Quick Reference
-
-```bash
-aikit init              # Scaffold AI Kit in current directory
-aikit init --force      # Overwrite all scaffold/skill files
-aikit init --guide      # JSON report of stale files for LLM-driven updates
-aikit serve             # Start MCP server (stdio or HTTP)
-aikit search <q>    # Hybrid search
-aikit find <q>      # Federated search
-aikit symbol <name> # Resolve symbol
-aikit scope-map <t> # Task reading plan
-aikit compact <q>   # Context compression (--path file or stdin)
-aikit check         # Typecheck + lint (--detail summary|errors|full)
-aikit test          # Run tests
-aikit rename <old> <new> <path>  # Rename symbol
-aikit lane create <name> --files f1,f2  # Create lane
-aikit lane diff <name>  # View lane changes
-aikit lane merge <name> # Merge lane back
-aikit status        # Index stats
-aikit reindex       # Rebuild index
-```
-
-## Configuration
-
-`kb.config.json` in project root:
-```json
-{
-  "sources": [{ "path": ".", "excludePatterns": ["node_modules/**", "**/node_modules/**", "dist/**", "coverage/**", ".aikit-data/**"] }],
-  "indexing": { "chunkSize": 1500, "chunkOverlap": 200, "minChunkSize": 100, "concurrency": 5 },
-  "embedding": { "model": "mixedbread-ai/mxbai-embed-large-v1", "dimensions": 1024 },
-  "store": { "backend": "lancedb", "path": ".aikit-data" },
-  "curated": { "path": "curated", "adapter": "filesystem" }
-}
-```
-
-## Tool Profiles
-
-Tool profiles control which subset of the 82 tools are active. Profiles reduce token overhead by exposing only relevant tools for a given task.
-
-### Built-in Profiles
-
-| Profile | Description | Use When |
-|---------|-------------|----------|
-| `full` | All tools enabled (default) | General development, orchestration |
-| `safe` | Read-only tools — no file/state modifications | Code review, analysis, research |
-| `research` | Search, analysis, knowledge, web access | Investigation, documentation |
-| `minimal` | Essential tools only — search, check, test | Simple tasks, low-token budgets |
-| `discovery` | Full toolset + meta-tools for guided exploration | New users, onboarding, tool learning |
-
-### Activating a Profile
-
-Set `toolProfile` in `kb.config.json`:
-
-```json
-{
-  "toolProfile": "research"
-}
-```
-
-Base tools (`status`, `config`, `guide`, `health`) are **always available** regardless of profile.
-
-### Meta-Tool Discovery Pattern (Token Cost Reduction)
-
-Instead of loading all 82 tool descriptions at session start, use the `discovery` profile:
-
-1. `list_tools()` — get a compact list of tool names + categories (~50 tokens)
-2. `search_tools({ query: "what I need" })` — find relevant tools by keyword
-3. `describe_tool({ tool_name: "specific_tool" })` — get full metadata only for tools you'll use
-
-This pattern reduces initial tool-loading cost from ~3000 tokens to ~200 tokens.
-
-## IDE Integration
-
-### VS Code — HTTP mode (recommended for development)
-```json
-// .vscode/mcp.json
-{
-  "servers": {
-    "kb": {
-      "type": "http",
-      "url": "http://localhost:3210/mcp"
-    }
-  }
-}
-```
-Start server: `npx aikit serve --http --port 3210`
-
-### VS Code — stdio mode (no separate server)
-```json
-{
-  "servers": {
-    "kb": {
-      "type": "stdio",
-      "command": "npx",
-      "args": ["@vpxa/aikit", "serve", "--stdio"]
-    }
-  }
-}
-```
-
-### Claude Code (`.mcp.json`)
-```json
-{
-  "mcpServers": {
-    "kb": {
-      "command": "npx",
-      "args": ["@vpxa/aikit", "serve"]
-    }
-  }
-}
-```
-
-## Development (Self-Dogfooding)
-
-When developing @vpxa/aikit itself, use the tool on its own codebase:
-
-```bash
-# Build → Reindex → Use loop
-pnpm build                          # Build all 10 packages
-node bin/aikit.mjs reindex          # Index own source into LanceDB
-node bin/aikit.mjs search "query"   # Search own code
-node bin/aikit.mjs symbol "FnName"  # Resolve symbols in own code
-node bin/aikit.mjs check            # Typecheck + lint
-pnpm test                           # Run 287+ tests
-
-# Start MCP server for agent use during development
-node bin/aikit.mjs serve --http --port 3210
-```
-
-**Rules:**
-- Always `pnpm build` before using CLI/server (runs from `dist/`)
-- Always `reindex` after structural code changes
-- LanceDB is single-process — don't run CLI and HTTP server simultaneously
-- Curated entries in `curated/` survive reindex and are indexed separately
-
----
-
-## Flows
-
-Flows are structured multi-step workflows that guide agents through complex tasks. They are the **primary workflow system** — use them instead of ad-hoc planning when a matching flow exists.
-
-### Flow Tools
-
-| Tool | Purpose |
-|------|---------|
-| `flow_status` | Check if a flow is active + current step + phase (before/flow/after) + isEpilogue |
-| `flow_list` | List available flows |
-| `flow_info` | Get flow details including steps and skill paths |
-| `flow_start` | Start a named flow |
-| `flow_step` | Advance: `next`, `skip`, or `redo` current step |
-| `flow_read_instruction` | Read the current step's instruction file content directly |
-| `flow_reset` | Clear flow state to start over |
-| `flow_add` | Add a custom flow from a directory |
-| `flow_update` | Update an existing custom flow |
-| `flow_remove` | Remove a custom flow |
-
-### Flow Selection
-
-| Task Type | Flow | Why |
-|-----------|------|-----|
-| Bug fix, config change, small refactor | `aikit:basic` | Known scope, low risk |
-| New feature in existing module | `aikit:basic` | Clear boundaries |
-| New system/service/module | `aikit:advanced` | Needs spec + planning |
-| Cross-service changes | `aikit:advanced` | Multiple boundaries |
-| Architectural change | `aikit:advanced` | High impact |
-| Unclear scope or exploratory | No flow | Use agent's native workflow |
-
-### Flow Lifecycle
-
-1. **Start**: `flow_list({})` → choose flow → `flow_start({ flow: "<name>", topic: "<task>" })`
-2. **Each step**: `flow_read_instruction({ step: "<name>" })` → follow step instructions → complete work
-3. **Advance**: `flow_step({ action: "next" })` → repeat from step 2
-4. **Epilogue**: After last flow step, mandatory epilogue steps run (e.g., `_docs-sync` updates `docs/`)
-5. **Resume**: `flow_status({})` → if active, `flow_read_instruction` for current step → continue
-6. **Reset**: `flow_reset({})` if you need to start over