Trigger: Use FIRST before any new UI build. Checks if a template or component already exists. 6,904+ pre-built files across 4 frameworks.
Decision Tree
| Building... | Load This Skill | Framework |
|---|---|---|
| Polished Tailwind sections (hero, pricing, CTA, features) | /tailwind-plus-ui | React + Tailwind + Headless UI |
| Animated/flashy marketing pages, dark-mode landing pages | Aceternity UI | React + Tailwind + Framer Motion |
| Full site scaffold (SaaS, portfolio, docs, fintech, podcast) | Cruip templates | Next.js + Tailwind |
| shadcn/ui components (dashboards, forms, tables, charts) | /shadcn-blocks | Next.js + shadcn/ui |
| WordPress client site (any service niche) | Elementor templates | WordPress + Elementor Pro |
Core Rules
- NEVER build a hero, pricing section, CTA, feature grid, or testimonial from scratch — 50+ pre-built options exist
- NEVER scaffold a new Next.js marketing site from zero — start from Cruip or Aceternity
- NEVER build a WordPress service site without checking Elementor kits first — 57 niche-specific kits
- Copy and modify > build from scratch — these are paid, production-quality templates
Steps
- Identify what's being built — section type, site type, tech stack
- Match to the decision tree above
- Load the relevant skill to get specific component paths
- Locate the template in installed files
- Adapt the template — never build from scratch when a match exists
Installed Paths
- ui-blocks (ready to use):
D:\ClaudeDev\00_GITHUB\_working-on\Templates\ui-blocks\ - Zip backups:
E:\LOC\Design Templates\ - Backup installed:
E:\LOC\Design Templates\ui-blocks-installed\
Examples
New SaaS marketing site: Load Cruip templates, find the SaaS scaffold, adapt it.
Add a pricing section: Load /shadcn-blocks or /tailwind-plus-ui, locate pricing component, copy and adapt. 10 minutes instead of 2 hours.
WordPress plumbing client: Load Elementor templates, find the plumbing niche kit, import and customize.