component-gallery
Reference patterns with CSS values for: buttons, form inputs, badges, breadcrumbs, pagination, horizontal/vertical/mobile navigation, tables, cards, modals, alerts, pricing pages, hero sections, feature grids, testimonials, footers, activity feeds, checkout pages, dropdowns, and empty states. Apply whenever implementing, styling, or reviewing a specific UI component — provides concrete sizing, padding, shadow, and layout values rather than abstract principles.
What this skill does
# Component Gallery
## Buttons
### Variants
- **Primary**: Bold background color (primary-500+), white text, used for main CTAs
- **Secondary**: Light background or outline, darker text, for secondary actions
- **Tertiary/Ghost**: No background, text-only with hover state, for least-important actions
- **Destructive**: Red tones, for delete/remove actions — keep smaller than primary buttons
### Sizes
- **Large**: `padding: 16px 24px; font-size: 18px;` — hero sections, marketing CTAs
- **Default**: `padding: 12px 20px; font-size: 16px;` — forms, dialogs
- **Small**: `padding: 8px 16px; font-size: 14px;` — inline actions, table rows
- **Extra Small**: `padding: 6px 12px; font-size: 12px;` — compact UIs, tags
### Design Tips
- Padding is NOT proportional to font size — larger buttons get disproportionately more generous padding
- Add subtle depth: `box-shadow: inset 0 1px 0 hsl(224, 84%, 74%); box-shadow: 0 1px 3px hsla(0,0%,0%,.2);`
- On click, reduce shadow to simulate pressing: switch from medium to small shadow
- Use brand colors for custom checkboxes/radio buttons, not browser defaults
- Consider selectable cards as alternative to radio button groups
---
## Form Inputs
### Text Inputs
- Light inset effect: `box-shadow: inset 0 2px 2px hsla(0, 0%, 0%, 0.1);`
- Adequate padding: at least `10px 12px`
- Clear focus state with ring/outline
- Labels above inputs (stacked), not beside them
### Layout
- Space between label and its input should be LESS than space between form groups
- Typical: 8px label-to-input, 24px between groups
- Use 2-column layouts for short related fields (First Name / Last Name)
- Single column for most forms — don't force 2 columns unnecessarily
### Validation
- Error messages near the field, not at the top of the form
- Red border + red text for errors
- Green checkmark for validated fields (optional)
- Don't rely on color alone — include text messages
---
## Badges / Tags
### Variants
- **Filled**: Solid background with contrasting text (e.g., white on primary-500)
- **Light**: Light tinted background with darker text (e.g., primary-50 bg + primary-700 text)
- **Outline**: Border only with matching text color
- **Dot indicator**: Small colored circle before text
### Sizes
- **Default**: `padding: 2px 8px; font-size: 12px; border-radius: 9999px;`
- **Large**: `padding: 4px 12px; font-size: 14px;`
### Usage
- Status indicators (Active, Pending, Rejected)
- Categories/labels
- Counts/notifications
- Use light variants over filled for less visual noise in tables
---
## Breadcrumbs
### Pattern
```
Home > Category > Subcategory > Current Page
```
### Design Tips
- Use a separator (>, /, chevron icon) between items
- De-emphasize all items except the current page
- Current page should not be a link
- Keep font size small (12-14px)
- Use lighter text color for separators
---
## Pagination
### Variants
- **Numbered**: `< 1 2 3 ... 10 >` — standard for search results
- **Prev/Next only**: Simpler, for sequential content
- **Load More button**: Single button, good for feeds
- **Infinite scroll**: Auto-load, for social feeds
### Design Tips
- Highlight current page with primary color background
- Disabled state for prev/next at boundaries
- Include first/last page shortcuts for large page counts
- Keep touch targets at least 44x44px on mobile
---
## Navigation
### Horizontal Navigation
- **Top bar**: Logo left, links center or right, CTA button far right
- **Tab style**: Underline or background highlight for active state
- Active indicator: colored bottom border (`border-bottom: 2px solid primary-500`)
- Keep items to 5-7 max; use dropdown for overflow
### Vertical / Sidebar Navigation
- Full-height sidebar, typically 240-280px wide (FIXED width, not percentage)
- Group related items with section headers
- Active state: background highlight + left border accent or bold text
- Icons optional but helpful for recognition
- Collapse to icons-only on smaller screens
### Mobile Navigation
- Hamburger menu for most apps
- Bottom tab bar for primary navigation (iOS pattern)
- Keep bottom nav to 3-5 items max
---
## Tables
### Design Tips
- Right-align numbers for easy comparison
- Combine related columns to reduce width (name + role in one column with hierarchy)
- Add profile images/avatars where appropriate
- Use colored badges for status columns
- Zebra striping optional — extra spacing between rows can work better
- Don't force percentage-based column widths; let content determine width
- Use `white-space: nowrap` for columns that shouldn't wrap
### Patterns
- **Simple table**: Headers + rows, minimal borders
- **Rich table**: Avatars, badges, combined columns, actions column
- **Condensed**: Tighter padding for data-dense dashboards
---
## Cards
### Anatomy
- Optional image/media at top
- Title (16-20px, bold)
- Description (14-16px, secondary color)
- Metadata (12-14px, tertiary color)
- Optional footer with actions
### Design Tips
- Use accent borders at the top for visual interest
- Subtle shadow: `box-shadow: 0 1px 3px hsla(0,0%,0%,.12), 0 1px 2px hsla(0,0%,0%,.24);`
- Consistent image aspect ratios with `object-fit: cover`
- Cards crossing background transitions create depth (overlap technique)
---
## Modals / Dialogs
### Design Tips
- Large shadow for prominence: `box-shadow: 0 15px 35px hsla(0,0%,0%,.2);`
- Semi-transparent backdrop: `background-color: rgba(0, 0, 0, .5);`
- Max-width constraint (400-600px for forms, up to 800px for complex content)
- Clear close action (X button top-right, Cancel button bottom)
- Focus trap for accessibility
- Destructive confirmations: make the destructive button less prominent (not big and red)
---
## Alerts / Notifications
### Variants
- **Info**: Blue tinted (blue-50 bg, blue-700 text, blue-500 left border)
- **Success**: Green tinted
- **Warning**: Yellow tinted
- **Error**: Red tinted
### Design Tips
- Colored left border accent (4px) is a classic, effective pattern
- Use icon + text, don't rely on color alone
- Light background with darker text of the same hue
- Dismissible with X button for non-critical alerts
### CSS Pattern
```css
.alert-info {
background-color: /* primary-50 */;
color: /* primary-900 */;
border-left: 4px solid /* primary-500 */;
}
```
---
## Pricing Pages
### Layout
- 2-4 plan options side by side
- Highlight recommended plan (accent border, raised with shadow, or "Popular" badge)
- Feature comparison list with checkmarks
- CTA button for each plan
### Design Tips
- Price should be the most prominent element
- Use hierarchy: Plan name (small, uppercase, letter-spaced) > Price (large, bold) > Period (small, muted)
- De-emphasize less popular plans
- Toggle between monthly/annual billing
---
## Marketing Sections
### Hero Section
- Large headline (36-72px)
- Supporting paragraph (18-20px, max 45-75 chars per line)
- Primary CTA button + optional secondary CTA
- Optional image/illustration to the right or below
### Feature Sections
- 3-4 features in a grid
- Icon + heading + short description per feature
- Icons in colored shapes (don't scale up small icons — wrap them in a background shape)
- Center-aligned text works for short descriptions (2-3 lines max)
### Testimonials
- Large quotation marks as visual element (oversized, colored)
- Quote text in larger font or italic
- Attribution: name, title, company, optional photo
---
## Footers
### Content
- Logo + short description
- Navigation links in columns (Product, Company, Resources, Legal)
- Social media links
- Newsletter signup
- Copyright notice
### Design Tips
- Different background color from main content (darker)
- 3-4 columns on desktop, stacked on mobile
- Keep link font size small (14px)
- Subtle separators between sections
---
## Activity Feeds
### Pattern
- Avatar + name + action + timestamp per entry
- Vertical timeline line connecting entries
- Group by date
- Different icons/colors for different action types
---
## Checkout / E-Commerce
### CaRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.