Learn from Mistakes

Review the full conversation, identify every place where the user corrected the model, and update .config/rules.md so the same mistakes never happen again.

Step 1: Scan the conversation

Read every message in the conversation. Look for signals that the model made a mistake:

• •User asked to undo, revert, or fix something the model did
• •User expressed frustration or said the model was wrong
• •User had to re-explain something
• •User pointed out leftover artifacts, dead code, or incomplete changes
• •User said "that's not what I asked" or similar
• •User manually did something the model should have done

For each mistake found, extract:

1. •What happened — the specific bad behavior
2. •Why it was wrong — what the user expected instead
3. •Root cause — the general pattern behind the mistake (not the specific instance)

Generalizing properly

This is the critical part. Don't write rules about the specific code that was wrong. Write rules about the class of mistake.

Bad (too specific): "When removing a header from generateOpenCodeRules, also remove the intermediate variable" Good (general): "When removing code, review surrounding context for leftover artifacts (dead variables, unnecessary wrappers, orphaned blank lines)"

Bad (too specific): "Don't leave const opencodeRulesContent when simplifying the function" Good (general): "Clean up the full impact of every change, not just the literal lines requested"

Ask yourself: "If I saw a completely different codebase with a similar mistake, would this rule still prevent it?" If no, generalize further.

Step 2: Read and critique current rules

Read the full .config/rules.md file. Never assume it's properly written or efficient — it was built incrementally and may have accumulated cruft, weak wording, or missed opportunities.

Look at it with fresh eyes every time:

• •Are existing rules clear enough to actually prevent mistakes, or are they too vague?
• •Are there redundant or overlapping rules that should be merged?
• •Is the structure logical, or would reorganizing make it easier to follow?
• •Are there rules that could be tightened or expressed more directly?
• •Does the tone and style stay consistent throughout?

Improve anything you find, even if it's unrelated to the current session's mistakes. The goal is to leave the file better than you found it every time. Don't be afraid to make changes — the user reviews all diffs before committing.

Step 3: Update rules

Open .config/rules.md and apply changes. For each lesson learned:

1. •Already covered? — skip it, or strengthen the wording if the current version wasn't clear enough to prevent the mistake
2. •Fits an existing section? — add it there
3. •New category? — create a new section in a logical position, matching the file's existing structure and conventions

Keeping the file concise

After making changes, review the entire file for:

• •Redundant rules — merge or deduplicate
• •Rules that are subsets of other rules — remove the narrower one if the broader one is clear enough
• •Overly verbose sections — tighten the wording
• •Rules the model would follow anyway — remove obvious ones that don't need stating

If the file would be cleaner rewritten from scratch, do it. Preserve all existing rules that are still relevant, but reorganize and tighten freely.

Constraints

• •Do NOT delete rules unless they're genuinely redundant, superseded, or wrong — reword or merge instead
• •Do NOT add rules that are just common sense for any competent developer (e.g., "test your code")
• •Do NOT add rules so specific they'll never apply again

Step 4: Summary

Tell the user:

• •How many mistakes were identified
• •What rules were added, modified, or merged
• •Whether any existing rules were tightened or reorganized