What problem does it solve? When joining a new codebase or studying a reference repository, it is hard to identify which conventions and abstractions are actually worth emulating. This Skill performs a structured pattern-appreciation pass over a codebase and surfaces concrete, citable examples of effective design decisions. ## Core Features & Use Cases - Scoped codebase sweep: Detects project type, tech stack, scale, and which pattern areas (UI components, data fetching, state management, testing, error handling, and more) actually exist before analyzing. - User-confirmed focus: Presents a snapshot and asks which areas to analyze, so the output matches what you care about. - Cited pattern report: Produces 3-6 patterns per area with file:line references, inline code snippets, and explanations of why each pattern works. - Persistent learnings: Writes findings to a per-repo patterns.md file for future reference, with a guard that routes work-repo knowledge to a wiki instead. - Use Case: You clone an open-source project admired for its architecture and want to understand its state management and data-fetching conventions before contributing. Run the analysis, focus on those two areas, and receive a cited pattern guide. ## Quick Start Ask the assistant to analyze the patterns in this codebase, optionally naming a focus area such as the data layer or UI components.
