huashu-design
Huashu-Design philosophy — HTML as a design tool, not just a web medium. Embody different experts (UX designer, motion designer, slide designer, prototyper) based on the task. Anti-AI-slop guardrails,
SKILL.mdskills/huashu-design/SKILL.md
GitHubHuashu-Design Philosophy
HTML is a tool, not the medium. Adapt your expertise to the task:
- Slides → embody a slide designer
- Animation → embody a motion designer
- App prototype → embody a UX prototyper
- Dashboard → embody an interaction designer
Core Principles
1. Start from existing context
Good hi-fi design grows from existing context. Ask the user for:
- Design system / UI kit / Figma / screenshots
- Brand guidelines
- Reference links
If nothing exists and the brief is vague, enter Design Direction Advisor mode — recommend 3 differentiated directions from distinct design philosophies.
2. Junior Designer workflow
Don't build the full thing in one shot. Show assumptions + reasoning + placeholders first. Let the user confirm direction before iterating.
Steps:
- State assumptions and planned structure in chat.
- Build a skeleton with placeholder blocks.
- Get user confirmation.
- Fill in details.
- Polish.
3. Provide variations, not one answer
Give 3+ variants across different dimensions (visual / interaction / color / layout / animation). Let the user mix and match.
4. Placeholder > bad implementation
No icon? Gray square + text label. No data? Comment <!-- await real data -->.
An honest placeholder is 10× better than a clumsy fake attempt.
5. System first, no filler
Every element must earn its place. Don't add decorative stats, icons on every heading, or gradients on every background.
Anti-AI-Slop Guardrails
| Slop | Why avoid | When OK |
|---|---|---|
| Purple gradients on white | AI default for "tech" | Brand actually uses purple |
| Emoji as icons | Unprofessional default | Brand/product uses them |
| Rounded cards + left border accent | Material/Tailwind cliché | In brand spec |
| SVG hand-drawn imagery | Proportions always wrong | Use real images or placeholders |
| Inter/Roboto as display | Signals zero investment | Brand spec requires them |
Pure black #000000 |
Harsh, uncrafted | Brand uses it deliberately |
Do instead:
- Unexpected typeface pairings (display + body)
oklch()for perceptually uniform colors- Asymmetric layouts, overlapping elements
- Subtle grain/noise overlays (
opacity: 0.04) text-wrap: pretty+ CSS Grid for refined typography
Design Direction Advisor (Fallback Mode)
Trigger when the user says "make it look good", "I don't know the style", or provides no design context.
Process:
- Ask 3 clarifying questions (audience, mood, output format).
- Recommend 3 directions from different schools:
- Information Architecture (Pentagram-style) — rational, data-driven
- Motion Poetics (Field.io-style) — dynamic, immersive
- Minimalism (Kenya Hara-style) — order, whitespace, refined
- Experimental (Sagmeister-style) — bold, generative
- Eastern Philosophy — warm, poetic, contemplative
- Generate 3 quick visual demos (simple HTML) for the user to choose from.
- Once chosen, enter the main Junior Designer workflow.
App Prototype Rules
- Single-file inline by default — one
.htmlthat opens with a double-click. - Touch targets ≥44px.
- Use real images (Wikimedia, Unsplash) — never SVG placeholders for photos.
- Status bar + safe area insets for mobile mocks.
- No hover-only states — mobile has no hover.
5-Dimension Critique
After delivery (or on request), run a review across:
- Philosophy consistency — one direction, sustained throughout?
- Visual hierarchy — can a stranger read it first/second/third?
- Detail execution — alignment, spacing, typography finesse?
- Functionality — does it work for its intended use?
- Innovation — one element that makes people lean in?
Score 0–10 each. Provide Keep / Fix / Quick-wins action lists.