-
Notifications
You must be signed in to change notification settings - Fork 2
Agent Overlays
type: concept up: "Template-vs-Derived-Projects" tags: [architecture, agents]
The wiki-llm pattern is agent-agnostic. The template supports multiple coding assistants by overlaying agent-specific surfaces on top of the same core pattern. Each overlay implements the same operations but uses the surfaces the chosen agent supports.
| Overlay | Surface files | Status |
|---|---|---|
claude-code |
.claude/commands/wiki-*.md, .claude/skills/wiki-*.md, .claude/settings.json, optional .claude/hooks/posttooluse-hook.sh
|
Behaviorally validated in a live Claude Code session. See Lesson-Validation-Methodology. |
cursor |
.cursor/rules/wiki-*.mdc |
Structurally validated only. See Limitation-Untested-Overlays. |
scripts/instantiate.sh accepts --agent=none, which installs no overlay at all. There is no wiki/agents/none/ directory; the derived project ships only the llm-wiki core (the wiki, the SCHEMA, and the generated CLAUDE.md). The hypothesis is that a non-instructed agent (OpenCode, Pi, or any other coding assistant) can still benefit from the pattern by reading CLAUDE.md and following the documented procedures manually. Whether any specific agent actually does is empirical and currently open; see Limitation-Untested-Overlays.
Each overlay implements the Three-Operations (ingest, query, lint) plus the Verification-Gate using the surfaces that the agent supports:
- Claude Code ships both slash commands (user-invoked from the UI) and skills (model-side procedures). The slash commands are a safety net; the skills are the proactive default. Each operation has both forms, and both forms must stay in sync; see Lesson-Parallel-File-Drift.
-
Cursor ships rules.
wiki-as-memory.mdcisalwaysApply(injected into every prompt). The three operation rules (wiki-experiment,wiki-source,wiki-lint) areAgent Requestedand can be invoked explicitly with@wiki-experiment, etc.
Two policy files in wiki/agents/ are agent-agnostic:
-
discipline-gates.md: see Discipline-Gates -
verification-gate.md: see Verification-Gate
Slash commands, skills, and rules reference these files instead of duplicating their content. The same pattern is used for the Log-Entry-Attribution rule, which lives in the generated SCHEMA and is referenced from the per-overlay procedures. References eliminate the drift class that plagues the parallel-file pairs.
Each overlay has its own wiki/agents/<overlay>/setup.sh that wires its surfaces into a fresh project. The Claude Code variant supports flags like --seed-memory (initialize Claude Code's memory with the wiki maintenance subsection) and --posttooluse-hook (install the optional advisory hook; see PostToolUse-Hook).
- Template-vs-Derived-Projects
- Three-Operations
- Verification-Gate
- Discipline-Gates
- PostToolUse-Hook
- Limitation-Untested-Overlays
- Lesson-Validation-Methodology: the structural + behavioral discipline that validates each overlay
- Lesson-Parallel-File-Drift: the slash-command vs skill parallel-form that overlays inherit
- Wiki-Corrections-Log: receipt for the 2026-05-31 restructure separating minimal mode from true overlays