extra pt2

This commit is contained in:
2026-03-09 17:34:14 +00:00
parent 457fb2068b
commit e0c4c2ed7b
14 changed files with 310 additions and 21 deletions

View File

@@ -36,12 +36,44 @@ Maintain `AGENTS.md` as the single source of truth:
- **Verify symlinks exist**: `CLAUDE.md`, `.cursorrules`, `.github/copilot-instructions.md` should all point to `AGENTS.md`
- **Do NOT duplicate `.memory/` contents** — instruction file is for "how to work here", not "what we're doing"
### 3. Memory File Maintenance
### 3. Memory Structure Maintenance
- Review `.memory/` files for accuracy, staleness, and completeness.
- Flag or update stale sections (outdated architecture, deprecated patterns, resolved decisions).
Ensure `.memory/` conforms to the standard structure:
```text
.memory/
├── manifest.yaml # Index: all files with descriptions + groups
├── system.md # One-paragraph project overview
├── knowledge/ # Nested knowledge domains
│ ├── overview.md
│ ├── tech-stack.md
│ ├── conventions.md
│ ├── patterns/
│ └── domain/
├── decisions.md # ADRs only
├── plans/ # One file per feature
├── research/ # Research findings
├── gates/ # Quality gate records
└── sessions/ # Session continuity
└── continuity.md
```
**Manifest maintenance:**
- When new `.memory/` files are created, update `manifest.yaml` with path, description, and group
- Descriptions should be one line explaining what the file contains
- Groups: `knowledge`, `decisions`, `plans`, `research`, `gates`, `sessions`
**Structure compliance:**
- Ensure `knowledge/` uses nested structure for domains and patterns
- Quality gate records go in `gates/<feature>.md`, not plan files
- Session continuity goes in `sessions/continuity.md`
- ADRs go in `decisions.md`, not scattered
**Content maintenance:**
- Review `.memory/` files for accuracy, staleness, and completeness
- Flag or update stale sections (outdated architecture, deprecated patterns, resolved decisions)
- Ensure cross-references between `.memory/` files are valid
- Keep hierarchy shallow (max 2 heading levels preferred).
- Keep hierarchy shallow (max 2 heading levels preferred)
## Operating Rules