moodboard-creator
Create visual moodboards from collected inspiration with iterative refinement. Use after trend research or website analysis to synthesize design direction before implementation.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- description
- Create visual moodboards from collected inspiration with iterative refinement. Use after trend research or website analysis to synthesize design direction before implementation.
- allowed-tools
- [ "Read", "Write", "AskUserQuestion", "mcp__claude-in-chrome__computer" ]
03 SKILL.md 正文
Moodboard Creator
Create and refine visual moodboards that synthesize design inspiration into a cohesive direction.
Purpose
Before jumping to code, create a moodboard that:
- Consolidates inspiration into clear direction
- Extracts colors, typography, and patterns
- Allows iterative refinement with user feedback
- Establishes design language before implementation
Workflow
Step 1: Gather Sources
Collect inspiration from:
- Trend research screenshots
- Analyzed websites
- User-provided URLs or images
- Dribbble/Behance shots
For each source, note:
- URL or source
- Key visual elements to extract
- Why it's relevant
Step 2: Extract Elements
From collected sources, extract:
Colors
- Primary colors (1-2)
- Secondary/accent colors (1-2)
- Background colors
- Text colors
- Note hex codes
Typography
- Headline font style (name if identifiable)
- Body font style
- Weight and size observations
- Spacing/tracking notes
UI Patterns
- Navigation styles
- Card treatments
- Button designs
- Section layouts
- Decorative elements
Mood/Atmosphere
- Keywords describing the feel
- Emotional response
- Brand personality traits
Step 3: Create Moodboard Document
Generate a structured moodboard:
## Moodboard v1 - [Project Name]
### Inspiration Sources
| Source | Key Takeaway |
|--------|--------------|
| [URL/Name 1] | [What we're taking from it] |
| [URL/Name 2] | [What we're taking from it] |
| [URL/Name 3] | [What we're taking from it] |
### Color Direction
Primary: #[hex] - [color name] Secondary: #[hex] - [color name] Accent: #[hex] - [color name] Background: #[hex] - [color name] Text: #[hex] - [color name]
### Typography Direction
- **Headlines**: [Font/style] - [weight, size notes]
- **Body**: [Font/style] - [readability notes]
- **Accents**: [Any special type treatments]
### UI Patterns to Incorporate
1. **[Pattern Name]**: [Description of how to use it]
2. **[Pattern Name]**: [Description of how to use it]
3. **[Pattern Name]**: [Description of how to use it]
### Layout Approach
- Grid system: [e.g., 12-column, bento, asymmetric]
- Spacing philosophy: [tight, airy, mixed]
- Section structure: [full-width, contained, alternating]
### Mood Keywords
[Keyword 1] | [Keyword 2] | [Keyword 3] | [Keyword 4]
### Visual References
[Descriptions of key screenshots/references]
### What to Avoid
- [Anti-pattern from inspiration that doesn't fit]
- [Style that would clash]
Step 4: User Review
Present moodboard to user and ask:
- Does this direction feel right?
- Any colors to adjust?
- Typography preferences?
- Patterns to add or remove?
- Keywords that don't fit?
Step 5: Iterate
Based on feedback:
- Update moodboard version number
- Adjust elements per feedback
- Add new inspirations if needed
- Remove rejected elements
- Present updated version
Continue until user approves.
Step 6: Finalize
When approved, create final moodboard summary:
## FINAL Moodboard - [Project Name]
### Approved Direction
[Summary of the design direction]
### Color Palette (Final)
| Role | Hex | Usage |
|------|-----|-------|
| Primary | #xxx | Buttons, links, accents |
| Secondary | #xxx | Hover states, icons |
| Background | #xxx | Page background |
| Surface | #xxx | Cards, modals |
| Text Primary | #xxx | Headings, body |
| Text Secondary | #xxx | Captions, muted |
### Typography (Final)
- Headlines: [Font Name] - [weight]
- Body: [Font Name] - [weight]
- Monospace: [Font Name] (if needed)
### Key Patterns
1. [Pattern with implementation notes]
2. [Pattern with implementation notes]
### Ready for Implementation
[Checkbox] Colors defined
[Checkbox] Fonts selected
[Checkbox] Layout approach set
[Checkbox] User approved
Iteration Best Practices
- Keep each version documented
- Make focused changes (don't overhaul everything)
- Explain changes clearly
- Show before/after for major shifts
- Maximum 3-4 iterations (then synthesize feedback)
Fallback Mode
If no visual sources available:
- Ask user to describe desired mood/feel
- Reference aesthetic categories from design-wizard
- Suggest color palettes from color-curator fallbacks
- Use typography pairings from typography-selector fallbacks
- Create text-based moodboard from descriptions
Output
Final moodboard should directly inform:
- Tailwind config colors
- Google Fonts selection
- Component styling decisions
- Layout structure
04 同仓库更多 Skills
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
internal-comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
algorithmic-art
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
theme-factory
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.