Update Docs Skill

Update README.md files in the folders where code was changed. Documentation lives next to the code it describes — each component/abstraction folder has its own README.

When to Use

Activate this skill when:

• The user explicitly asks to update documentation after changes
• After completing a task that adds, removes, or significantly modifies files in a component/abstraction folder

Principles

1. Co-located — Each README lives in the folder it documents
2. Lean — Only document what helps a developer understand the folder's purpose, structure, and patterns
3. Precise — Accurate file names, sizes, type counts, and descriptions
4. Compact — No verbose prose. Use tables, bullet points, and code snippets
5. Delta-driven — Only update sections affected by the change. Don't rewrite unrelated content

README Structure Convention