gsd-ui-phase

Orchestrate UI research and verification to generate a validated UI-SPEC.md.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/onelee85/my-skills --skill gsd-ui-phase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-ui-phase
Source: https://github.com/onelee85/my-skills/tree/main/gsd-ui-phase
Command: npx skills add https://github.com/onelee85/my-skills --skill gsd-ui-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a complete frontend UI design contract (UI-SPEC.md) by orchestrating UI research and verification steps, reducing back-and-forth and ensuring a consistent specification baseline.

Core Features & Use Cases

  • Orchestrates gsd-ui-researcher and gsd-ui-checker to produce a validated UI specification.
  • Validates inputs and gates at each stage (research, drafting, verification) for multiple frontend phases.
  • Use Case: A design team wants a rigorously reviewed UI-SPEC.md for phase 1, including references and validation gates.

Quick Start

Invoke gsd-ui-phase with the optional phase number to generate the UI-SPEC.md for the given frontend phase.

Frequently Asked Questions about gsd-ui-phase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a UI specification for a frontend phase workflow?

To generate a UI specification for a frontend phase, invoke the orchestrator with an optional phase number to coordinate research, drafting, and verification into a validated UI-SPEC.md baseline.

What is a UI design contract and how does orchestration validate it?

A UI design contract is a UI-SPEC.md file defining frontend requirements. Orchestration validates it by chaining validation gates across research, drafting, and verification stages to preserve workflow integrity.

Can I automate UI research and verification steps for multiple frontend phases?

Yes, you can automate UI research and verification for multiple frontend phases by orchestrating subagents and applying validation gates at each stage to ensure a consistent specification baseline.

Do I need specific dependencies to orchestrate frontend UI contracts end-to-end?

No specific dependencies are required to orchestrate frontend UI contracts. The workflow validates inputs, orchestrates subagents, and accesses references internally to preserve end-to-end execution gates.

What's the best way to reduce back-and-forth when creating a UI-SPEC.md?

The best way to reduce back-and-forth when creating a UI-SPEC.md is to orchestrate UI research and verification steps together, applying validation gates to ensure a consistent specification baseline.