self-commenting

To preserve developer intent across sessions, embed grep-searchable AICODE-* memory markers directly into source code. This captures critical decisions, TODOs, and bug fixes within the codebase, ensuring context survives across edits without external services.

The best way to add grep-searchable notes is using structured AICODE annotations with explicit marker types like NOTE, TODO, and FIX. This distinguishes notes, tasks, and bug fixes, enabling standard grep workflows to scan complex logic easily.

Start a coding session by running a standard grep scan for AICODE markers using the command grep -rn "AICODE-" <path>. This reveals all stored decisions, tasks, and fixes, establishing context before you begin working.

Yes, you can use standard grep workflows to manage cross-session code memory without external services. The markers, actions, and conventions are defined locally in SKILL.md and references/conventions.md, integrating directly with existing command-line search tools.

Follow the SCAN → WORK → ANNOTATE workflow to keep context aligned with code changes. Scan existing AICODE markers first, perform your coding work, then annotate the source code with new markers to document decisions and fixes.

You need to embed memory markers when working on complex tasks, non-obvious logic, and bug fixes. Adding AICODE annotations during these scenarios ensures future sessions can immediately understand the context and reasoning behind specific code changes.