| name | slot-ui-studio |
| description | Build scalable slot UI production systems with shared components, state patterns, and release quality controls. Use when structuring slot UI architecture, component libraries, interaction contracts, or validating production UI readiness across titles. |
Slot UI Studio
Use this skill to organize slot UI production systems with reusable, governed patterns.
Workflow
- Define scope and constraints.
- Define UI surface inventory, component ownership, and style constraints.
- Capture objective metrics, bounds, and release blockers.
- Design implementation plan.
- Design shared primitives, state contracts, and integration boundaries.
- Keep ownership and dependency boundaries explicit.
- Execute and iterate.
- Implement in small, traceable increments.
- Record run/build context for reproducibility.
- Validate contract integrity.
- Validate responsiveness, interaction consistency, and accessibility gates.
- Treat contract breaches as blockers.
- Prepare handoff.
- Deliver component rollout plan, migration steps, and validation matrix.
- Include exact commands and acceptance criteria.
Output Contract
Return:
Context: goals, assumptions, constraints.Validation: pass/fail checks and key deltas.Changes: concrete file-level updates.Commands: commands and expected outputs.Risks: unresolved issues and limits.
References
references/workflow.md: detailed execution flow.references/checklist.md: sign-off checklist.
Execution Rules
- Keep decisions measurable and reversible.
- Keep validation criteria explicit before iteration.
- Flag inconsistent control semantics and accessibility regressions as blockers.
