apply-figma-make
Apply Figma Make exported designs to website pages. Converts React/motion code to framework-appropriate code (Astro, Next.js, etc.) with CSS animations.
What this skill does
# Figma Make Design Application
Apply designs exported from Figma Make to your website pages. Handles the conversion from React/motion.js to your framework's conventions.
## When to Use
This skill activates when:
- User provides a Figma Make zip file
- User says "apply this design", "use this Figma export"
- User wants to implement a design from a `.zip` containing React components
## Workflow
### Phase 1: Extract and Analyze
1. **Extract the zip file** to a temporary directory
```bash
unzip -o "<path-to-zip>" -d "$TMPDIR/figma-design"
```
Note: Use `$TMPDIR` or any suitable temp directory. Claude will determine the appropriate location at runtime.
2. **Identify key files**
- Main component: `src/app/App.tsx` or similar
- Guidelines: `guidelines/Guidelines.md` (if present)
- Theme/styles: `src/styles/theme.css`, `tailwind.css`
3. **Read the design file** to understand:
- Layout structure (sections, containers)
- Animation patterns (motion.js usage)
- Color scheme and gradients
- Component hierarchy
### Phase 2: Gather User Constraints
**IMPORTANT**: Before applying, ask the user about constraints:
```
Task(subagent_type="general-purpose", prompt="
Ask the user using AskUserQuestion:
1. Which page(s) should receive this design?
2. Are there elements to KEEP unchanged? (e.g., existing logo, header, footer)
3. Are there elements to REMOVE from the design? (e.g., badges, specific sections)
4. Any other customizations needed?
")
```
Common constraints:
- **Keep existing logo** - Don't replace with design's placeholder logo
- **Remove marketing badges** - "AI-powered", "New", etc.
- **Preserve navigation structure** - Keep existing routes/links
### Phase 3: Convert and Apply
**Conversion Rules for Astro/Static Sites:**
| Figma Make (React) | Convert To |
|-------------------|------------|
| `motion.div` with `animate` | CSS `@keyframes` animation |
| `motion.div` with `whileHover` | CSS `:hover` with `transition` |
| `motion.div` with `whileInView` | CSS animation (plays on load) |
| `useState`/`useEffect` for scroll | CSS or remove if decorative |
| `[...Array(N)].map()` particles | CSS gradients or fewer elements |
| Inline `style={{}}` | Tailwind classes or `<style>` |
**Delegate to executor:**
```
Task(
subagent_type="oh-my-claudecode:executor",
model="sonnet",
prompt="Apply the Figma Make design to [target page].
DESIGN SOURCE: [extracted temp directory]/src/app/App.tsx
TARGET FILE: [path to target page]
CONSTRAINTS:
- [User's constraints from Phase 2]
CONVERSION REQUIREMENTS:
- Convert all motion.js animations to CSS @keyframes
- Convert React state-based animations to CSS transitions
- Replace particle arrays with CSS gradient backgrounds
- Use Tailwind classes where possible
- Add custom CSS in <style> tags for complex animations
PRESERVE:
- Existing imports and layout structure
- Logo references (use existing logo paths)
- Navigation links and routes
OUTPUT: Modified page file with design applied"
)
```
### Phase 4: Optimize
After initial application, simplify the code:
```
Task(
subagent_type="code-simplifier:code-simplifier",
prompt="Optimize the recently modified files:
- Remove Figma Make boilerplate
- Consolidate duplicate Tailwind classes into CSS utilities
- Convert repeated HTML into data-driven loops
- Simplify complex animations
- Remove unnecessary wrapper divs
Keep visual design intact - only simplify implementation."
)
```
### Phase 5: Verify
1. **Build the project**
```bash
npm run build
```
2. **Check for errors** - Fix any build/type errors
3. **Report changes** - List modified files and key changes
## Example Usage
```
User: Apply this design to homepage
/Users/me/Downloads/Homepage-Design.zip
Claude:
1. Extracts zip to a temporary directory
2. Reads App.tsx to understand design
3. Asks: "Any elements to keep or remove?"
4. User: "Keep our logo, remove the AI badge"
5. Applies design with constraints
6. Optimizes generated code
7. Verifies build passes
8. Reports: "Homepage updated with new hero, cards, CTA sections"
```
## Tips
- **Check viewBox on SVGs** - Figma exports may have different dimensions
- **Watch for hardcoded colors** - Replace with your theme colors
- **Gradient text needs `bg-clip-text`** - Common pattern in Figma designs
- **Floating elements** - Often better as CSS pseudo-elements than DOM nodes
## Common Issues
| Issue | Solution |
|-------|----------|
| Logo appears wrong size | Check SVG viewBox matches your existing logo |
| Animations janky | Simplify or use `will-change` CSS property |
| Too many DOM elements | Replace particle arrays with CSS gradients |
| Colors don't match | Map Figma colors to your Tailwind theme |
Related 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.