personal memory agent
Add self-contained codebase principle to development guidelines
Explicitly documents that this project has no external dependents,
so backwards-compatibility shims, fallback aliases, re-exports, and
legacy support code are never needed. Journal format changes use
migration scripts instead.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
+1
+1
AGENTS.md
+1
AGENTS.md
···
188
188
* **Single Responsibility**: Functions/classes do one thing well
189
189
* **Conciseness & Maintainability**: Clear code over clever code
190
190
* **Robustness**: Minimize assumptions that must be kept in sync across the codebase, avoid fragility and increasing maintenance burden.
191
+
* **Self-Contained Codebase**: All code that depends on this project lives within this repository—never add backwards-compatibility shims, fallback aliases, re-exports for moved symbols, deprecated parameter handling, or legacy support code. When renaming or removing something, update all usages directly. For journal data format changes, write a migration script (see [docs/APPS.md](docs/APPS.md) for `maint` commands) instead of adding compatibility layers.
191
192
* **Security**: Never expose secrets, validate/sanitize all inputs
192
193
* **Performance**: Profile before optimizing
193
194
* **Git**: Small focused commits, descriptive branch names. Run git commands directly (not `git -C`) since you're already in the repo.