gsd-ui-phase

You can automate UI design contract generation by using a skill that orchestrates sub-skills for research and verification, producing a standardized UI-SPEC.md file for frontend phases. It streamlines the design process by managing flow control from validation to completion.

A UI design contract is a standardized UI specification document generated for frontend phases. You need it when your team requires a consistent design contract to orchestrate UI research and verification across multiple development phases.

To generate a UI specification for a specific frontend phase, you run the automation skill with your phase identifier, such as 'phase-1', as the argument. The tool then orchestrates UI research and verification to output the design contract.

Yes, you need access to workflow and reference files for context loading to generate UI specifications. The automation process requires these files to properly orchestrate sub-skills and manage the flow control for design contract generation.

The best way to manage UI research and verification is to use an orchestration skill that automates the flow control between specialized researcher and checker components. This approach ensures a validated UI design contract is generated for each frontend phase.

A key limitation is that automating phase management requires explicit phase arguments and access to workflow reference files for context loading. Without these inputs, the orchestration flow cannot properly execute the UI research and verification steps.