Gather user design preferences before building UI. Use when: starting a project with visual interface (Web App, Mobile, Browser Extension). Triggers: "design preferences", "visual style", "choose theme", "design step".
/plugin marketplace add timequity/vibe-coder/plugin install vibe-coder@vibe-coderThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Gather user preferences for visual design before building. Creates docs/DESIGN.md with selected choices.
Applies to project types with UI:
Skip for:
question: "Насколько важен дизайн для этого проекта?"
header: "Design"
options:
- label: "Профессиональный"
description: "Уникальный стиль, впечатляет пользователей"
- label: "Функциональный"
description: "Чистый и понятный, без лишнего"
- label: "Минимальный MVP"
description: "Работает -> достаточно, стиль потом"
If "Минимальный MVP" -> Skip remaining questions, use defaults.
question: "Какой визуальный стиль ближе?"
header: "Style"
options:
- label: "Minimalist"
description: "Много пространства, чистые линии"
- label: "Bold & Modern"
description: "Яркие акценты, современный"
- label: "Soft & Friendly"
description: "Округлые формы, мягкие тона"
- label: "Dark & Professional"
description: "Тёмная тема, серьёзный"
- label: "Colorful & Playful"
description: "Яркие цвета, игривый"
Based on aesthetic direction, offer matching themes from theme-factory:
| Direction | Matching Themes |
|---|---|
| Minimalist | Modern Minimalist, Arctic Frost |
| Bold & Modern | Tech Innovation, Sunset Boulevard |
| Soft & Friendly | Desert Rose, Botanical Garden |
| Dark & Professional | Ocean Depths, Midnight Galaxy |
| Colorful & Playful | Golden Hour, Sunset Boulevard |
question: "Какая цветовая схема?"
header: "Theme"
options:
- label: "{Theme 1}"
description: "{Primary colors}"
- label: "{Theme 2}"
description: "{Primary colors}"
- label: "Custom"
description: "Опишу свои цвета"
If "Custom" -> Ask follow-up: "Опиши желаемые цвета или бренд"
question: "Какой стиль текста?"
header: "Fonts"
options:
- label: "Sans-Serif (современный)"
description: "Чистый, технологичный"
- label: "Serif (классический)"
description: "Традиционный, солидный"
- label: "Mixed (заголовки/текст)"
description: "Display + body fonts"
question: "Сколько анимации?"
header: "Motion"
options:
- label: "Subtle"
description: "Только hover эффекты"
- label: "Moderate"
description: "Переходы, hover, scroll"
- label: "Rich"
description: "Page transitions, stagger, parallax"
- label: "None"
description: "Без анимации"
# Design Specification
## Priority
{Professional / Functional / MVP}
## Aesthetic Direction
{Selected style}
## Theme
**Name:** {theme name}
**Colors:**
- Primary: {hex}
- Secondary: {hex}
- Accent: {hex}
- Background: {hex}
- Text: {hex}
**Fonts:**
- Headers: {font name}
- Body: {font name}
## Motion
**Level:** {Subtle / Moderate / Rich / None}
**Patterns:**
- Hover: {yes/no}
- Page transitions: {yes/no}
- Scroll animations: {yes/no}
- Loading states: {yes/no}
## Implementation Notes
- Use CSS variables for theme colors
- Follow frontend-design skill principles
- Avoid generic fonts (Inter, Roboto, Arial)
- {Additional notes based on choices}
If user chooses "Минимальный MVP":
Place this step between Phase 1 (Idea Validation) and Phase 2 (Project Setup):
Phase 1: Idea Validation
-> Step 1.6: Create PRD
Phase 1.5: Design Preferences <-- NEW
-> Ask design questions
-> Create DESIGN.md
Phase 2: Project Setup
-> Read PRD.md + DESIGN.md
-> Apply theme to templates
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.