AGENT SKILL

design-wizard

Interactive design wizard that guides through a complete frontend design process with discovery, aesthetic selection, and code generation. Use for creating distinctive, production-ready UI.

License 许可
MIT
最近更新
2026-11-10
Stars
★ 1
Forks
0

01 前言 Front Matter

description
Interactive design wizard that guides through a complete frontend design process with discovery, aesthetic selection, and code generation. Use for creating distinctive, production-ready UI.
allowed-tools
[ "Read", "Write", "AskUserQuestion", "Skill" ]

02 资源文件 4

03 SKILL.md 正文

Design Wizard

An interactive wizard that guides you through creating distinctive, production-ready frontend designs.

Purpose

This skill orchestrates the complete design process:

  1. Discovery - Understanding what to build
  2. Research - Analyzing trends and inspiration
  3. Direction - Selecting aesthetic approach
  4. Colors - Choosing color palette
  5. Typography - Selecting fonts
  6. Implementation - Generating code
  7. Review - Validating quality

Process Overview

┌─────────────┐     ┌─────────────┐     ┌─────────────┐
│  Discovery  │ ──▶ │  Research   │ ──▶ │  Moodboard  │
└─────────────┘     └─────────────┘     └─────────────┘
                                              │
┌─────────────┐     ┌─────────────┐           ▼
│   Review    │ ◀── │  Generate   │ ◀── ┌─────────────┐
└─────────────┘     └─────────────┘     │ Colors/Type │
                                        └─────────────┘

Step 1: Discovery Questions

Ask the user about their project:

Question 1: What are you building?

  • Landing page
  • Dashboard
  • Blog/Content site
  • E-commerce
  • Portfolio
  • SaaS application
  • Mobile app UI
  • Other (describe)

Question 2: Project context

  • Personal project
  • Startup/new product
  • Established brand
  • Client work
  • Redesign of existing

Question 3: Target audience

  • Developers/technical
  • Business professionals
  • Creative/designers
  • General consumers
  • Young/Gen-Z
  • Luxury/premium market

Question 4: Background style preference

  • Pure white (#ffffff)
  • Off-white/warm (#faf8f5)
  • Light tinted (use lightest palette color)
  • Dark/moody (use darkest palette color)
  • Let me decide based on aesthetic

Question 5: Any specific inspiration?

  • URLs to analyze
  • Aesthetic keywords
  • Specific requirements
  • Skip (use trend research)

Step 2: Research Phase

Based on answers, optionally invoke:

  • trend-researcher - For current design trends
  • inspiration-analyzer - For specific URLs provided

Step 3: Moodboard Phase

Invoke moodboard-creator to:

  • Synthesize research into direction
  • Present options to user
  • Iterate until approved

Step 4: Aesthetic Selection

Based on discovery and moodboard, suggest aesthetics from catalog:

For Modern/Premium:

  • Dark & Premium - Sophisticated, high-contrast
  • Glassmorphism - Layered, translucent
  • Bento Grid - Structured, modular

For Bold/Distinctive:

  • Neobrutalism - Raw, impactful
  • Statement Hero - Typography-focused
  • Editorial - Magazine-inspired

For Minimal/Clean:

  • Scandinavian - Warm minimal
  • Swiss Typography - Grid-based clarity
  • Single-Page Focus - Concentrated impact

For Playful/Creative:

  • Y2K/Cyber - Retro-futuristic
  • Memphis - Colorful geometric
  • Kawaii - Cute, rounded

See references/aesthetics-catalog.md for full catalog.

Step 5: Color & Typography

Invoke specialized skills:

  • color-curator - Browse Coolors or select from fallbacks
  • typography-selector - Browse Google Fonts or use pairings

Map selections to Tailwind config.

Step 6: Code Generation

Generate single HTML file with:

Structure

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>[Project Title]</title>

  <!-- Google Fonts -->
  <link rel="preconnect" href="https://fonts.googleapis.com">
  <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
  <link href="https://fonts.googleapis.com/css2?family=[Font1]&family=[Font2]&display=swap" rel="stylesheet">

  <!-- Tailwind CDN -->
  <script src="https://cdn.tailwindcss.com"></script>
  <script>
    tailwind.config = {
      theme: {
        extend: {
          colors: {
            // Custom colors from palette
          },
          fontFamily: {
            // Custom fonts
          }
        }
      }
    }
  </script>

  <style>
    /* Custom animations */
    /* Focus states */
    /* Reduced motion */
  </style>
</head>
<body>
  <!-- Semantic HTML structure -->
</body>
</html>

Requirements

  • Mobile-responsive (Tailwind breakpoints)
  • Semantic HTML (header, main, nav, footer, section)
  • Accessible (ARIA labels, focus states, contrast)
  • No Lorem ipsum (realistic placeholder content)
  • Animations respect prefers-reduced-motion
  • Keyboard navigable

Step 7: Self-Review

Check against references/anti-patterns.md:

  • [ ] No hero badges/pills
  • [ ] No generic fonts (Inter, Roboto, Arial)
  • [ ] No purple/blue gradients on white
  • [ ] No generic blob shapes
  • [ ] No excessive rounded corners
  • [ ] No predictable templates

Check references/design-principles.md:

  • [ ] Clear visual hierarchy
  • [ ] Proper alignment
  • [ ] Sufficient contrast
  • [ ] Appropriate white space
  • [ ] Consistent spacing

Check references/accessibility-guidelines.md:

  • [ ] 4.5:1 contrast ratio for text
  • [ ] Visible focus states
  • [ ] Semantic HTML
  • [ ] Alt text for images
  • [ ] Form labels

Output Format

Deliver:

  1. Final HTML file
  2. Brief explanation of design choices
  3. List of fonts used (for reference)
  4. Color palette summary

Iteration

If user requests changes:

  1. Note specific feedback
  2. Make targeted adjustments
  3. Re-run self-review
  4. Present updated version

Maximum 3 major iterations, then consolidate feedback.

References

  • references/design-principles.md - Core design principles with code
  • references/aesthetics-catalog.md - Full aesthetic catalog
  • references/anti-patterns.md - What NOT to do
  • references/accessibility-guidelines.md - WCAG compliance

04 同仓库更多 Skills

YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

vercel-sandbox

Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

slack

Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

electron

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

dogfood

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.

★ 1