ux-design

Generates section-by-section UX spec skeletons for screens, flows, or HUDs from concept docs and CDDs.

3|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill ux-design-negentropy-laby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-design
Source: https://github.com/Negentropy-Laby/Constitution-Driven-Development/tree/main/.agents/skills/ux-design
Command: npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill ux-design-negentropy-laby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guided, section-by-section UX spec authoring for a screen, flow, or HUD. It supports both game projects (player journey, HUD, game screens) and product projects (user flows, CLI interaction, API consumer journey). It reads concept doc and relevant CDDs for context-aware design guidance.

Core Features & Use Cases

  • Domain-aware UX spec generation for game and product projects.
  • Context gathering from concept docs, CDDs, and user journey notes.
  • Retrofit and skeleton creation for new or existing specs.
  • Section-by-section authoring workflow with review gates and approvals.

Quick Start

Invoke the ux-design skill with a screen or flow name to generate a guided UX spec skeleton for that target.

Frequently Asked Questions about ux-design

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

FAQPage Schema
How do I write a UX specification for a game HUD from scratch?

To write a UX specification for a game HUD, you need a guided, section-by-section authoring workflow that reads concept docs and relevant CDDs. This approach generates structured documentation tailored to player journeys and game screens.

What is the best way to document user flows for product design?

Documenting user flows for product design requires context-aware integration of user journey notes into structured specs. A guided authoring process captures UI requirements and generates section-by-section documentation for screens and flows.

Can I use a single UX spec workflow for both game and product projects?

Yes, you can use a single UX spec workflow for both game and product projects through domain detection. It adapts design guidance to support game player journeys, HUDs, and product user flows like CLI interactions or API consumer journeys.

How does domain detection work when generating UX documentation?

Domain detection works by reading concept docs and relevant CDDs to differentiate between game and product contexts. This context gathering tailors the design guidance and structures the generated UX specification specifically for the detected domain.

Do I need a concept doc to start section-by-section UX spec authoring?

Yes, providing a concept doc and relevant CDDs is necessary for context-aware design guidance. These documents supply the foundational UI requirements and domain context needed to accurately tailor the generated UX specification.