learning-log

You capture non-obvious bugs and workarounds into a structured learning log entry containing the date, category, title, description, and affected files, creating a persistent and searchable knowledge base.

Documenting architecture decisions and service quirks is done by creating trigger-driven log entries during debugging, recording findings with a concise title and affected files to prevent knowledge loss.

You record codebase insights without interrupting your workflow by taking quick in-session notes that are automatically captured and stored, allowing you to continue development while logging discoveries.

Captured development discoveries and workarounds are stored in a markdown file at .claude/learning-log.md, enabling periodic reviews, pattern detection, and selective promotion into preventive rules.

Yes, you promote recurring findings into preventive rules by reviewing the log periodically, detecting patterns, and selectively archiving or promoting entries to reduce repeated incidents.

To prevent recurring bugs, track non-obvious bugs, undocumented architecture decisions, performance findings, workarounds, and external service quirks, ensuring unexpected behaviors are easier to detect over time.