Reflect

Adapted from Poteto's brainmaxxing reflect (MIT, see THIRD_PARTY.md). This repository has no separate memory vault: what the next agent must know lives in the repository itself, where it is reviewed like code.

Process

1. Scan the session for:
   • mistakes made and corrections received;
   • the product owner's preferences (how they want the app to behave or read);
   • codebase knowledge gained (gotchas, why something is the way it is);
   • library or tool quirks (vendor/boring/, Flue, the model provider);
   • friction in a skill (boring-app-template, build-app) or in the app's checks;
   • repeated manual steps.
2. Skip anything trivial or already written down (grep AGENTS.md, docs/, the skills).
3. Route each learning (below), smallest durable form first.
4. Put the changes in the current branch, or a new one, and say what you changed.