Site Design Replication & Remix Skill
Overview
This skill enables you to:
- Crawl & Analyze - Fetch website content and extract design patterns
- Document - Create LLM-ready markdown documentation of components and styles
- Remix - Build new sites inspired by existing designs with your own concept
When to Use This Skill
- "Clone this website" / "Copy this site's design"
- "Extract the design system from [URL]"
- "Create a site like [URL] but for [concept]"
- "Document this site's components"
- "What's the color palette of [URL]?"
Step-by-Step Process
Phase 1: Crawl & Extract
- Fetch the target site using WebFetch tool
- Identify key elements:
- Navigation structure - Hero section patterns - Card/grid layouts - Color usage - Typography hierarchy - Spacing patterns - Interactive elements
- Extract design tokens:
`` Colors: primary, secondary, accent, neutral scale Typography: font families, size scale, weights Spacing: base unit, scale (4px, 8px, 16px, etc.) Borders: radius values, border widths Shadows: elevation levels ``
Phase 2: Document for LLM Context
Create markdown files that can be fed back to LLMs:
- COMPONENTS.md - Document each component:
```markdown ## ComponentName
Purpose: What it does Props/Variants: Configuration options Code: ``tsx // Component code here ` ``
- STYLES.md - Design token documentation:
```markdown ## Color Palette
| Name |
Value |
Usage |
| primary |
#8b5cf6 |
CTAs, links |
## Typography Scale
| Name |
Size |
Weight |
Line Height |
| h1 |
48px |
700 |
1.2 |
```
- LLM-CONTEXT.md - High-level architecture summary
Phase 3: Remix & Create
When building a new site inspired by another:
- Identify transferable patterns:
- Layout structures - Component architecture - Animation/interaction patterns - Responsive breakpoints
- Define the new concept:
- Purpose and audience - Unique value proposition - Content structure - Brand personality
- Adapt the design:
- New color palette aligned with concept - Adjusted typography for tone - Modified components for use case - Original content and imagery
Project Structure
When creating a new site, use this structure:
project-name/
├── app/ # Next.js App Router pages
│ ├── page.tsx # Home page
│ ├── layout.tsx # Root layout
│ └── [feature]/ # Feature pages
├── components/
│ ├── cards/ # Card components
│ ├── hero/ # Hero sections
│ ├── navigation/ # Nav, Footer
│ ├── sections/ # Page sections
│ └── ui/ # Base UI components
├── lib/
│ └── data.ts # Data and types
├── public/
│ └── images/ # Static assets
├── styles/
│ └── globals.css # Global styles + Tailwind
└── docs/ # Documentation
├── COMPONENTS.md
├── STYLES.md
└── LLM-CONTEXT.md
Code Templates
See TEMPLATES.md for:
- Next.js 14 setup with Tailwind
- Common component patterns
- Animation utilities
- Dark mode implementation
Best Practices
- Always document as you build - Future LLMs need context
- Extract reusable patterns - Don't copy blindly, understand why
- Respect originality - Remix, don't plagiarize
- Test responsiveness - Mobile-first approach
- Optimize for performance - Use Next.js Image, lazy loading
Image Generation Integration
When the design needs custom images:
- Plan image requirements - List all needed images with descriptions
- Use AI image generation - MuleRouter, Midjourney, DALL-E
- Optimize images - Compress and format appropriately
- Integrate with Next.js Image - Use fill, priority, sizes props
Deployment Checklist