// 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.
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.
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.
Creates a Galactic-specific user insight brief for a feature, workflow, or product area. Use when you need to identify the target user, JTBD, current workaround, trust requirements, and adoption blockers before gap analysis or design.
| name | galactic-design-validation |
| description | 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. |
| allowed-tools | Read, Grep, Glob |
Use this skill to pressure-test a Galactic design before it becomes handoff material.
Read these first:
../references/galactic-product-foundation.mdREADME.mdSolution BriefUX/UI SpecInspect relevant implementation only when needed to verify compatibility or surface mismatch.
Return exactly this Markdown structure:
# Design Validation Report
## Findings
| Severity | Finding | Why It Matters |
| --- | --- | --- |
| Blocking / Major / Minor | | |
## Clarity Risks
- Risk:
## Trust Risks
- Risk:
## Tool And Workflow Compatibility Risks
- Risk:
## Edge Cases
- Case:
## Accessibility And Comprehension Checks
- Check:
## Required Revisions
- Revision:
## Decision
- Pass or revise:
- Reason:
If the decision is Revise, hand back to $galactic-ux-ui-feature-design. If the decision is Pass, hand off to $galactic-design-handoff.