ui-forge

Generate HTML UI screen variations and reusable component catalogs from declarative schemas.

1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/dmedina-dev/dev-forge --skill ui-forge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-forge
Source: https://github.com/dmedina-dev/dev-forge/tree/main/plugins/forge-ui-forge/skills/ui-forge
Command: npx skills add https://github.com/dmedina-dev/dev-forge --skill ui-forge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

Designers and developers often need to explore multiple UI variations and build reusable components without altering production code, leading to slow iteration and fragmented design assets.

Core Features & Use Cases

  • Iterative Prototyping: Generates multiple HTML screen variations from a declarative schema stored in .ui-forge/.
  • Component Catalog: Reuses and promotes UI pieces into a growing registry of versioned components.
  • Data Scenarios: Creates realistic mock data and edge‑case scenarios for thorough validation.
  • Annotation Overlay: Lets users annotate screens, extract component ideas, and capture feedback as JSON.
  • Hands‑off Handoff: Produces framework‑agnostic screen specs and component specifications ready for downstream implementation.

Quick Start

Ask ui-forge to prototype a new dashboard screen for the sales analytics project.

Frequently Asked Questions about ui-forge

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

FAQPage Schema
How do I prototype UI screens with reusable components for frontend handoff?

To prototype UI screens with reusable components, you generate multiple HTML screen variations from a declarative schema stored in a `.ui-forge` directory. This approach produces framework-agnostic screen specs and component specifications ready for downstream implementation.

What is the best way to generate mock data and edge-case scenarios for UI prototypes?

The best way to generate mock data for UI prototypes is to use a tool that creates realistic data scenarios alongside your HTML screen variations. This allows thorough validation of interface states without altering production code.

Do I need external dependencies or specific frameworks to prototype HTML UI variations?

You do not need external dependencies to prototype HTML UI variations. The process requires a project root with a `.ui-forge` directory, bash for bootstrap, Tailwind token defaults, and standard HTML/JS.

Can I annotate UI mockups and extract component ideas during design exploration?

Yes, you can annotate UI mockups during design exploration by applying an annotation overlay. This lets you capture feedback and extract component ideas directly from the screen, saving them as JSON.

How does component reuse work when iterating on UI screen prototypes?

Component reuse works by promoting UI pieces into a growing registry of versioned components. As you iterate on screen prototypes, these cataloged components are applied across multiple HTML variations to maintain consistency.

What are the limitations of using standard HTML and bash for UI screen prototyping?

Using standard HTML, JS, and bash for UI screen prototyping limits you to Tailwind token defaults and a local `.ui-forge` directory schema. It focuses on generating static variations rather than running a live coded application environment.