Design Spec
DesignDesign Spec is an Agent Skill for design published in the GongShichen/LuminaCode repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Convert a PRD into a durable UX design document with states, flows, copy, and accessibility.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/GongShichen/LuminaCode/blob/HEAD/.Lumina/TEAM/product-development/ux-design/skills/design-spec/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/design-spec, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Write the design as <project_root>/UX_DESIGN.md unless Team Leader gives a different path.
Size guidance:
- Small CLI, TUI, single-screen, or narrow workflow: 60-140 lines.
- Medium multi-screen feature: 120-220 lines.
- Large product surface: expand only when the PRD or existing system requires it.
- Prefer compact tables and bullet decisions over long prose. Do not include every possible state if it is not relevant.
Inputs:
- PRD path and summary.
- Platform constraints and existing UI conventions.
- Known backend/data contract assumptions.
Required sections:
-
Design objective
- What user workflow this design optimizes.
- What is intentionally not designed.
-
Information architecture
- Primary regions, navigation/routing, hierarchy, and reading order.
- Responsive or terminal/window-size behavior when relevant.
-
User flows
- Happy path.
- Empty/loading/error flow.
- Retry/recovery flow.
- Keyboard and accessibility flow.
-
Screen/state inventory
- Initial state.
- Loading state.
- Empty state.
- Populated state.
- Validation error.
- Network/server error.
- Success confirmation.
-
Interaction and copy
- Labels, buttons, status text, empty/error messages.
- Focus behavior and live-region/announcement behavior.
-
Data needs
- Fields consumed from backend/API/storage.
- Formatting decisions for dates, status, counts, names, and validation.
- What the design expects but does not define as backend internals.
-
Accessibility and constraints
- Semantic structure, labels, keyboard access, focus, color contrast, reduced motion.
- Platform constraints and no-go decisions.
-
Handoff notes
- Frontend implications.
- Backend/API assumptions that must be confirmed through
INTERFACE_CONTRACT.md.
Quality bar:
- Do not produce frontend or backend technical plans.
- Do not let visual polish override repeated-use ergonomics.
- Do not invent backend internals; identify contract needs instead.
- Make missing PRD details explicit as assumptions or questions.