// 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.
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.
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-solution-framing |
| description | 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. |
| allowed-tools | Read, Grep, Glob |
Use this skill to turn a diagnosed gap into a clear product bet for design.
Read these first:
../references/galactic-product-foundation.mdREADME.mdGap AnalysisInspect relevant code only as needed to confirm terminology, current behavior, and feature boundaries.
Return exactly this Markdown structure:
# Solution Brief
## Problem Statement
- Primary gap:
- Primary user:
- Why this matters:
## Product Bet
- Core bet:
- User outcome:
- Why Galactic can credibly solve this:
## In Scope
- Included behaviors:
- Included surfaces:
## Out Of Scope
- Explicitly excluded problems:
- Deferred ideas:
## Constraints
- Product constraints:
- Trust or proof constraints:
- Compatibility constraints:
## Success Metrics
- User-facing success signal:
- Product success signal:
- What would count as failure:
## Questions For Design
- Open question 1:
- Open question 2:
- Open question 3:
Hand off to $galactic-ux-ui-feature-design.