gsd-ui-phase

To generate a UI specification for a frontend phase, use a tool that orchestrates UI research and verification to produce a production-ready design contract saved as UI-SPEC.md in your project context.

A UI design contract is a specification document that lists components, interactions, accessibility requirements, and verification checks for a frontend phase. You need one to reduce ambiguity between designers and engineers during handoffs.

Yes, you can automatically verify UI requirements by running a checker tool that validates the resulting specification and preserves workflow gates while reading and writing project context files.

To ensure phase-level continuity across multiple frontend phases, use a project-context aware tool that auto-detects the current phase, reads existing workflow files, and writes updated specifications to maintain continuity.

UI spec generation works without manual handoffs by orchestrating research to collect requirements and verification to validate designs, automatically capturing and storing the results in the project context.

A limitation of auto-detecting the frontend phase is that the tool requires readable project workflow files; when the phase is omitted and context files are missing, it cannot determine the correct phase to generate the UI-SPEC.md.