B-End Neutral-Style Standardized UI Generation

Problem: B-end UIs Often Miss the Mark

Many admin consoles and internal tools do not lack pages; they lack a calm, low-decoration, reusable visual baseline. Stakeholders may reference Tencent Cloud, Volcano Engine, or AntD v5, but actual screens can drift into marketing colors, card overload, and inconsistent button states, forcing repeated CSS and component checks.

How It Works: From Style Constraints to Spec Output

The skill targets B-end backend UIs and generates interface solutions aligned with the neutral design language of Tencent Cloud, Volcano Engine, and AntD v5. Its main outputs include:

• Design tokens: shared color, spacing, radius, shadow, and other base variables;
• Grid rules: layouts suited to common admin-screen information density;
• Component specs: forms, tables, dialogs, side navigation, and other B-end UI patterns;
• Front-end CSS variables: ready to enter a style system, with light / dark mode support.

This is useful for fixing the visual baseline first, then letting front-end implementation follow the same variable contract.

Boundaries and Notes

The skill is closer to a standardized UI specification than a full product architecture, interaction prototype, or brand-exploration service. For complex dashboards, mobile experiences, or strong brand styles, add explicit design constraints.