aped-ux

Scaffold a React preview app and generate a validated UX spec from a PRD.

2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/yabafre/aped-claude --skill aped-ux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aped-ux
Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-ux
Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you transform a PRD into a real, interactive React UX prototype without skipping the user validation gate—so downstream architecture and planning don’t drift from product truth.

Core Features & Use Cases

  • PRD-grounded UX synthesis (no lorem ipsum): Assembles design DNA, normalizes layouts and navigation, and fills every screen with real content derived from the PRD.
  • Interactive preview app as the source of truth: Scaffolds a Vite + React preview that stays intact for React Grab inspection and downstream consumption.
  • Validated, accessible UX delivery: Enforces loading/empty/error/success/disabled states, responsive behavior, dark-mode tokenization, and accessibility requirements before producing the UX spec.

Quick Start

Run aped-ux after your PRD is ready, then review each screen in the local preview and choose Continue when everything is signed off.

Frequently Asked Questions about aped-ux

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

FAQPage Schema
How do I turn a PRD into a validated UX prototype?

To turn a PRD into a validated UX prototype, this Skill scaffolds a React preview app and implements screen flows using real PRD-derived content, strictly avoiding placeholder text. It outputs a UX spec, screen inventory, and component files after mandatory user review gating.

Can I generate a React UX prototype with real content instead of placeholder text?

Yes, generating a React UX prototype with real content is supported through strict no lorem ipsum rules. The process assembles design DNA, normalizes layouts, and fills every screen with actual content derived directly from your existing PRD.

How do I ensure my UX prototype meets accessibility and responsive requirements?

To ensure accessibility and responsive requirements are met, the UX prototype delivery enforces loading, empty, error, success, and disabled states. It also applies responsive behavior and dark-mode tokenization before finalizing the UX spec.

What is the best way to prepare a UX spec for downstream architecture planning?

The best way to prepare a UX spec for architecture planning is to scaffold an interactive Vite and React preview app as the source of truth. This validated prototype stays intact for inspection and ensures downstream development does not drift from product truth.

Does the UX prototype generation process require manual user review?

Yes, the UX prototype generation process requires mandatory manual user review gating. You must review each screen in the local preview and explicitly choose to continue only when all screens are signed off.

What states must a complete UX prototype include before generating a UX spec?

A complete UX prototype must include loading, empty, error, success, and disabled states before generating the UX spec. It also mandates responsive behavior and dark-mode tokenization to ensure a fully accessible and validated design.