frontend-design-ui-ux

Translate UX concepts into design specs, tokens, and component briefs for Next.js and React handoff.

13|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/ulpi-io/browse --skill frontend-design-ui-ux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-design-ui-ux
Source: https://github.com/ulpi-io/browse/tree/main/.agents/skills/frontend-design-ui-ux
Command: npx skills add https://github.com/ulpi-io/browse --skill frontend-design-ui-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Bridges the gap between UX design and engineering by translating concepts into implementation-ready design specifications, component briefs with TypeScript interfaces, user flows, design tokens, and clear handoff guidance.

Core Features & Use Cases

  • Design artifacts and specifications to guide engineers through feature implementation.
  • Component briefs with TypeScript interfaces to ensure precise data contracts.
  • User flow documentation and system definitions to maintain consistency across products.
  • Design tokens and scalable system definitions for design-to-code handoff.
  • Clear handoff instructions for Next.js, React, and web app teams.

Quick Start

Provide a design brief for a new feature and this skill will generate a complete design specification, token definitions, and component briefs for engineering handoff.

Frequently Asked Questions about frontend-design-ui-ux

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

FAQPage Schema
How do I translate UX concepts into implementation-ready design specifications for React?

To translate UX concepts into implementation-ready design specifications, provide a design brief to generate component briefs with TypeScript interfaces, user flow docs, and design tokens tailored for React and Next.js engineering handoff.

What is the best way to generate design tokens for engineering handoff?

Generating design tokens for engineering handoff involves translating UX concepts into scalable system definitions. This process outputs precise token definitions and component briefs to ensure design-to-code consistency across web app teams.

How do I create component briefs with TypeScript interfaces for Next.js?

Creating component briefs with TypeScript interfaces for Next.js requires translating UX designs into precise data contracts. This ensures engineers receive clear handoff instructions with accessibility and responsive guidelines included.

Can I use this for both feature design and design system creation?

Yes, you can use this for both feature design and design system creation. It applies UX concepts to generate user flow documentation, system definitions, and design tokens suitable for scaling across products.

Do I need a specific framework to implement these design specifications?

You need to work within Next.js or React stacks to implement these design specifications. The generated artifacts include TypeScript interfaces and handoff instructions specifically tailored for these web app frameworks.

Why does engineering handoff fail without clear user flow documentation?

Engineering handoff fails without clear user flow documentation because developers lack the context to implement features accurately. Translating UX concepts into structured user flows and component briefs ensures precise data contracts and consistent system definitions.