ferrox-ui-phase

Create a UI-SPEC.md design contract before frontend implementation begins.

21|9|Updated Jul 21, 2026
One-click install
npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-ui-phase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ferrox-ui-phase
Source: https://github.com/FerroxLabs/ferrox-factory/tree/main/skills/ferrox-ui-phase
Command: npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-ui-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents frontend work from drifting into vague implementation by forcing a clear UI design contract before code is built. It helps teams avoid rework, inconsistent visuals, and unverified design decisions.

Core Features & Use Cases

  • UI Contract Creation: Produces a UI-SPEC.md that defines the phase’s design requirements and constraints.
  • Research and Verification Workflow: Coordinates UI research and validation through ferrox-ui-researcher and ferrox-ui-checker.
  • Frontend Phase Planning: Supports phase-based work where design must be pinned down before implementation begins.
  • Use Case: A product team starting a new frontend feature uses this Skill to lock the interface spec before any development starts.

Quick Start

Ask the AI to create a UI design contract for your frontend phase and generate the UI-SPEC.md from the current project context.

Frequently Asked Questions about ferrox-ui-phase

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

FAQPage Schema
How do I lock down frontend UI design requirements before implementation starts?

A UI design contract pins down interface requirements before build execution starts. It coordinates UI research and validation workflows to produce a verified UI-SPEC.md artifact, preventing frontend work from drifting into vague implementation and avoiding rework.

What is a UI-SPEC.md artifact and when do I need it for phase-based frontend work?

A UI-SPEC.md artifact defines a frontend phase’s design requirements and constraints. You need it for phase-based frontend work requiring design research, specification, and validation before build execution to prevent unverified design decisions and rework.

How to create a UI design contract for a frontend phase from existing project context?

To create a UI design contract, orchestrate UI research and checker workflows against your current project context. This validates interface requirements and generates a verified UI-SPEC.md artifact that blocks implementation from starting until the design is pinned down.

Does phase planning for frontend work require UI research and verification before build?

Yes, phase planning for frontend work requires UI research and verification before build. Orchestrating UI research and checker workflows produces a validated UI-SPEC.md design contract, ensuring interface requirements are pinned down and preventing unverified design decisions.

Why does frontend implementation drift into inconsistent visuals and rework?

Frontend implementation drifts into inconsistent visuals and rework when there is no clear UI design contract before code is built. Forcing a verified UI-SPEC.md artifact with pinned down interface requirements prevents vague implementation and unverified design decisions.

Can I start frontend implementation before the UI-SPEC.md design contract is verified?

No, you cannot start frontend implementation before the UI-SPEC.md design contract is verified. The workflow explicitly prevents implementation from starting until interface requirements are pinned down through UI research and checker validation.