@namch/agent-assistant 1.3.0 → 1.3.2

package/skills/docs-core/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: docs-core
-description: "Generate or update the 5 core project knowledge documents (overview, architecture, domain, source-base, standards) in ./documents/. Performs autonomous codebase scanning, gap analysis, and produces enterprise-grade documentation for rapid onboarding. Use when user says 'generate docs', 'update docs', 'create project documentation', 'docs-core', '/docs-core', 'onboarding docs', or wants to create/refresh the knowledge base."
+description: "Generate or update the 5 core project knowledge **folders** (overview, architecture, domain, source-base, standards) in ./documents/. Each knowledge area is a folder with 00-index.md + numbered sub-files. Performs autonomous codebase scanning, gap analysis, and produces enterprise-grade documentation for rapid onboarding. Use when user says 'generate docs', 'update docs', 'create project documentation', 'docs-core', '/docs-core', 'onboarding docs', or wants to create/refresh the knowledge base."
 metadata:
-  version: 1.0.0
+  version: 2.0.0
 ---
 
-# Docs-Core — Core Project Documentation Generator
+# Docs-Core — Core Project Documentation Generator (v2.0 Folder-Based)
 
-> **Mission**: Autonomously scan a codebase and produce (or update) **ALL 5** core knowledge documents at the highest quality standard. Every document must enable a new team member to fully understand the project's architecture and business domain in minimal time.
+> **Mission**: Autonomously scan a codebase and produce (or update) **ALL 5** core knowledge **folders** at the highest quality standard. Each folder contains `00-index.md` + numbered sub-files. Every document must enable a new team member to fully understand the project's architecture and business domain in minimal time.
 
 ---
 
@@ -15,8 +15,8 @@ metadata:
 
 Intelligent documentation engine. It handles two modes:
 
-- **CREATE** — Generate documents from scratch when `./documents/` is empty or files are missing.
-- **UPDATE** — Incrementally enrich existing documents by appending new content and correcting stale sections, **without discarding valuable existing context**.
+- **CREATE** — Generate folder structure from scratch when `./documents/` is empty or knowledge folders are missing.
+- **UPDATE** — Incrementally enrich existing folders/sub-files by appending new content and correcting stale sections, **without discarding valuable existing context**.
 
 All output files are written in **English only** regardless of the user's language.
 
@@ -34,17 +34,83 @@ All output files are written in **English only** regardless of the user's langua
 
 ---
 
-## Deliverables
+## Deliverables — Folder-Based Structure (v2.0)
 
-| # | File | Purpose |
-|---|------|---------|
-| 1 | `./documents/knowledge-overview.md` | Project identity, goals, tech stack, getting started |
-| 2 | `./documents/knowledge-architecture.md` | System design, components, data flow, design patterns |
-| 3 | `./documents/knowledge-domain.md` | Data models, schemas, API contracts, business rules |
-| 4 | `./documents/knowledge-source-base.md` | Directory tree, file purposes, entry points, modules |
-| 5 | `./documents/knowledge-standards.md` | Code style, naming, commit format, PR guidelines |
+Each knowledge area is a **folder** containing `00-index.md` (summary + TOC) and numbered sub-files:
 
-**Failure condition**: If fewer than 5 files are produced, the execution is **INCOMPLETE**.
+```
+./documents/
+  knowledge-overview/
+    00-index.md            # Project identity summary + TOC linking sub-files
+    01-project-identity.md
+    02-tech-stack.md
+    03-features.md
+    04-getting-started.md
+  knowledge-architecture/
+    00-index.md            # Architecture summary + TOC linking sub-files
+    01-system-overview.md
+    02-components.md
+    03-data-flow.md
+    04-design-patterns.md
+    05-decisions.md
+  knowledge-domain/
+    00-index.md            # Domain summary + TOC linking sub-files
+    01-entities.md
+    02-database-schema.md
+    03-api-contracts.md
+    04-business-rules.md
+  knowledge-source-base/
+    00-index.md            # Source map summary + TOC linking sub-files
+    01-directory-structure.md
+    02-entry-points.md
+    03-key-modules.md
+    04-configuration.md
+  knowledge-standards/
+    00-index.md            # Standards summary + TOC linking sub-files
+    01-code-style.md
+    02-conventions.md
+    03-git-workflow.md
+    04-testing-standards.md
+```
+
+**Minimum**: 5 folders x (1 index + 4 sub-files) = **25 files minimum**.
+**Failure condition**: If fewer than 5 folders are produced, or any folder is missing `00-index.md`, the execution is **INCOMPLETE**.
+
+### `00-index.md` Pattern
+
+Every `00-index.md` MUST follow this structure:
+
+```markdown
+# {Knowledge Area Title}
+
+> **Purpose**: {one-line purpose}
+> **Sub-files**: {count}
+> **Last Updated**: {YYYY-MM-DD}
+
+## Quick Summary
+{2-3 paragraph executive summary of this knowledge area}
+
+## Sub-Files
+
+| # | File | Description |
+|---|------|-------------|
+| 01 | [01-file-name.md](./01-file-name.md) | Brief description |
+| 02 | [02-file-name.md](./02-file-name.md) | Brief description |
+...
+
+## Cross-References
+- Related: [knowledge-architecture/00-index.md](../knowledge-architecture/00-index.md)
+...
+```
+
+### Scaling Rules
+
+| Condition | Action |
+|-----------|--------|
+| Sub-file exceeds ~300 lines | Split into two numbered sub-files |
+| Sub-file has < 20 lines of real content | Merge into adjacent sub-file |
+| New major topic discovered | Add new numbered sub-file at end (e.g., `05-new-topic.md`) |
+| `00-index.md` TOC out of sync | Update TOC to match actual sub-files |
 
 ---
 
@@ -57,27 +123,27 @@ BEFORE any work:
 1. Confirm ./documents/ directory exists (create if missing)
 2. Load templates directly from `skills/docs-core/references/` (read-only, in place)
 3. Do not create or persist template copies under `./documents/templates/`
-4. Check which of the 5 files already exist
-5. Determine execution mode per file:
-   - File missing → CREATE mode
-   - File exists  → UPDATE mode
-6. Log the execution plan
+4. Check which of the 5 knowledge FOLDERS already exist
+5. Check for legacy flat files (v1.0) and plan migration if found
+6. Determine execution mode per folder:
+   - Folder missing → CREATE mode
+   - Folder exists  → UPDATE mode (check sub-files individually)
+   - Flat file exists, no folder → MIGRATE mode
+7. Log the execution plan
 ```
 
 **Output**:
 ```markdown
-📋 Docs-Core Execution Plan
-| File | Status | Mode |
-|------|--------|------|
-| knowledge-overview.md | ✅ Exists / ❌ Missing | UPDATE / CREATE |
-| knowledge-architecture.md | ✅ Exists / ❌ Missing | UPDATE / CREATE |
-| knowledge-domain.md | ✅ Exists / ❌ Missing | UPDATE / CREATE |
-| knowledge-source-base.md | ✅ Exists / ❌ Missing | UPDATE / CREATE |
-| knowledge-standards.md | ✅ Exists / ❌ Missing | UPDATE / CREATE |
-
-📚 Template Source
-- Source: `skills/docs-core/references/*.md`
-- Mode: read-only, no copy
+## Docs-Core Execution Plan
+| Knowledge Area | Status | Mode |
+|----------------|--------|------|
+| knowledge-overview/ | Folder exists / Missing / Flat file only | UPDATE / CREATE / MIGRATE |
+| knowledge-architecture/ | Folder exists / Missing / Flat file only | UPDATE / CREATE / MIGRATE |
+| knowledge-domain/ | Folder exists / Missing / Flat file only | UPDATE / CREATE / MIGRATE |
+| knowledge-source-base/ | Folder exists / Missing / Flat file only | UPDATE / CREATE / MIGRATE |
+| knowledge-standards/ | Folder exists / Missing / Flat file only | UPDATE / CREATE / MIGRATE |
+
+Template Source: `skills/docs-core/references/*.md` (read-only, no copy)
 ```
 
 ---
@@ -96,7 +162,7 @@ If any of these 4 parts is skipped, documentation is considered incomplete.
 
 **1.1 — Structure Scan**:
 - List all top-level directories and files.
-- Recursively map the directory tree (depth 3–4 levels).
+- Recursively map the directory tree (depth 3-4 levels).
 - Identify entry points: `main.*`, `index.*`, `app.*`, `server.*`, `package.json`, `Makefile`, `Dockerfile`, etc.
 
 Minimum direct-read set (must read content, not only file names):
@@ -161,88 +227,100 @@ Required targeted search passes (minimum):
 
 ### Step 2: Gap Analysis (UPDATE mode only)
 
-When existing documents are found, perform a diff-aware analysis:
+When existing knowledge folders are found, perform a diff-aware analysis:
 
 ```
-FOR each existing document:
-  1. READ the current content completely.
+FOR each existing knowledge folder:
+  1. READ 00-index.md and all sub-files completely.
   2. COMPARE against reconnaissance findings.
-  3. IDENTIFY:
+  3. IDENTIFY per sub-file:
      a. Stale sections — info no longer matching codebase
      b. Missing sections — new components/features not documented
      c. Accurate sections — still correct, DO NOT TOUCH
   4. PLAN targeted edits:
-     - APPEND new sections for new discoveries
+     - APPEND new content to existing sub-files
+     - ADD new numbered sub-files for newly discovered topics
      - REVISE stale paragraphs with corrected info
      - PRESERVE all existing context that remains valid
+     - UPDATE 00-index.md TOC if sub-files changed
 ```
 
 **UPDATE Rules**:
-- **NEVER** delete existing sections that are still accurate.
-- **AVOID** rewriting from scratch in UPDATE mode.
-- **ALLOW** controlled rewrite only when file is structurally broken or over 70% stale.
+- **NEVER** delete existing sub-files or sections that are still accurate.
+- **AVOID** rewriting sub-files from scratch in UPDATE mode.
+- **ALLOW** controlled rewrite only when a sub-file is structurally broken or over 70% stale.
 - For controlled rewrite, preserve still-valid legacy context under `## Legacy Notes (Preserved Context)`.
 - **ALWAYS** add a changelog entry at the bottom: `> Last updated: {date} — {summary of changes}`.
 - **PREFER** appending new subsections over modifying existing ones.
 - Mark newly added sections with: `<!-- Added: {date} -->` HTML comment.
+- **ALWAYS** update `00-index.md` TOC when sub-files are added, removed, or renamed.
 
 ---
 
 ### Step 3: Content Generation (Thinking Protocol)
 
-For each of the 5 documents, apply this thinking protocol **before** writing:
+For each of the 5 knowledge folders, apply this thinking protocol **before** writing:
 
 ```
 THINK:
   1. WHO is the reader? → New developer, BA/PM, or AI agent.
-  2. WHAT must they understand from this file alone?
-  3. WHAT data from reconnaissance supports each section?
+  2. WHAT must they understand from this folder's files alone?
+  3. WHAT data from reconnaissance supports each sub-file?
   4. Is every claim backed by actual code evidence?
   5. Is any section speculative? → Remove or mark as assumption.
   6. Would a new team member find this sufficient for their first day?
   7. Is the language professional, direct, and jargon-appropriate?
+  8. Is content properly distributed across sub-files (no single file > ~300 lines)?
 
 VERIFY before writing:
   □ Every technical claim references actual files or patterns found
   □ No placeholder text ("TODO", "TBD", "fill in later")
-  □ Table of Contents matches actual headings
+  □ 00-index.md TOC matches actual sub-files
   □ Mermaid diagrams (if used) are syntactically valid
   □ All file paths referenced actually exist in the project
 ```
 
-**Generation order** (each file builds on the previous):
-1. `knowledge-source-base.md` — Foundation: where things are
-2. `knowledge-overview.md` — Identity: what and why
-3. `knowledge-architecture.md` — Design: how things connect
-4. `knowledge-domain.md` — Data: what data flows through
-5. `knowledge-standards.md` — Rules: how to contribute correctly
+**Generation order** (each folder builds on the previous):
+1. `knowledge-source-base/` — Foundation: where things are
+2. `knowledge-overview/` — Identity: what and why
+3. `knowledge-architecture/` — Design: how things connect
+4. `knowledge-domain/` — Data: what data flows through
+5. `knowledge-standards/` — Rules: how to contribute correctly
+
+**Per-folder execution order**:
+1. Create folder if missing
+2. Write `00-index.md` first (summary + planned TOC)
+3. Write numbered sub-files in order (`01-`, `02-`, ...)
+4. Verify `00-index.md` TOC links match actual sub-files
+5. Verify no sub-file exceeds ~300 lines
 
 **Onboarding-first requirements**:
-- Every generated file must include one subsection named `Onboarding Notes`.
-- `knowledge-overview.md` must include `First 60 Minutes` checklist.
-- `knowledge-source-base.md` must include `Read Order for New Members`.
+- Every `00-index.md` must include a `Quick Summary` section.
+- `knowledge-overview/01-project-identity.md` must include `First 60 Minutes` checklist.
+- `knowledge-source-base/00-index.md` must include `Read Order for New Members`.
 
 ---
 
 ### Step 4: Write Documents
 
-For each document, follow the corresponding template structure from `references/`.
+For each knowledge folder, follow the corresponding template structure from `references/`.
 
 **Writing rules**:
 - **Language**: English only. No exceptions.
 - **Tone**: Professional, direct, accessible to both business and technical readers.
 - **Format**: Standard Markdown with GFM extensions (tables, task lists, fenced code blocks).
-- **TOC**: Every file MUST begin with a Table of Contents after the title.
+- **TOC**: Every `00-index.md` MUST list all sub-files with links.
 - **Diagrams**: Use Mermaid.js for flowcharts, entity relationships, and architecture diagrams where they add clarity by visualizing relationships that text alone cannot convey.
 - **Tables**: Use tables for structured data (APIs, config vars, file listings).
 - **Code blocks**: Use fenced code blocks with language identifiers.
 - **Headings**: H1 for title, H2 for major sections, H3 for subsections, H4 for details.
-- **Metadata header**: Every file starts with:
+- **Metadata header**: Every sub-file starts with:
 
 ```markdown
 # {Project Name} — {Document Title}
 
 > **Purpose**: {one-line purpose statement}
+> **Parent**: [00-index.md](./00-index.md)
 > **Last Updated**: {YYYY-MM-DD}
 > **Generated By**: docs-core skill
 
@@ -255,21 +333,23 @@ For each document, follow the corresponding template structure from `references/
 ...
 ```
 
-- **Evidence section**: Every file must include `## Evidence Sources` listing concrete files used.
-- **Known gaps section**: Every file must include `## Known Gaps and Open Questions`.
+- **Evidence section**: Every sub-file must include `## Evidence Sources` listing concrete files used.
+- **Known gaps section**: At minimum, `00-index.md` must include `## Known Gaps and Open Questions`.
 
 ---
 
 ### Step 5: Verification Checklist
 
-After generating all 5 files, verify:
+After generating all 5 knowledge folders, verify:
 
 ```
 VERIFICATION MATRIX:
-| Check | knowledge-overview | knowledge-architecture | knowledge-domain | knowledge-source-base | knowledge-standards |
-|-------|-------------------|----------------------|-----------------|---------------------|-------------------|
-| File exists | □ | □ | □ | □ | □ |
-| TOC present | □ | □ | □ | □ | □ |
+| Check | knowledge-overview/ | knowledge-architecture/ | knowledge-domain/ | knowledge-source-base/ | knowledge-standards/ |
+|-------|--------------------|-----------------------|-------------------|----------------------|---------------------|
+| Folder exists | □ | □ | □ | □ | □ |
+| 00-index.md present | □ | □ | □ | □ | □ |
+| All sub-files present | □ | □ | □ | □ | □ |
+| TOC matches sub-files | □ | □ | □ | □ | □ |
 | No TODO/TBD | □ | □ | □ | □ | □ |
 | English only | □ | □ | □ | □ | □ |
 | Minimum sections | □ | □ | □ | □ | □ |
@@ -277,20 +357,21 @@ VERIFICATION MATRIX:
 | Diagrams render | □ | □ | □ | □ | □ |
 | Professional tone | □ | □ | □ | □ | □ |
 | Evidence Sources present | □ | □ | □ | □ | □ |
-| Known gaps section present | □ | □ | □ | □ | □ |
+| No sub-file > ~300 lines | □ | □ | □ | □ | □ |
 ```
 
-**Minimum section requirements per file**:
-- `knowledge-overview.md`: ≥ 6 sections (Identity, Purpose, Tech Stack, Features, Quick Start, Configuration)
-- `knowledge-architecture.md`: ≥ 5 sections (Overview, Components, Data Flow, Patterns, Dependencies)
-- `knowledge-domain.md`: ≥ 5 sections (Entities, Relationships, Schema, API Contracts, Business Rules)
-- `knowledge-source-base.md`: ≥ 4 sections (Root Structure, Directory Breakdown, Entry Points, Key Files)
-- `knowledge-standards.md`: ≥ 5 sections (Naming, Style, Commit Format, PR Guidelines, Testing)
+**Minimum sub-file requirements per folder**:
+- `knowledge-overview/`: >= 4 sub-files (Project Identity, Tech Stack, Features, Getting Started)
+- `knowledge-architecture/`: >= 5 sub-files (System Overview, Components, Data Flow, Design Patterns, Decisions)
+- `knowledge-domain/`: >= 4 sub-files (Entities, Database Schema, API Contracts, Business Rules)
+- `knowledge-source-base/`: >= 4 sub-files (Directory Structure, Entry Points, Key Modules, Configuration)
+- `knowledge-standards/`: >= 4 sub-files (Code Style, Conventions, Git Workflow, Testing Standards)
 
 **Coverage quality gates**:
 - Every major section must be backed by at least one explicit evidence file.
-- No document may contain unresolved placeholders.
+- No sub-file may contain unresolved placeholders.
 - If confidence is low for a section, mark confidence and list follow-up actions.
+- `00-index.md` TOC MUST match actual sub-files (no phantom links, no unlisted files).
 
 ---
 
@@ -299,25 +380,27 @@ VERIFICATION MATRIX:
 Present the final status to the user:
 
 ```markdown
-## ✅ Docs-Core Complete
-
-### 📦 Deliverables
-| # | File | Mode | Status |
-|---|------|------|--------|
-| 1 | ./documents/knowledge-overview.md | CREATE/UPDATE | ✅ |
-| 2 | ./documents/knowledge-architecture.md | CREATE/UPDATE | ✅ |
-| 3 | ./documents/knowledge-domain.md | CREATE/UPDATE | ✅ |
-| 4 | ./documents/knowledge-source-base.md | CREATE/UPDATE | ✅ |
-| 5 | ./documents/knowledge-standards.md | CREATE/UPDATE | ✅ |
-
-### 📊 Coverage Summary
+## Docs-Core Complete
+
+### Deliverables
+| # | Folder | Sub-Files | Mode | Status |
+|---|--------|-----------|------|--------|
+| 1 | ./documents/knowledge-overview/ | 00-index + 4 sub-files | CREATE/UPDATE | Done |
+| 2 | ./documents/knowledge-architecture/ | 00-index + 5 sub-files | CREATE/UPDATE | Done |
+| 3 | ./documents/knowledge-domain/ | 00-index + 4 sub-files | CREATE/UPDATE | Done |
+| 4 | ./documents/knowledge-source-base/ | 00-index + 4 sub-files | CREATE/UPDATE | Done |
+| 5 | ./documents/knowledge-standards/ | 00-index + 4 sub-files | CREATE/UPDATE | Done |
+
+**Total files**: {count} (minimum 25)
+
+### Coverage Summary
 - Tech stack documented: {list}
 - Architecture patterns identified: {list}
 - Domain entities mapped: {count}
 - Source directories documented: {count}
 - Standards defined: {count}
 
-### 📝 Next Steps
+### Next Steps
 - `/docs:business` — Generate business documentation
 - Review and customize generated docs for project-specific nuances
 ```
@@ -326,18 +409,18 @@ Present the final status to the user:
 
 ## Document Templates
 
-Detailed templates for each document are stored in `references/`. Load the relevant template when generating each file:
+Detailed templates for each document are stored in `references/`. Load the relevant template when generating each folder's sub-files:
 
 | Template File | Produces |
 |---------------|----------|
-| `references/template-overview.md` | knowledge-overview.md |
-| `references/template-architecture.md` | knowledge-architecture.md |
-| `references/template-domain.md` | knowledge-domain.md |
-| `references/template-source-base.md` | knowledge-source-base.md |
-| `references/template-standards.md` | knowledge-standards.md |
+| `references/template-overview.md` | knowledge-overview/ folder |
+| `references/template-architecture.md` | knowledge-architecture/ folder |
+| `references/template-domain.md` | knowledge-domain/ folder |
+| `references/template-source-base.md` | knowledge-source-base/ folder |
+| `references/template-standards.md` | knowledge-standards/ folder |
 | `references/deep-recon-checklist.md` | Mandatory deep reconnaissance checklist |
 
-**Usage**: Read the template → Fill sections with reconnaissance data → Write to `./documents/`.
+**Usage**: Read the template → Create folder → Write `00-index.md` + numbered sub-files → Write to `./documents/{knowledge-area}/`.
 
 ---
 
@@ -362,7 +445,7 @@ bash skills/docs-core/scripts/scan-project.sh [project-root]
 
 | Criterion | Requirement |
 |-----------|-------------|
-| **Completeness** | All 5 files produced with all required sections |
+| **Completeness** | All 5 folders produced with 00-index.md + all required sub-files |
 | **Accuracy** | Every technical claim backed by actual code evidence |
 | **Freshness** | Content reflects current codebase state, not historical |
 | **Readability** | Understandable by both BA/PM and junior developers |
@@ -371,6 +454,7 @@ bash skills/docs-core/scripts/scan-project.sh [project-root]
 | **No Placeholders** | Zero TODO, TBD, or "fill in later" markers |
 | **Professional Tone** | Direct, clear, no filler, no marketing-speak |
 | **Update Safety** | UPDATE mode preserves existing valuable context |
+| **Scalability** | No sub-file exceeds ~300 lines; split when needed |
 
 ### Quality Bar
 
@@ -387,12 +471,12 @@ bash skills/docs-core/scripts/scan-project.sh [project-root]
 User: Generate documentation for this project
 
 Docs-Core Process:
-1. Pre-Flight: ./documents/ exists but all 5 files missing → CREATE mode
+1. Pre-Flight: ./documents/ exists but knowledge folders missing → CREATE mode
 2. Reconnaissance: Scan finds Next.js + Prisma + PostgreSQL monorepo
-3. Generation order: source-base → overview → architecture → domain → standards
-4. Write all 5 files with full templates
-5. Verify: All checks pass
-6. Report: 5/5 files created
+3. Generation order: source-base/ → overview/ → architecture/ → domain/ → standards/
+4. Per folder: create folder → write 00-index.md → write numbered sub-files
+5. Verify: All checks pass, 25+ files created
+6. Report: 5/5 folders created (25+ total files)
 ```
 
 ### Example 2: Existing Project (UPDATE mode)
@@ -401,24 +485,12 @@ Docs-Core Process:
 User: Update the docs, we added a new module
 
 Docs-Core Process:
-1. Pre-Flight: All 5 files exist → UPDATE mode
+1. Pre-Flight: All 5 folders exist → UPDATE mode
 2. Reconnaissance: Scan finds new `payments/` module with Stripe integration
-3. Gap Analysis: knowledge-architecture.md missing payments component,
-   knowledge-domain.md missing PaymentIntent entity
-4. Targeted edits: Append payments section to architecture, add entity to domain
-5. Verify: All checks pass, existing content preserved
-6. Report: 2/5 files updated, 3/5 unchanged
-```
-
-### Example 3: Partial Documentation (MIXED mode)
-
-```
-User: Create docs for this repo
-
-Docs-Core Process:
-1. Pre-Flight: 2 files exist (overview, standards), 3 missing → MIXED mode
-2. Scan codebase, read existing 2 files
-3. CREATE 3 missing files, UPDATE 2 existing files if stale
-4. Verify all 5 files complete
-5. Report: 3 created, 2 updated
+3. Gap Analysis: knowledge-architecture/02-components.md missing payments component,
+   knowledge-domain/01-entities.md missing PaymentIntent entity
+4. Targeted edits: Append payments section to architecture sub-file, add entity to domain sub-file
+5. Update affected 00-index.md files if new sub-files were added
+6. Verify: All checks pass, existing content preserved
+7. Report: 2 sub-files updated, rest unchanged
 ```

package/skills/planning/references/codebase-understanding.md

@@ -21,11 +21,11 @@ ALWAYS read these files first when they exist under `./documents/`:
    - Development rules and best practices
    - Code quality standards & Security guidelines
 
-2. **`./documents/knowledge-overview.md`** — Project purpose, goals, tech stack, getting started
-3. **`./documents/knowledge-architecture.md`** — System design, components, data flow, patterns
-4. **`./documents/knowledge-source-base.md`** — Project structure, modules, entry points
-5. **`./documents/knowledge-domain.md`** — Data models, API contracts, domain entities
-6. **`./documents/knowledge-standards.md`** — Coding conventions, naming, commit format
+2. **`./documents/knowledge-overview/00-index.md`** — Project purpose, goals, tech stack, getting started (drill into sub-files as needed)
+3. **`./documents/knowledge-architecture/00-index.md`** — System design, components, data flow, patterns (drill into sub-files as needed)
+4. **`./documents/knowledge-source-base/00-index.md`** — Project structure, modules, entry points (drill into sub-files as needed)
+5. **`./documents/knowledge-domain/00-index.md`** — Data models, API contracts, domain entities (drill into sub-files as needed)
+6. **`./documents/knowledge-standards/00-index.md`** — Coding conventions, naming, commit format (drill into sub-files as needed)
 7. **`./docs/design-guidelines.md`** (if exists) — Design system, branding, UI/UX
    - Design system guidelines
    - Branding and UI/UX conventions

package/code-assistants/codex-assistant/skills/agent-assistant-code-focus/SKILL.md

@@ -1,18 +0,0 @@
----
-name: agent-assistant-code-focus
-description: "🔒 Focused Development — Full cycle with enforced context optimization. Use when user types /code:focus."
----
-
-# /code:focus
-
-> Activates Agent Assistant `/code:focus` workflow.
-
-## Rules
-
-1. **Load first**: `~/.codex/skills/agent-assistant/rules/CORE.md` — follow all 10 Laws
-2. **Agents**: Spawn via Codex native multi-agent (`~/.codex/agents/`)
-3. **Skills**: Resolve from `~/.codex/skills/agent-assistant/matrix-skills/`
-
-## Workflow
-
-**Load and follow**: `~/.codex/skills/agent-assistant/commands/code/focus.md`

package/code-assistants/codex-assistant/skills/agent-assistant-code-focus/agents/openai.yaml

@@ -1,4 +0,0 @@
-display_name: "/code:focus"
-short_description: "🔒 Focused Development — Full cycle with enforced context optimization"
-brand_color: "#6366F1"
-allow_implicit_invocation: true

package/code-assistants/codex-assistant/skills/agent-assistant-cook-focus/SKILL.md

@@ -1,18 +0,0 @@
----
-name: agent-assistant-cook-focus
-description: "🔒 Focused Feature — Complete development with enforced context optimization. Use when user types /cook:focus."
----
-
-# /cook:focus
-
-> Activates Agent Assistant `/cook:focus` workflow.
-
-## Rules
-
-1. **Load first**: `~/.codex/skills/agent-assistant/rules/CORE.md` — follow all 10 Laws
-2. **Agents**: Spawn via Codex native multi-agent (`~/.codex/agents/`)
-3. **Skills**: Resolve from `~/.codex/skills/agent-assistant/matrix-skills/`
-
-## Workflow
-
-**Load and follow**: `~/.codex/skills/agent-assistant/commands/cook/focus.md`

package/code-assistants/codex-assistant/skills/agent-assistant-cook-focus/agents/openai.yaml

@@ -1,4 +0,0 @@
-display_name: "/cook:focus"
-short_description: "🔒 Focused Feature — Complete development with enforced context optimization"
-brand_color: "#6366F1"
-allow_implicit_invocation: true

package/code-assistants/codex-assistant/skills/agent-assistant-debug-focus/SKILL.md

@@ -1,18 +0,0 @@
----
-name: agent-assistant-debug-focus
-description: "🔒 Focused Debug — Deep investigation with enforced context optimization. Use when user types /debug:focus."
----
-
-# /debug:focus
-
-> Activates Agent Assistant `/debug:focus` workflow.
-
-## Rules
-
-1. **Load first**: `~/.codex/skills/agent-assistant/rules/CORE.md` — follow all 10 Laws
-2. **Agents**: Spawn via Codex native multi-agent (`~/.codex/agents/`)
-3. **Skills**: Resolve from `~/.codex/skills/agent-assistant/matrix-skills/`
-
-## Workflow
-
-**Load and follow**: `~/.codex/skills/agent-assistant/commands/debug/focus.md`

package/code-assistants/codex-assistant/skills/agent-assistant-debug-focus/agents/openai.yaml

@@ -1,4 +0,0 @@
-display_name: "/debug:focus"
-short_description: "🔒 Focused Debug — Deep investigation with enforced context optimization"
-brand_color: "#EF4444"
-allow_implicit_invocation: true

package/code-assistants/codex-assistant/skills/agent-assistant-design-focus/SKILL.md

@@ -1,18 +0,0 @@
----
-name: agent-assistant-design-focus
-description: "🔒 Focused Design — Complete design with enforced context optimization. Use when user types /design:focus."
----
-
-# /design:focus
-
-> Activates Agent Assistant `/design:focus` workflow.
-
-## Rules
-
-1. **Load first**: `~/.codex/skills/agent-assistant/rules/CORE.md` — follow all 10 Laws
-2. **Agents**: Spawn via Codex native multi-agent (`~/.codex/agents/`)
-3. **Skills**: Resolve from `~/.codex/skills/agent-assistant/matrix-skills/`
-
-## Workflow
-
-**Load and follow**: `~/.codex/skills/agent-assistant/commands/design/focus.md`

package/code-assistants/codex-assistant/skills/agent-assistant-design-focus/agents/openai.yaml

@@ -1,4 +0,0 @@
-display_name: "/design:focus"
-short_description: "🔒 Focused Design — Complete design with enforced context optimization"
-brand_color: "#EC4899"
-allow_implicit_invocation: true

package/code-assistants/codex-assistant/skills/agent-assistant-fix-focus/SKILL.md

@@ -1,18 +0,0 @@
----
-name: agent-assistant-fix-focus
-description: "🔒 Focused Fix — Complete resolution with enforced context optimization. Use when user types /fix:focus."
----
-
-# /fix:focus
-
-> Activates Agent Assistant `/fix:focus` workflow.
-
-## Rules
-
-1. **Load first**: `~/.codex/skills/agent-assistant/rules/CORE.md` — follow all 10 Laws
-2. **Agents**: Spawn via Codex native multi-agent (`~/.codex/agents/`)
-3. **Skills**: Resolve from `~/.codex/skills/agent-assistant/matrix-skills/`
-
-## Workflow
-
-**Load and follow**: `~/.codex/skills/agent-assistant/commands/fix/focus.md`

package/code-assistants/codex-assistant/skills/agent-assistant-fix-focus/agents/openai.yaml

@@ -1,4 +0,0 @@
-display_name: "/fix:focus"
-short_description: "🔒 Focused Fix — Complete resolution with enforced context optimization"
-brand_color: "#EF4444"
-allow_implicit_invocation: true