design-flow

The design-flow skill converts an approved product specification into verifiable, customer-facing design assets and screen-level acceptance criteria, preventing UI build from starting with vague or non-implementable requirements.

Generating high-fidelity HTML/CSS handoff from a Figma design is best handled by the design-flow skill, which performs reference intake and outputs build-ready design packages so engineers can reproduce screens without guessing.

To define screen-level acceptance criteria for UI-heavy workflows, the design-flow skill produces DESIGN.md and visual system artifacts that ensure verifiable, build-ready targets for every key surface before coding begins.

Yes, you can use reference intake to translate extracted patterns into concrete interaction and structure decisions by applying the design-flow skill, which processes delegated visual direction to define platform behaviors.

Yes, you need an approved PRD or SPEC before starting the UI design-gate process, because the design-flow skill requires an approved product specification to convert into verifiable design artifacts and acceptance criteria.

UI build starts with vague requirements when lacking verifiable design targets; prevent it by using the design-flow skill to establish a design-gate that outputs screen acceptance criteria and high-fidelity HTML/CSS packages before coding.