KNOWLEDGE_INDEX.md.tmpl
1.9 KB61 lines
---type: knowledge-indexscope: 01-Knowledgetags:- moc- knowledge- indexcreated: [YYYY-MM-DD]updated: [YYYY-MM-DD]aliases:- Knowledge Map---<!--01-Knowledge/KNOWLEDGE_INDEX.md: Routing layer for the knowledge folder.Each entry: filename, one-line description, when to read it.If knowledge is TBD, list the slots and what should fill them.Read this first when working on a task; it routes to the right knowledge file.--># [PROJECT NAME]: Knowledge IndexThis is the routing layer for the project's knowledge base. Read this first to know where to find what.## Files in this folder| File | What it contains | When to read it ||------|------------------|-----------------|| [[01-Knowledge/file-1\|file-1]] | [One line] | [Trigger, e.g., "Before drafting any client-facing output"] || [[01-Knowledge/file-2\|file-2]] | [One line] | [Trigger] || [[01-Knowledge/file-3\|file-3]] | [One line] | [Trigger] |## File types and conventions- **Templates**: files ending in `-template.md`. Copy and fill rather than edit in place.- **References**: files starting with `ref-`. Read-only canonical sources.- **Examples**: files in `examples/`. Real-shaped illustrations of inputs and outputs.- **Data**: CSVs, JSONs, structured data. Don't modify in place; copy to `02-Working/` first.## Knowledge gaps<!-- TBD slots that need to be filled before the project is fully operational.Each entry: what's missing, why it matters, where it should live when added. -->- **[TBD: filename]**: [What this file should contain. Why the project needs it. Suggested format.]## Scoped instructions[If a [[01-Knowledge/CLAUDE-knowledge]] file exists, reference it here:]For Claude-specific operational rules when working in `01-Knowledge/`, see [[01-Knowledge/CLAUDE-knowledge]].[Otherwise:]No scoped Claude instructions for this folder. Root [[CLAUDE]] instructions apply.## Last reviewed[YYYY-MM-DD]