Design System Components
# Component Development Workflow with Figma MCP
## Workflow Steps
### 1. Initial Setup & Analysis- **Initialize Figma MCP Connection** - Use the Figma MCP (Model Context Protocol) for design system integration - Verify access to the design file/project - Extract node ID from provided Figma URL
### 2. Analyze Figma Design- **Extract Component Data**
### 3. Generate Component Specifications
#### Visual Specifications:- Dimensions (width, height, padding, margins)- Typography (font family, size, weight, line-height)- Colors (fill, stroke, gradients)- Border radius and shadows- Spacing and alignment rules
#### Behavioral Specifications:- Interactive states (hover, active, focus, disabled)- Animations and transitions- Responsive behavior and breakpoints- Accessibility requirements (ARIA labels, keyboard navigation)
### 4. Implementation Phase
#### Create Interactive Component:- Build fully functional component matching Figma design- Implement all interactive states and behaviors- Add proper TypeScript types/interfaces- Include all variants from Figma- Ensure responsive design implementation- Add proper error handling and edge cases
### 5. Create Preview Showcases
#### Design Tokens Preview:- Color tokens used in the component- Typography scale and tokens- Spacing tokens (margins, padding, gaps)- Border radius tokens- Shadow/elevation tokens- Animation/transition tokens
#### Styles Preview:- All component variants side by side- Theme variations (light/dark mode if applicable)- Size variations (small, medium, large)- State demonstrations (interactive demo)- Responsive behavior at different breakpoints
#### Properties Preview:- Live prop manipulation interface- Documentation for each prop- Code examples for common use cases- Validation rules and constraints- Default values clearly indicated
### 6. Component-Specific Features
### 7. Documentation Generation(describe what you want)
### 8. Testing Setup(describe what you want)
## Output Structure
### Directory Organization:(describe what you want)
## Execution Order
1. **Parse Figma URL** → Extract node ID2. **Fetch Design Data** → Get all component information from Figma3. **Analyze & Document** → Create specifications4. **Build Component** → Implement with all features5. **Create Previews** → Generate visual showcases6. **Write Documentation** → Complete usage guides7. **Setup Tests** → Ensure qualityBuild a reusable React input component that matches these Figma specs (paste link).
Use CDN React + plain CSS, include states (default, focus, disabled, read-only, error, success), optional left/right icons, hint/error/success messaging, and a demo page that showcases each state and size.# Bare Minimum Prompt
**Figma Link**: [Share your Figma design link here]
## TaskShort description what you want
### Core BehaviorShort description what you want
### Tech- Vanilla JS, Tailwind CSS, Inter font- 16px icons, keyboard accessible- Emit `filterChange` event
### Files- `index.html`, `filter.js`, `styles.css`
**Done when**: Matches Figma design with full interactivity.Prompt from the video Vibe-coding for designers #2 - Model vs Prompt
**Step 1**: Paste your Figma design link here:
## TaskCreate an interactive filter chip component that matches the Figma design with these behaviors:
### Core Functionality- **Two states**: "All" state (unfiltered) and "Selected" state (filtered)- **State switching**: Component changes appearance/content between states- **Interactive dropdown**: Click chip to open selection interface- **Dynamic content**: Shows different text/icons based on current state- **Remove action**: Way to delete/clear the filter entirely
### Required Interactions1. **Default state**: Component shows initial appearance from Figma2. **Click chip**: Opens dropdown/modal for user selections3. **Make selections**: User can choose/unchoose options4. **Apply changes**: Component updates to show selections5. **Clear/remove**: User can reset or delete the filter
### Technical Requirements- **Framework**: Use what fits your project (React, Vue, vanilla JS, etc.)- **Styling**: Match Figma specs exactly (colors, fonts, spacing, borders)- **Icons**: Implement icon switching between states as shown in design- **Responsive**: Ensure mobile-friendly touch targets- **Accessible**: Keyboard navigation + screen reader support- **Events**: Emit changes so parent components can respond
### Implementation Guide1. **Analyze Figma**: Identify the two states and their visual differences2. **Extract tokens**: Colors, typography, spacing, border radius from design3. **Plan interactions**: Map user actions to state changes4. **Build component**: Start with static states, add interactivity5. **Test thoroughly**: Verify all interactions work across devices
### Success Criteria✅ Visual design matches Figma exactly✅ State transitions work smoothly✅ Dropdown/selection interface functions correctly✅ Component integrates with parent application✅ Accessible via keyboard and screen readers✅ Works on mobile and desktop
**Deliverable**: Functional filter component that replicates Figma design with full interactivity.