[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M9HA83FR5ACRKXDC9H6YDA":3,"skill-same:01M6M9HA83FR5ACRKXDC9H6YDA":68},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6M9HA83FR5ACRKXDC9H6YDA","context-architecture",null,"Progressive disclosure architecture for organizing project context as a DAG (directed acyclic graph).\nAgents enter at the root and traverse only the subgraph relevant to their task.\nCovers the 4-tier information flow (refs → kits → plans → impl), CLAUDE.md hierarchy\nacross context\u002F and source tree, index files as DAG hub nodes, nesting rules, and backward compatibility.\nTrigger phrases: \"context architecture\", \"progressive disclosure\", \"organize context for agents\",\n\"context directory structure\", \"how to structure docs for AI\", \"context hierarchy\"","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJuliusBrussee\u002Fblueprint\u002Fskills\u002Fcontext-architecture\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"architecture","context architecture","context","structure","hierarchy","source","at","information","relevant","how to","impl","project","across","directory","organize","files","only","how","flow","dag","2026-11-10 10:12:30",false,"---\nname: context-architecture\ndescription: |\n  Progressive disclosure architecture for organizing project context as a DAG (directed acyclic graph).\n  Agents enter at the root and traverse only the subgraph relevant to their task.\n  Covers the 4-tier information flow (refs → kits → plans → impl), CLAUDE.md hierarchy\n  across context\u002F and source tree, index files as DAG hub nodes, nesting rules, and backward compatibility.\n  Trigger phrases: \"context architecture\", \"progressive disclosure\", \"organize context for agents\",\n  \"context directory structure\", \"how to structure docs for AI\", \"context hierarchy\"\n---\n\n# Context Architecture: DAG-Based Progressive Disclosure\n\n## Core Principle\n\n**Agents should only read what they need.** Documents are organized as a directed acyclic graph (DAG) where index files act as hub nodes. An agent reads the index, identifies relevant edges, and follows only those to leaf documents. No agent ever loads the full tree.\n\n---\n\n## The 4-Tier Information Flow\n\n```\nrefs\u002F (what IS)  -->  kits\u002F (what MUST BE)  -->  plans\u002F (HOW)  -->  impl\u002F (what WAS DONE)\n     Tier 1                  Tier 2                     Tier 3              Tier 4\n```\n\nEach tier consumes the previous tier's output. Cross-references between tiers create the DAG edges that agents traverse.\n\n---\n\n## Directory Layout\n\n```\ncontext\u002F\n├── CLAUDE.md                              # Root entry node: describes all tiers + design layer\n├── refs\u002F                                  # Tier 1: Source material (read-only input)\n│   ├── CLAUDE.md                          # \"Source of truth. Organized by source. Read-only.\"\n│   └── {source}\u002F                          # Subdirs per source (e.g., prd\u002F, api-spec\u002F)\n│       └── ...\n├── kits\u002F                            # Tier 2: WHAT to build\n│   ├── CLAUDE.md                          # \"Start at cavekit-overview.md. R-numbered reqs.\"\n│   ├── cavekit-overview.md              # Index node (DAG hub)\n│   ├── cavekit-{domain}.md              # Leaf — simple domain (single file)\n│   └── {domain}\u002F                          # Complex domain gets a subdirectory\n│       ├── cavekit-{domain}.md          # Domain index (becomes hub node)\n│       └── cavekit-{domain}-{sub}.md    # Sub-domain leaves\n├── designs\u002F                               # Cross-cutting: visual design system\n│   ├── CLAUDE.md                          # \"DESIGN.md at project root is canonical.\"\n│   └── design-changelog.md               # Append-only change log\n├── plans\u002F                                 # Tier 3: HOW to build (task graphs)\n│   ├── CLAUDE.md                          # \"Start at plan-overview.md. Task dependency tiers.\"\n│   ├── plan-overview.md                   # Index node\n│   ├── build-site.md                      # Primary build site\n│   ├── build-site-{feature}.md            # Feature-specific build sites\n│   └── {domain}\u002F                          # Complex plans get subdirectories\n│       └── plan-{domain}-{area}.md\n├── impl\u002F                                  # Tier 4: What WAS DONE\n│   ├── CLAUDE.md                          # \"Start at impl-overview.md. Update after every session.\"\n│   ├── impl-overview.md                   # Index node\n│   ├── impl-{domain}.md                   # Per-domain tracking\n│   ├── impl-review-findings.md            # Codex review findings ledger\n│   ├── dead-ends.md                       # Failed approaches (shared across domains)\n│   └── archive\u002F                           # Compacted\u002Farchived tracking\n```\n\n> **Note:** `designs\u002F` is a **cross-cutting constraint layer**, not a fifth tier. DESIGN.md (at project root) is read by agents at every Hunt phase — Draft reads it to constrain visual decisions, Architect references tokens in task descriptions, Build uses it for implementation, Inspect validates against it. It parallels how CLAUDE.md files provide conventions, but for visual design.\n\n### Backward Compatibility: sites\u002F → plans\u002F\n\nBuild sites previously lived in `context\u002Fsites\u002F`. All Cavekit commands check both locations:\n\n1. Look in `context\u002Fplans\u002F`\n2. If not found, fall back to `context\u002Fsites\u002F`\n3. If found in `sites\u002F`, use it — no auto-migration, no breakage\n\n`\u002Fck:init` offers optional migration. Declining is permanent — the system works with either layout.\n\n---\n\n## CLAUDE.md Hierarchy\n\n### Scope: Full Repository\n\n`CLAUDE.md` files extend beyond `context\u002F` into the source code tree. They form the connective tissue between code and the context DAG.\n\n```\nproject\u002F\n├── CLAUDE.md                          # Project root: build\u002Ftest commands,\n│                                      #   \"context\u002F has the full hierarchy\"\n├── context\u002F\n│   ├── CLAUDE.md                      # Root context node: 4 tiers described\n│   ├── refs\u002FCLAUDE.md                 # Tier 1 conventions\n│   ├── kits\u002FCLAUDE.md           # Tier 2 conventions\n│   ├── plans\u002FCLAUDE.md                # Tier 3 conventions\n│   └── impl\u002FCLAUDE.md                 # Tier 4 conventions\n│\n├── src\u002F\n│   ├── CLAUDE.md                      # Source code conventions\n│   ├── auth\u002F\n│   │   ├── CLAUDE.md                  # \"implements cavekit-auth.md R1-R3\"\n│   │   └── ...\n│   └── parser\u002F\n│       ├── CLAUDE.md                  # \"implements cavekit-grammar.md R1-R4,\n│       │                              #   see plans\u002Fbuild-site.md T-012 through T-018\"\n│       └── ...\n│\n├── tests\u002F\n│   ├── CLAUDE.md                      # Test conventions, how to run\n│   └── ...\n└── scripts\u002F\n    ├── CLAUDE.md                      # Utility script conventions\n    └── ...\n```\n\n### Loading Behavior\n\nWhen an agent works in `src\u002Fauth\u002F`, it loads hierarchically:\n1. `project\u002FCLAUDE.md` — project-level conventions\n2. `project\u002Fsrc\u002FCLAUDE.md` — source code conventions\n3. `project\u002Fsrc\u002Fauth\u002FCLAUDE.md` — **\"implements cavekit-auth.md R1-R3\"**\n\nThe third file bridges to the context DAG. The agent knows which cavekit to load without loading the entire `context\u002Fkits\u002F` directory.\n\n### CLAUDE.md Design Principles\n\n- **Minimal** — 3-10 lines for source-tree files. Never duplicate cavekit content.\n- **Connective** — each one names the cavekit requirements and plan tasks it relates to.\n- **Contextual** — includes module-specific conventions (error handling patterns, test fixture locations).\n- **Honest** — `\u002Fck:make` only writes mappings it is certain about (tasks it completed, files it created).\n\n---\n\n## Progressive Disclosure: The DAG Traversal\n\n### How Agents Navigate\n\n1. **Enter at root** — read `context\u002FCLAUDE.md` to understand the 4 tiers\n2. **Select tier** — based on current task, navigate to the relevant tier's `CLAUDE.md`\n3. **Read index** — the tier's overview file is the DAG hub, listing all domains with one-line summaries\n4. **Follow edges** — read only the domain files relevant to the current task\n5. **Cross-reference** — if a domain references another, follow that edge only if needed\n6. **Nest deeper** — if a domain has subdirectories, its root file is the sub-index; spider from there\n\n### Index File Format\n\nEvery overview file follows the same format:\n\n```markdown\n# Cavekit Overview\n\n| Domain | File | Summary | Status |\n|--------|------|---------|--------|\n| Authentication | cavekit-auth.md | Registration, login, sessions, OAuth | DRAFT |\n| Data Models | cavekit-data-models.md | Core entities, relationships, validation | DRAFT |\n| Type System | cavekit-type-system.md | Effects lattice, tagged values (see type-system\u002F) | DRAFT |\n```\n\nAn agent reads this table, identifies \"I need Authentication,\" and loads only `cavekit-auth.md`.\n\n### Cross-Reference Edges\n\n```markdown\n**Dependencies:** cavekit-auth.md R2 (session tokens required for API auth)\n**See also:** cavekit-api.md R4 (rate limiting uses auth identity)\n```\n\nAgents follow these only when the cross-referenced content is needed for the current task.\n\n---\n\n## Nesting Rule\n\nA domain stays flat (single file) by default. When a file covers multiple independent concerns that could be understood separately, it becomes an index file pointing to a subdirectory.\n\n**Trigger:** Cohesion, not line count. If a file has sections that an agent working on one section would never need to read the others, decompose it.\n\n**Example:** `cavekit-type-system.md` covers effects lattice, tagged values, and inference rules:\n\n```\nkits\u002F\n├── cavekit-type-system.md                        # Now an index\n└── type-system\u002F\n    ├── cavekit-type-system-effects.md\n    ├── cavekit-type-system-tagged.md\n    └── cavekit-type-system-inference.md\n```\n\nThe original file stays in place as the index — no reference breakage.\n\n---\n\n## Backpropagation via CLAUDE.md\n\nWhen a bug is found, source-tree CLAUDE.md files provide the reverse traversal:\n\n```\nBug in src\u002Fauth\u002Flogin.ts\n    |\n    v\nsrc\u002Fauth\u002FCLAUDE.md says \"implements cavekit-auth.md R2\"\n    |\n    v\ncavekit-auth.md R2 — check acceptance criteria\n    |\n    |-- Criteria missing?  --> update cavekit (spec gap)\n    |-- Criteria wrong?    --> fix cavekit (spec bug)\n    |-- Criteria present but code violates? --> fix code (impl bug)\n    |\n    v\nIf cavekit changed --> propagate to plans\u002F --> flag affected tasks\n```\n\n### Forward Propagation\n\nWhen a cavekit changes via `\u002Fck:revise`:\n1. Scan all `src\u002F*\u002FCLAUDE.md` files for references to the changed requirement\n2. Flag those modules as potentially affected\n3. New requirements with no source-tree CLAUDE.md references are unimplemented\n\n---\n\n## Bootstrapping\n\nRun `\u002Fck:init` to create the full hierarchy. It:\n1. Scans existing project structure\n2. Creates context directories (refs\u002F, kits\u002F, plans\u002F, impl\u002F)\n3. Creates CLAUDE.md files using standard templates\n4. Creates empty index files (cavekit-overview.md, plan-overview.md, impl-overview.md)\n5. Offers migration if legacy `context\u002Fsites\u002F` exists\n\nProperties: idempotent, non-destructive, no questions asked.\n\n---\n\n## Build-Time Updates\n\nAfter `\u002Fck:make` completes, source-tree CLAUDE.md files are generated\u002Fupdated:\n- New source directories get a CLAUDE.md with cavekit\u002Fplan references\n- Existing CLAUDE.md files get new references appended (never removed)\n- `impl-overview.md` and `plan-overview.md` are updated with current status\n\n---\n\n## Multi-Repo Strategy\n\nFor shared kits across implementations, use git submodules:\n\n```\nTier 1-2 (shared): shared-context\u002F (submodule)\n    └── refs\u002F + kits\u002F\n\nTier 3-4 (per-repo): context\u002F\n    └── plans\u002F + impl\u002F\n```\n\nEach framework repo includes the shared context as a submodule. Updates propagate via `git submodule update`.\n\n---\n\n## Integration with Other Skills\n\n| Skill | Integration |\n|-------|------------|\n| `ck:cavekit-writing` | Kits go in `context\u002Fkits\u002F` following naming conventions |\n| `ck:design-system` | DESIGN.md lives at project root; `context\u002Fdesigns\u002F` has CLAUDE.md and changelog |\n| `ck:impl-tracking` | Tracking lives in `context\u002Fimpl\u002F`, compacted when exceeding ~500 lines |\n| `ck:validation-first` | Validation results recorded in impl tracking within the hierarchy |\n| `ck:revision` | `\u002Fck:revise` traverses CLAUDE.md edges in reverse to trace bugs to specs |\n| `ck:methodology` | Context structure established during Draft phase, maintained throughout the Hunt |\n\n---\n\n## Anti-Patterns\n\n| Anti-Pattern | Why It's Wrong | Fix |\n|-------------|---------------|-----|\n| Flat file dump | No progressive disclosure, agents load everything | Use standard directory structure with indexes |\n| Missing CLAUDE.md files | No convention guidance, no DAG edges | Run `\u002Fck:init` or add manually |\n| Monolithic documents | Defeats progressive disclosure | Decompose into domains with overview indexes |\n| Stale archives in active dirs | Wastes context window | Move to `impl\u002Farchive\u002F` |\n| Duplicating cavekit content in CLAUDE.md | Content drifts, double maintenance | CLAUDE.md files only contain references |\n","# Context Architecture: DAG-Based Progressive Disclosure\n\n## Core Principle\n\n**Agents should only read what they need.** Documents are organized as a directed acyclic graph (DAG) where index files act as hub nodes. An agent reads the index, identifies relevant edges, and follows only those to leaf documents. No agent ever loads the full tree.\n\n---\n\n## The 4-Tier Information Flow\n\n```\nrefs\u002F (what IS)  -->  kits\u002F (what MUST BE)  -->  plans\u002F (HOW)  -->  impl\u002F (what WAS DONE)\n     Tier 1                  Tier 2                     Tier 3              Tier 4\n```\n\nEach tier consumes the previous tier's output. Cross-references between tiers create the DAG edges that agents traverse.\n\n---\n\n## Directory Layout\n\n```\ncontext\u002F\n├── CLAUDE.md                              # Root entry node: describes all tiers + design layer\n├── refs\u002F                                  # Tier 1: Source material (read-only input)\n│   ├── CLAUDE.md                          # \"Source of truth. Organized by source. Read-only.\"\n│   └── {source}\u002F                          # Subdirs per source (e.g., prd\u002F, api-spec\u002F)\n│       └── ...\n├── kits\u002F                            # Tier 2: WHAT to build\n│   ├── CLAUDE.md                          # \"Start at cavekit-overview.md. R-numbered reqs.\"\n│   ├── cavekit-overview.md              # Index node (DAG hub)\n│   ├── cavekit-{domain}.md              # Leaf — simple domain (single file)\n│   └── {domain}\u002F                          # Complex domain gets a subdirectory\n│       ├── cavekit-{domain}.md          # Domain index (becomes hub node)\n│       └── cavekit-{domain}-{sub}.md    # Sub-domain leaves\n├── designs\u002F                               # Cross-cutting: visual design system\n│   ├── CLAUDE.md                          # \"DESIGN.md at project root is canonical.\"\n│   └── design-changelog.md               # Append-only change log\n├── plans\u002F                                 # Tier 3: HOW to build (task graphs)\n│   ├── CLAUDE.md                          # \"Start at plan-overview.md. Task dependency tiers.\"\n│   ├── plan-overview.md                   # Index node\n│   ├── build-site.md                      # Primary build site\n│   ├── build-site-{feature}.md            # Feature-specific build sites\n│   └── {domain}\u002F                          # Complex plans get subdirectories\n│       └── plan-{domain}-{area}.md\n├── impl\u002F                                  # Tier 4: What WAS DONE\n│   ├── CLAUDE.md                          # \"Start at impl-overview.md. Update after every session.\"\n│   ├── impl-overview.md                   # Index node\n│   ├── impl-{domain}.md                   # Per-domain tracking\n│   ├── impl-review-findings.md            # Codex review findings ledger\n│   ├── dead-ends.md                       # Failed approaches (shared across domains)\n│   └── archive\u002F                           # Compacted\u002Farchived tracking\n```\n\n> **Note:** `designs\u002F` is a **cross-cutting constraint layer**, not a fifth tier. DESIGN.md (at project root) is read by agents at every Hunt phase — Draft reads it to constrain visual decisions, Architect references tokens in task descriptions, Build uses it for implementation, Inspect validates against it. It parallels how CLAUDE.md files provide conventions, but for visual design.\n\n### Backward Compatibility: sites\u002F → plans\u002F\n\nBuild sites previously lived in `context\u002Fsites\u002F`. All Cavekit commands check both locations:\n\n1. Look in `context\u002Fplans\u002F`\n2. If not found, fall back to `context\u002Fsites\u002F`\n3. If found in `sites\u002F`, use it — no auto-migration, no breakage\n\n`\u002Fck:init` offers optional migration. Declining is permanent — the system works with either layout.\n\n---\n\n## CLAUDE.md Hierarchy\n\n### Scope: Full Repository\n\n`CLAUDE.md` files extend beyond `context\u002F` into the source code tree. They form the connective tissue between code and the context DAG.\n\n```\nproject\u002F\n├── CLAUDE.md                          # Project root: build\u002Ftest commands,\n│                                      #   \"context\u002F has the full hierarchy\"\n├── context\u002F\n│   ├── CLAUDE.md                      # Root context node: 4 tiers described\n│   ├── refs\u002FCLAUDE.md                 # Tier 1 conventions\n│   ├── kits\u002FCLAUDE.md           # Tier 2 conventions\n│   ├── plans\u002FCLAUDE.md                # Tier 3 conventions\n│   └── impl\u002FCLAUDE.md                 # Tier 4 conventions\n│\n├── src\u002F\n│   ├── CLAUDE.md                      # Source code conventions\n│   ├── auth\u002F\n│   │   ├── CLAUDE.md                  # \"implements cavekit-auth.md R1-R3\"\n│   │   └── ...\n│   └── parser\u002F\n│       ├── CLAUDE.md                  # \"implements cavekit-grammar.md R1-R4,\n│       │                              #   see plans\u002Fbuild-site.md T-012 through T-018\"\n│       └── ...\n│\n├── tests\u002F\n│   ├── CLAUDE.md                      # Test conventions, how to run\n│   └── ...\n└── scripts\u002F\n    ├── CLAUDE.md                      # Utility script conventions\n    └── ...\n```\n\n### Loading Behavior\n\nWhen an agent works in `src\u002Fauth\u002F`, it loads hierarchically:\n1. `project\u002FCLAUDE.md` — project-level conventions\n2. `project\u002Fsrc\u002FCLAUDE.md` — source code conventions\n3. `project\u002Fsrc\u002Fauth\u002FCLAUDE.md` — **\"implements cavekit-auth.md R1-R3\"**\n\nThe third file bridges to the context DAG. The agent knows which cavekit to load without loading the entire `context\u002Fkits\u002F` directory.\n\n### CLAUDE.md Design Principles\n\n- **Minimal** — 3-10 lines for source-tree files. Never duplicate cavekit content.\n- **Connective** — each one names the cavekit requirements and plan tasks it relates to.\n- **Contextual** — includes module-specific conventions (error handling patterns, test fixture locations).\n- **Honest** — `\u002Fck:make` only writes mappings it is certain about (tasks it completed, files it created).\n\n---\n\n## Progressive Disclosure: The DAG Traversal\n\n### How Agents Navigate\n\n1. **Enter at root** — read `context\u002FCLAUDE.md` to understand the 4 tiers\n2. **Select tier** — based on current task, navigate to the relevant tier's `CLAUDE.md`\n3. **Read index** — the tier's overview file is the DAG hub, listing all domains with one-line summaries\n4. **Follow edges** — read only the domain files relevant to the current task\n5. **Cross-reference** — if a domain references another, follow that edge only if needed\n6. **Nest deeper** — if a domain has subdirectories, its root file is the sub-index; spider from there\n\n### Index File Format\n\nEvery overview file follows the same format:\n\n```markdown\n# Cavekit Overview\n\n| Domain | File | Summary | Status |\n|--------|------|---------|--------|\n| Authentication | cavekit-auth.md | Registration, login, sessions, OAuth | DRAFT |\n| Data Models | cavekit-data-models.md | Core entities, relationships, validation | DRAFT |\n| Type System | cavekit-type-system.md | Effects lattice, tagged values (see type-system\u002F) | DRAFT |\n```\n\nAn agent reads this table, identifies \"I need Authentication,\" and loads only `cavekit-auth.md`.\n\n### Cross-Reference Edges\n\n```markdown\n**Dependencies:** cavekit-auth.md R2 (session tokens required for API auth)\n**See also:** cavekit-api.md R4 (rate limiting uses auth identity)\n```\n\nAgents follow these only when the cross-referenced content is needed for the current task.\n\n---\n\n## Nesting Rule\n\nA domain stays flat (single file) by default. When a file covers multiple independent concerns that could be understood separately, it becomes an index file pointing to a subdirectory.\n\n**Trigger:** Cohesion, not line count. If a file has sections that an agent working on one section would never need to read the others, decompose it.\n\n**Example:** `cavekit-type-system.md` covers effects lattice, tagged values, and inference rules:\n\n```\nkits\u002F\n├── cavekit-type-system.md                        # Now an index\n└── type-system\u002F\n    ├── cavekit-type-system-effects.md\n    ├── cavekit-type-system-tagged.md\n    └── cavekit-type-system-inference.md\n```\n\nThe original file stays in place as the index — no reference breakage.\n\n---\n\n## Backpropagation via CLAUDE.md\n\nWhen a bug is found, source-tree CLAUDE.md files provide the reverse traversal:\n\n```\nBug in src\u002Fauth\u002Flogin.ts\n    |\n    v\nsrc\u002Fauth\u002FCLAUDE.md says \"implements cavekit-auth.md R2\"\n    |\n    v\ncavekit-auth.md R2 — check acceptance criteria\n    |\n    |-- Criteria missing?  --> update cavekit (spec gap)\n    |-- Criteria wrong?    --> fix cavekit (spec bug)\n    |-- Criteria present but code violates? --> fix code (impl bug)\n    |\n    v\nIf cavekit changed --> propagate to plans\u002F --> flag affected tasks\n```\n\n### Forward Propagation\n\nWhen a cavekit changes via `\u002Fck:revise`:\n1. Scan all `src\u002F*\u002FCLAUDE.md` files for references to the changed requirement\n2. Flag those modules as potentially affected\n3. New requirements with no source-tree CLAUDE.md references are unimplemented\n\n---\n\n## Bootstrapping\n\nRun `\u002Fck:init` to create the full hierarchy. It:\n1. Scans existing project structure\n2. Creates context directories (refs\u002F, kits\u002F, plans\u002F, impl\u002F)\n3. Creates CLAUDE.md files using standard templates\n4. Creates empty index files (cavekit-overview.md, plan-overview.md, impl-overview.md)\n5. Offers migration if legacy `context\u002Fsites\u002F` exists\n\nProperties: idempotent, non-destructive, no questions asked.\n\n---\n\n## Build-Time Updates\n\nAfter `\u002Fck:make` completes, source-tree CLAUDE.md files are generated\u002Fupdated:\n- New source directories get a CLAUDE.md with cavekit\u002Fplan references\n- Existing CLAUDE.md files get new references appended (never removed)\n- `impl-overview.md` and `plan-overview.md` are updated with current status\n\n---\n\n## Multi-Repo Strategy\n\nFor shared kits across implementations, use git submodules:\n\n```\nTier 1-2 (shared): shared-context\u002F (submodule)\n    └── refs\u002F + kits\u002F\n\nTier 3-4 (per-repo): context\u002F\n    └── plans\u002F + impl\u002F\n```\n\nEach framework repo includes the shared context as a submodule. Updates propagate via `git submodule update`.\n\n---\n\n## Integration with Other Skills\n\n| Skill | Integration |\n|-------|------------|\n| `ck:cavekit-writing` | Kits go in `context\u002Fkits\u002F` following naming conventions |\n| `ck:design-system` | DESIGN.md lives at project root; `context\u002Fdesigns\u002F` has CLAUDE.md and changelog |\n| `ck:impl-tracking` | Tracking lives in `context\u002Fimpl\u002F`, compacted when exceeding ~500 lines |\n| `ck:validation-first` | Validation results recorded in impl tracking within the hierarchy |\n| `ck:revision` | `\u002Fck:revise` traverses CLAUDE.md edges in reverse to trace bugs to specs |\n| `ck:methodology` | Context structure established during Draft phase, maintained throughout the Hunt |\n\n---\n\n## Anti-Patterns\n\n| Anti-Pattern | Why It's Wrong | Fix |\n|-------------|---------------|-----|\n| Flat file dump | No progressive disclosure, agents load everything | Use standard directory structure with indexes |\n| Missing CLAUDE.md files | No convention guidance, no DAG edges | Run `\u002Fck:init` or add manually |\n| Monolithic documents | Defeats progressive disclosure | Decompose into domains with overview indexes |\n| Stale archives in active dirs | Wastes context window | Move to `impl\u002Farchive\u002F` |\n| Duplicating cavekit content in CLAUDE.md | Content drifts, double maintenance | CLAUDE.md files only contain references |\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FJuliusBrussee\u002Fblueprint\u002Fskills\u002Fcontext-architecture",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill context-architecture",{"tool":60,"command":61},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill context-architecture",{"tool":63,"command":64},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill context-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJuliusBrussee\u002Fblueprint\u002Fskills\u002Fcontext-architecture\u002FSKILL.md",true,[],[69,79,87,95,103,111],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":74,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":78},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":78},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":78},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":78},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":78},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":78},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]