// Produces a Galactic UX/UI spec from a solution brief. Use when you need concrete flows, interface states, trust cues, copy direction, and progressive disclosure for power users and aspiring users.
Applies Galactic engineering rules for work in the galactic-ide repository. Use when implementing, reviewing, or refactoring repo code and you need the canonical standards for testing, versioning, React/Tailwind conventions, toasts, storage, OS-aware logic, and git-service boundaries.
Applies the client-side subset of Galactic engineering rules. Use when writing, reviewing, or modifying React/TypeScript renderer code and you want the UI conventions without loading the broader repo framing.
Packages an approved Galactic UX/UI design into a design-ready handoff for future engineering skills. Use when solution framing, design, and validation are complete and you need one final artifact with behavior, states, acceptance criteria, instrumentation, and open risks.
Critiques a Galactic UX/UI spec before engineering handoff. Use when you need a structured validation pass focused on clarity, trust, compatibility risk, edge cases, and whether the design actually serves Galactic's target users.
Analyzes an existing Galactic feature or workflow to find the highest-value product gaps. Use when you need a structured gap analysis grounded in real users, current implementation, and clear in-scope versus out-of-scope pain.
Turns a Galactic gap analysis into a scoped product brief. Use when you need a decision-oriented solution framing artifact with scope, constraints, success metrics, and design questions before UX/UI work starts.
| name | galactic-ux-ui-feature-design |
| description | Produces a Galactic UX/UI spec from a solution brief. Use when you need concrete flows, interface states, trust cues, copy direction, and progressive disclosure for power users and aspiring users. |
| allowed-tools | Read, Grep, Glob |
Use this skill to turn a Galactic solution brief into a design-ready experience specification.
Read these first:
../references/galactic-product-foundation.mdREADME.mdSolution BriefInspect the current feature surfaces in the repo before proposing changes so the design fits Galactic's product reality.
Design for progressive disclosure:
Prefer outcome language over infrastructure language. Expose technical detail only when it helps the user act.
Return exactly this Markdown structure:
# UX/UI Spec
## Entry Points
- Primary entry point:
- Supporting entry points:
- Trigger moment:
## Primary Flow
1. Step 1:
2. Step 2:
3. Step 3:
## Audience Paths
- Power-user path:
- Aspiring-user path:
## Screen And State Inventory
| Surface or State | Purpose | Key Elements |
| --- | --- | --- |
| | | |
## Interaction Rules
- What the user can do:
- What the system must confirm:
- What stays hidden by default:
## Copy And Trust Cues
- Headline or framing guidance:
- Mechanism explanation:
- Compatibility reassurance:
- Trust/provenance cue:
## Error, Empty, Loading, And Success States
- Loading:
- Empty:
- Error:
- Success:
- Blocked or degraded:
## Open Design Risks
- Risk 1:
- Risk 2:
- Risk 3:
Hand off to $galactic-design-validation.