Crystallize Gold Experience

Map the discovery to the correct .opencode/ category:

Step 3: Draft Precise Updates

Follow the AReaL Formatting Standard:

• Imperative Mood: Use "Always," "Never," "Ensure." (e.g., "Never use print() in hot paths").
• Evidence-First: Include the specific bash command used to verify the state.
• Short & Precise: Use bullet points. No introductory fluff.

Step 4: Update and Commit

1. Read the relevant .opencode/ file.
2. Inject the new intelligence into the "Common Issues," "Key Requirements," or "Debugging" sections.
3. Perform a "Crystallization Commit" to save the system state.

Reference Examples (AReaL Gold Standard)

Key Requirements

1. Never delete existing knowledge: Only append or refine unless a rule is proven wrong.
2. Externalize everything: If you "figured it out" in your reasoning, it must be written in the .opencode/ folder.
3. Machine-Readable: Keep checklists structured so future agents can parse them as tasks.
4. Reference the Gold Standard: When adding a skill, link to the best implementation in the current repo as the "Template."

Common Mistakes

• ❌ Writing long paragraphs (AI context is more efficient with lists).
• ❌ Keeping lessons "in-head" across session restarts (leads to regression).
• ❌ Documenting the "What" (Code) instead of the "Why" (Architecture/Trap).
• ❌ Forgetting to include the bash commands used for verification.