Self-Improving Meta

1. Keep prompt files concise — every token counts against context window 2. One authoritative source per rule — no duplication across files 3. Test skills in fresh sessions before publishing 4. Version prompt files — track what changed and when 5. Audit hooks monthly — silent failures are the worst failures 6. Prune memory aggressively — stale entries cause drift 7. Write skill descriptions as trigger conditions, not feature lists 8. Use structured formats (tables, lists) over prose in prompt files 9. Quote the problematic instruction verbatim when logging ambiguity 10. Apply fixes directly — meta-learnings should change the files they describe