What problem does it solve?
It prevents inconsistent frontend outputs by enforcing PMOS’s Ant Design family baseline across design, UI schema, implementation handoff, and final page delivery.
Core Features & Use Cases
- Governed Ant Design Family baseline: Ensures the output follows the required layering (Ant Design X host + Ant Design foundational layer) rather than generic Ant Design pages.
- UI schema and implementation-ready delivery: Produces route/layout shell, functional links, and page contracts suitable for downstream frontend work.
- Pro adapter boundary handling: Forces explicit decisions when Ant Design Pro/Pro Components are involved (reference only, isolated adapter layer, or blocked by compatibility).
- State and verification expectations: Includes loading/empty/error/permission states and aligns outputs with browser-verification before user review.
Quick Start
Use this skill to generate a DESIGN.md and ui-schema for a new PMOS frontend page that must follow the Ant Design family baseline, including the correct Ant Design X host and Pro isolation decision.