gsd-ui-phase

Generate a UI-SPEC.md design contract for a frontend phase.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-ui-phase-trucol270
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-ui-phase
Source: https://github.com/TruCol270/salty-pickle/tree/main/.claude-skills/gsd-ui-phase
Command: npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-ui-phase-trucol270

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a UI design contract (UI-SPEC.md) for frontend phases to codify design decisions and reduce ambiguity in the early design process.

Core Features & Use Cases

  • Orchestrated UI research: coordinates research tasks to inform UI specifications and decisions.
  • Verification & validation: ensures the produced UI-SPEC.md aligns with design goals and technical constraints.
  • Rapid spec generation: outputs a complete UI-SPEC.md ready for design and engineering review.

Quick Start

Generate a UI design contract (UI-SPEC.md) for the specified 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 design contract for a frontend phase?

To generate a UI design contract, this skill orchestrates UI research and verification steps to produce a compliant UI-SPEC.md file that codifies frontend design decisions and reduces ambiguity.

What is a UI-SPEC.md file used for in frontend workflow automation?

A UI-SPEC.md file codifies design decisions for a frontend phase, serving as a formal contract that reduces early design ambiguity and ensures produced specifications align with technical constraints.

Can I use this to coordinate UI research and design verification before engineering review?

Yes, the skill orchestrates coordinated UI research and validation tasks to inform specifications, ensuring the final UI design contract meets frontend-phase requirements and is ready for review.

What's the best way to codify frontend design decisions to reduce ambiguity?

The best way is generating a structured UI-SPEC.md contract that documents and validates decisions through orchestrated research and verification, ensuring alignment with both design goals and technical constraints.

Does this skill require any specific dependencies or workflow files to produce a UI-SPEC?

No specific dependencies are required to run this skill. It coordinates existing workflow files and references internally to ensure the produced UI-SPEC.md meets frontend-phase requirements.

Why does my frontend UI design process lack consistency across phases?

Your process lacks consistency because design decisions are not codified. Generating a UI-SPEC.md contract standardizes and validates these decisions, reducing ambiguity across different frontend phases.