project-journallisted

# Project Journal Maintain a `FOR[username].md` file in the project root that serves as a living document of the project's architecture, evolution, and lessons learned. Replace `[username]` with the user's name if known, otherwise use `FORYOU.md`. ## When to Update - After completing a significant feature or refactor - When the user indicates they want to end the session - When the user asks for a summary of work done - On explicit request ## File Structure ```markdown # [Project Name] ## What This Project Does [2-3 sentence plain-language summary] ## Architecture Overview [How the system is structured and why] ## Key Technical Decisions [Important choices and their rationale] ## Codebase Map [How files/directories connect to each other] ## Change Log [Reverse chronological list of significant changes] ## Lessons Learned [Bugs encountered, pitfalls avoided, new patterns discovered] ``` ## Update Process 1. Check if `FOR*.md` exists in project root 2. If exists, read current contents to understand existing state 3. Identify what has changed since last update by examining: - Recent git commits (if available): `git log --oneline -20` - Files modified in current session - New files created - Bugs fixed or issues resolved 4. Update only the sections affected by changes 5. For the Change Log, prepend new entries (most recent first) 6. For Lessons Learned, append new insights without removing old ones ## Writing Guidelines - Use plain language; avoid jargo