What problem does it solve? Engineering teams lose track of their own coding conventions as codebases evolve, forcing engineers and AI agents to re-derive patterns every session. This Skill produces and maintains a living guide to the patterns, conventions, and design idioms actually used in a repository. ## Core Features & Use Cases - Bootstrap survey: Spawns parallel exploration agents across 12 seed categories (architecture, ui-state, compose-correctness, data, concurrency, errors, resources, di, kmp, testing, observability, build) to produce docs/PATTERNS.md plus per-category files. - Incremental updates: Uses per-category git cursors and path-scope globs to re-verify only what changed, classifying entries as KEEP, UPDATE, DECOMMISSION, or FLIP via a triage plan the user approves before any writes. - Structured pattern schema: Each entry records status, coverage, trade-offs, pseudocode application guidance, file-path citations, and optional senior deep dives. - Use Case: An Android team adopting Compose wants new hires to follow existing StateFlow and MVVM conventions; run the skill to generate docs/patterns/ui-state.md documenting the established shapes with real file references. ## Quick Start Ask the assistant to document the coding patterns and architectural conventions used in this codebase.
