componentslisted

# components **Fetch flashy, proven, animated React+Tailwind components LIVE from code libraries instead of hand-writing complex motion.** User describes an effect → match it → pull the real component at build time → adapt to brand. ## What this is - **PRIMARY: showpiece live-fetch.** Distinctive/animated components (laptop scroll, 3D card, beams, globe, marquee...) fetched live from code libraries via registry CLI / WebFetch. - **FALLBACK: plain components.** Standard button/form/modal/table when no "wow" is asked. - **SOURCE layer only.** After placing the component, hand off final polish/distinctiveness to `impeccable` / `frontend-design` **if installed** - both are optional sibling skills, not dependencies of this repo. See `references/handoff.md` for what to do when neither is available. - **Galleries ≠ code.** Dribbble, godly.website, Awwwards = visual reference ONLY. Never fetch components from them. - **Layout curation.** `layouts[]` are pre-composed arrangements (web sections or video beat patterns). `TASTE.md` is the required-reading standard for picking or building one - read it before selecting a layout. ## Decision flow ``` user wants a UI component (React + Tailwind)? ├─ is it a distinctive / animated / "wow" effect? │ ├─ YES (primary path): │ │ 1. match the described effect → showpiece[] entry (name or aliases) │ │ 2. no direct match → search code_libraries[] live for the effect │ │ (WebFetch the library's components page, find the closest