// 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.
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.
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.
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-handoff |
| description | 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. |
| allowed-tools | Read, Grep, Glob |
Use this skill to consolidate approved product and design decisions into a clean handoff artifact for future engineering work.
Read these first:
../references/galactic-product-foundation.mdREADME.mdSolution BriefUX/UI SpecDesign Validation ReportIf the validation report does not explicitly pass the design, stop and say the handoff is blocked pending revision.
Return exactly this Markdown structure:
# Design-Ready Handoff
## Final User Goal
- Primary user:
- User goal:
- Why this matters:
## Approved Behavior
- Behavior 1:
- Behavior 2:
- Behavior 3:
## State Matrix
| State | What The User Sees | Expected Outcome |
| --- | --- | --- |
| | | |
## Acceptance Criteria
- Criterion 1:
- Criterion 2:
- Criterion 3:
## Instrumentation Needs
- Event or metric:
- Why it matters:
## Dependencies
- Dependency:
## Open Risks
- Risk:
## Future Engineer Skill Inputs
- What future engineering work should preserve:
- What engineering should not decide alone:
This artifact is the final output of the non-engineering suite.