component-gallerylisted

# Component Gallery — Pattern Research via Local RAG Research real component implementations before building. The gap between "I'll make a sidebar" and "here's how Atlassian, Shopify, and GitHub each solved sidebar navigation" is the gap between guessing and grounding. This skill bridges it. ## Philosophy Every UI component has been built thousands of times. The best implementations share patterns that no single designer invented—they emerged from convergent problem-solving across design systems with different constraints. Studying these patterns before writing code prevents reinventing solved problems, surfaces accessibility requirements that are easy to miss, and reveals implementation trade-offs that only become visible when comparing multiple approaches side by side. Pattern research is not copying. It is the equivalent of a literature review before writing a paper. Build with awareness of what exists, then make deliberate choices about what to keep, adapt, or reject. ## Quick Reference — Static Indexes Read these files directly for fast lookup. No RAG query needed. | File | Contents | |------|----------| | `references/component-index.md` | All 60 component types with alt names, example counts, descriptions | | `references/design-system-index.md` | All 95 design systems with org, tech stack, features, links | | `references/component-taxonomy.md` | Components grouped by functional category (Forms, Navigation, Feedback, Layout, Data Display, Actions) | For a quick a