Han Design Gives AI Agents a Chinese-Style Web Toolkit That Knows When to Stop
Most AI-generated "Chinese-style" web design defaults to beige backgrounds, brush-script titles, and red stamps — a visual cliché that collapses thousands of years of aesthetics into three tokens. Han Design gives both AI Agents and human developers a structured, scoped alternative that can drop into a React or Vue project without forcing a full design-system rewrite, while its cultural-context rules prevent the kind of lazy symbol-pasting that makes generated pages look like a souvenir shop.
Han Design packages 16 visual themes — seven dynasty-inspired and nine scene-based — into a set of CSS tokens, decorative components, and Agent-readable judgment rules. The project deliberately avoids becoming yet another component library; it supplies static structures like seal buttons, scroll cards, and window-lattice borders, while leaving interactive widget behavior to the host application's existing components. A scoped CSS entry point keeps its styles from leaking into the rest of a project, so a marketing page's ink-wash treatment won't crawl through an entire backend dashboard. The Skill layer encodes cultural guardrails: it distinguishes historical restoration from contemporary inspiration, flags symbols like dragons and religious imagery that shouldn't be pasted casually, and prompts the Agent to consider period, region, and medium before generating a design.
The project's core insight is that AI design tools need encoded cultural judgment, not just more CSS. Without rules that distinguish a real seal face from a red square, or a historical motif from a modern decorative association, an Agent reliably produces the same cliché page every time.
Scoping is treated as a first-class integration concern, not an afterthought. The 7-pixel horizontal-scroll bug on mobile that came from a hidden global box-sizing dependency illustrates how easily a "drop-in" stylesheet breaks a real project — and why the scoped boundary matters more than the themes themselves.
Han Design explicitly refuses to become a component library, which is a pragmatic choice: the maintenance burden of accessible, keyboard-navigable interactive widgets would overwhelm a solo project, and most teams already have a component system they won't abandon for a decorative layer.