gsd-ui-phase

Generate UI-SPEC.md design contracts with phase objectives and verification steps.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/MINT-IA/MINT --skill gsd-ui-phase-mint-ia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-ui-phase
Source: https://github.com/MINT-IA/MINT/tree/main/.claude/skills/gsd-ui-phase
Command: npx skills add https://github.com/MINT-IA/MINT --skill gsd-ui-phase-mint-ia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates a formal UI design contract (UI-SPEC.md) to remove ambiguity between design and engineering during frontend phase planning, ensuring phase goals, research findings, and verification gates are captured consistently.

Core Features & Use Cases

  • Orchestrates the end-to-end UI phase workflow: validate inputs, run UI research, and verify the resulting UI-SPEC with an automated checker.
  • Produces a standardized UI-SPEC.md containing phase objectives, component specifications, accessibility guidelines, acceptance criteria, and verification steps for handoffs.
  • Use Case: During iterative frontend development, create a phase-specific UI contract to align product, design, and engineering before implementation starts.

Quick Start

Create a UI design contract for the next frontend phase by running the gsd-ui-phase skill with the desired phase number or omit the argument to auto-detect the next unplanned 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 create a UI design contract for frontend development phases?

A UI design contract standardizes phase objectives, component specifications, accessibility guidelines, and verification steps to remove ambiguity between design and engineering before frontend implementation starts.

What is a UI-SPEC.md file and what should it include for frontend handoffs?

A UI-SPEC.md file is a structured UI design contract that includes phase objectives, research findings, component specs, accessibility criteria, and verification steps for frontend development handoffs.

How do I validate phase scope and run UI research for iterative frontend projects?

You validate phase scope and orchestrate UI research by applying a UI design contract workflow that validates inputs, runs UI research, and verifies results with an automated checker across frontend phases.

Can I automatically detect the next unplanned phase when generating a UI design contract?

Yes, you can auto-detect the next unplanned phase by running the workflow without specifying a phase number, or you can explicitly provide a desired phase number to generate the UI-SPEC.md.

Does generating a UI design contract work for multi-phase frontend projects?

Yes, generating a UI design contract is designed for multi-phase frontend projects to validate phase scope, orchestrate UI research, and enforce verification gates across design and engineering handoffs.

How are verification gates enforced in a UI design contract workflow?

Verification gates are enforced by integrating researcher and checker workflows that validate the UI-SPEC.md file, ensuring phase goals, research findings, and acceptance criteria are met before handoff.