A universal AI skill that generates UI design mockups and helps reconstruct generated UI screenshots into HTML/CSS. Prefer the runtime's built-in image generation when available; use GPT Image 2 via the ZenMux API for scripted local outputs.

• Generates high-quality UI mockups from natural language descriptions
• Locks navigation/sidebar consistency across multiple screens using a reference image
• Uses proven prompt techniques (analogy-style or inventory-style) for better design quality
• Handles GPT Image 2's edit_image API quirks automatically (serial execution, retries)
• Guides HTML reconstruction with asset strategy, browser screenshot comparison, and background-removal rules for logos and illustrations

• An AI agent that supports the skills protocol (Claude Code, Cursor, etc.)
• For scripted image generation: a ZenMux API key — set as ZENMUX_API_KEY env var, in .env.local, or in ~/.config/see/api_key
• Python 3 (auto-installs google-genai on first run)

npx skills add oil-oil/draw-ui

Or clone manually:

mkdir -p ~/.claude/skills
git clone https://github.com/oil-oil/draw-ui ~/.claude/skills/draw-ui

Trigger by saying anything like:

帮我设计一个 Dashboard 页面
Design a user profile screen
出图，产品详情页

The agent will ask you a few questions first (what the page does, whether you have a reference screenshot, consistency requirements), then generate.

# No reference image
scripts/ask_draw.sh --type wide --name "dashboard" --prompt "..."

# With reference image (locks sidebar/nav consistency)
scripts/ask_draw.sh \
  --frame /path/to/sidebar-reference.png \
  --type wide \
  --name "dashboard" \
  --prompt "..."

Reference image strategy

The reference image constrains what AI will copy. If your screenshot has existing content in the main area, AI will mimic that layout — limiting creative freedom.

Best practice: use a "clean frame" — a screenshot with only the sidebar/nav visible and the content area blank. This lets AI keep your chrome consistent while designing the content area freely.

Prompt writing

Don't write layout specs (pixels, columns, padding). Instead, describe the business using one of two approaches:

• Analogy — "Like reading the sheet music behind a hit song. Think Notion's calm meets a music producer's notes." → best for creative quality
• Inventory — "The page shows: user name, 30-day trend chart, active campaigns list with status badges." → most reliable for accuracy

Always use real example data instead of placeholders. "2.3M views" produces a far more realistic output than "show view count".

HTML reconstruction

When turning a generated mockup or screenshot into HTML/CSS, split the work into code and assets:

• Build layout, cards, buttons, text, filters, and ordinary line icons with HTML/CSS/SVG.
• Generate standalone image assets for brand logos, empty-state illustrations, glassy/3D visuals, complex gradients, and other hard-to-code visual details. Use crops only as references for image-to-image redraw, not as final assets unless the source is already high-resolution and background-clean.
• Do not mix large illustrations, logos, and small icons in the same sprite sheet. Generate large illustration assets separately.
• For vendor logo rows, dark wordmarks, and small dark icons, generate a large pure-white source image and remove the white background conservatively. This avoids green fringing and protects thin strokes.
• For colorful illustrations and product visuals, use green-screen or real transparent output when available; white-background keying can damage white cards and highlights.
• If an icon sprite sheet is needed, make it machine-cuttable: pure white background, exact 4x4 grid, no borders, no labels, no shadows, no overlap, and each icon centered with wide padding.

This keeps the HTML clean while preserving the visual parts that image generation is best at.

MIT