figma-make-website-builder
Structured 9-phase workflow for building production-ready websites using Claude (architecture, logic, reasoning) paired with Figma Make (UI, interactions, deployment). Use when planning, designing, or building a website with Figma Make.
Best use case
figma-make-website-builder is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Structured 9-phase workflow for building production-ready websites using Claude (architecture, logic, reasoning) paired with Figma Make (UI, interactions, deployment). Use when planning, designing, or building a website with Figma Make.
Teams using figma-make-website-builder should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/figma-make-website-builder/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How figma-make-website-builder Compares
| Feature / Agent | figma-make-website-builder | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Structured 9-phase workflow for building production-ready websites using Claude (architecture, logic, reasoning) paired with Figma Make (UI, interactions, deployment). Use when planning, designing, or building a website with Figma Make.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Figma Make Website Builder A structured 9-phase workflow for building production-ready websites using Claude paired with Figma Make. Claude handles architecture, logic, content strategy, and QA. Figma Make handles pixel-perfect UI, interactions, and deployment. ## Quick Reference | Phase | File | Role | Description | |-------|------|------|-------------| | 1 | [phase-1-architecture-strategy.md](references/phase-1-architecture-strategy.md) | Principal Architect | Site map, user journeys, component inventory, tech stack | | 2 | [phase-2-design-system.md](references/phase-2-design-system.md) | Design Director | Color, typography, spacing, 30+ component specs | | 3 | [phase-3-content-architecture.md](references/phase-3-content-architecture.md) | Conversion Copywriter | Headlines, CTAs, social proof, FAQ content | | 4 | [phase-4-component-logic.md](references/phase-4-component-logic.md) | Frontend Architect | State machines, data flow, error handling, React structure | | 5 | [phase-5-prompt-engineering.md](references/phase-5-prompt-engineering.md) | AI Prompt Engineer | Convert specs into 5 Figma Make prompts | | 6 | [phase-6-animation-interaction.md](references/phase-6-animation-interaction.md) | Motion Designer | Load sequences, scroll behaviors, micro-interactions | | 7 | [phase-7-responsive-strategy.md](references/phase-7-responsive-strategy.md) | Responsive Specialist | Breakpoints, layout transforms, content prioritization | | 8 | [phase-8-data-integration.md](references/phase-8-data-integration.md) | Full-Stack Architect | Data models, APIs, auth, Supabase integration | | 9 | [phase-9-qa-optimization.md](references/phase-9-qa-optimization.md) | QA Engineer | Performance, accessibility, SEO, security checklist | ## Workflow Overview ``` Phase 1-4 (Claude) Phase 5 (Bridge) Phase 6-8 (Claude) Phase 9 (Review Loop) ┌─────────────────┐ ┌──────────────┐ ┌─────────────────┐ ┌──────────────────┐ │ 1. Architecture │ │ 5. Convert │ │ 6. Animation │ │ 9. QA Checklist │ │ 2. Design System│───▶│ specs to │────▶│ 7. Responsive │───▶│ ↕ iterate │ │ 3. Content │ │ Figma Make │ │ 8. Data Layer │ │ Figma Make edits │ │ 4. Logic │ │ prompts │ │ │ └──────────────────┘ └─────────────────┘ └──────────────┘ └─────────────────┘ ``` - **Phases 1-4** and **6-8**: Done in Claude - **Phase 5**: Bridge — converts Claude output into Figma Make prompts - **Phase 9**: Review loop — iterate between Claude QA and Figma Make refinement - **Target**: ~2 hours for a complete production website ## Problem → Phase Mapping | Problem | Start With | |---------|------------| | Starting a new website from scratch | [Phase 1 — Architecture](references/phase-1-architecture-strategy.md) | | Need a design system or brand tokens | [Phase 2 — Design System](references/phase-2-design-system.md) | | Writing website copy and CTAs | [Phase 3 — Content](references/phase-3-content-architecture.md) | | Building interactive components (forms, calculators) | [Phase 4 — Component Logic](references/phase-4-component-logic.md) | | Ready to prompt Figma Make | [Phase 5 — Prompt Engineering](references/phase-5-prompt-engineering.md) | | Adding animations and interactions | [Phase 6 — Animation](references/phase-6-animation-interaction.md) | | Making a site responsive | [Phase 7 — Responsive](references/phase-7-responsive-strategy.md) | | Connecting a database or API | [Phase 8 — Data Integration](references/phase-8-data-integration.md) | | Reviewing and optimizing before launch | [Phase 9 — QA](references/phase-9-qa-optimization.md) | ## Usage Run phases sequentially — each phase's output feeds the next. You can also jump to individual phases for specific tasks. When running the full workflow, provide the website type (portfolio, SaaS, e-commerce, etc.) and brand attributes (minimal, bold, luxury, playful) at Phase 1 to propagate context through all subsequent phases.
Related Skills
telegram-bot-builder
Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategie...
skill-builder-medical
Specialized guide for creating Claude Code skills for Dr. Sophia AI medical system. Includes healthcare integration patterns (FHIR/REST/EHR), medical compliance validation (HIPAA/PBS/TGA), botanical design integration, Railway deployment patterns, and proven examples from our 7 production skills. Use when creating skills specifically for Dr. Sophia AI, medical integration skills, healthcare compliance skills, EHR workflows, or adapting our proven skill patterns.
Skill Builder / Creator
Create high-quality skills with modular structure, progressive disclosure, and token-efficient design.
makepad-router
CRITICAL: Use for ALL Makepad/Robius questions including widgets, layout, events, and shaders. Triggers on: makepad, robius, live_design, app_main, Widget, View, Button, Label, Image, TextInput, ScrollView, RoundedView, SolidView, PortalList, Markdown, Html, TextFlow, layout, Flow, Walk, padding, margin, width, height, Fit, Fill, align, spacing, event, action, Hit, FingerDown, FingerUp, KeyDown, handle_event, click, tap, animator, animation, state, transition, hover, pressed, ease, shader, draw_bg, draw_text, Sdf2d, pixel, gradient, glow, shadow, font, text_style, font_size, glyph, typography, tokio, async, spawn, submit_async, SignalToUI, post_action, apply_over, TextOrImage, modal, collapsible, drag drop, AppState, persistence, theme, Scope, deploy, package, APK, IPA, WASM, cargo makepad, makepad widget, makepad 组件, makepad 按钮, makepad 布局, makepad 事件, makepad 动画, makepad 着色器, 创建组件, 自定义组件, 开发应用, 居中, 对齐, 点击事件, 悬停效果, 渐变, 阴影, 字体大小
form_builder
Builds form components and data collection interfaces including contact forms, registration flows, checkout processes, surveys, and settings pages. Includes 50+ input types, validation strategies, accessibility patterns (WCAG 2.1), multi-step wizards, and UX best practices. Provides decision trees from data type to component selection, validation timing guidance, and error handling patterns. Use when creating forms, collecting user input, building surveys, implementing validation, designing multi-step workflows, or ensuring form accessibility.
figma
Use MCP Figma for design system integration, asset export, and design-to-code workflows.
figma-use
Control Figma via CLI — create shapes, frames, text, components, set styles, layout, variables, export images. Use when asked to create/modify Figma designs or automate design tasks.
figma-design
Access Figma designs, extract design systems, and retrieve component specifications. Use when implementing UI from Figma mockups, extracting design tokens, or analyzing design files.
figma-automation
Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas.
figma-analyze
Analyze Figma designs for code implementation readiness and design-code parity. Use when working with Figma URLs, analyzing component designs, or checking token consistency.
assessment-builder
Creates assessments with varied question types (MCQ, code-completion, debugging, projects) aligned to learning objectives. Use when educators design quizzes/exams, need questions at appropriate Bloom's cognitive levels, want balanced cognitive distribution (60%+ non-recall), or require rubrics for open-ended questions.
appimage-builder
Build AppImage bundles with AppDir structure for portable Linux applications