Forge

Prototype UI components, page flows, API mocks, and backend slices.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Dinxeshh/agent-skills --skill forge-dinxeshh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Forge
Source: https://github.com/Dinxeshh/agent-skills/tree/main/skills/forge
Command: npx skills add https://github.com/Dinxeshh/agent-skills --skill forge-dinxeshh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Forge eliminates the gap between idea and runnable proof by quickly delivering UI components, page flows, API mocks, backend PoCs, or thin full-stack slices so teams can validate hypotheses without waiting for production-ready builds.

Core Features & Use Cases

  • UI and Flow Prototyping: Build isolated components, state patterns, and micro page journeys with mock data that demonstrate the happy path for Spark, Vision, or Muse inputs.
  • API Mocking & Backend PoCs: Ship MSW handlers, inline mock fetches, or minimal Express/Fastify servers to unblock frontend/backfill experimentation while documenting fake assumptions.
  • Full-stack Slice Delivery: Combine UI, backend mock/PoC, and decision notes to hand off a survival-ready artifact for Builder, Artisan, Showcase, or Muse, complete with recorded friction in .agents/forge.md.

Quick Start

Command Forge to build a Throwaway UI component with mock API data to prove the new sign-up journey.

Frequently Asked Questions about Forge

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

FAQPage Schema
How do I build a UI prototype with mock API data to validate a product hypothesis?

To build a UI prototype with mock API data, you generate isolated components, page flows, and MSW handlers that demonstrate the happy path, documenting the hypothesis and mock strategy to validate direction before full production builds.

What is the best way to create API mocks and backend PoCs for frontend experimentation?

The best way to create API mocks and backend PoCs is shipping MSW handlers, inline mock fetches, or minimal Express/Fastify servers to unblock frontend experimentation while recording fake assumptions and known debt in decision notes.

Can I deliver a full-stack slice that combines UI components and backend mocks?

Yes, you can deliver a full-stack slice by combining UI components, backend mock or PoC servers, and decision notes into a survival-ready artifact for downstream handoff, complete with recorded friction tracked in a workflow markdown file.

Does rapid prototyping work for testing micro page journeys and state patterns?

Rapid prototyping works for testing micro page journeys and state patterns by building isolated UI components with mock data that demonstrate the happy path, allowing teams to validate product direction quickly before committing to production-ready builds.

What should I document when creating a throwaway prototype to test a sign-up flow?

When creating a throwaway prototype to test a sign-up flow, you must document the hypothesis, mock strategy, prototype status, known debt, and next decision per the workflow, ensuring the artifact is survival-ready for downstream handoff.