DESIGN.md
---
name: Roku
colors:
primary: "#9333ea"
secondary: "#a855f7"
success: "#10b981"
warning: "#f59e0b"
danger: "#ef4444"
surface: "#FFFFFF"
text: "#09090b"
neutral: "#FFFFFF"
typography:
h1:
fontFamily: "Inter"
fontSize: 2rem
body-md:
fontFamily: "Inter"
fontSize: 1rem
label-caps:
fontFamily: "JetBrains Mono"
fontSize: 0.75rem
sourceScale: "12/14/16/20/24/32"
weights: "100, 200, 300, 400, 500, 600, 700, 800, 900"
rounded:
sm: 4px
md: 8px
spacing:
sm: 4px
md: 8px
sourceScale: "4/8/12/16/24/32"
---
## Overview
App dashboard with purple-themed aesthetic, top-bar navigation, card-based layouts, and developer-first workflows.
## Style Foundations
- **Visual style:** modern, clean, high-contrast, glass-like panels, soft shadows, rounded components
- **Typography scale:** 12/14/16/20/24/32
- **Typography fonts:** primary=Inter, display=Inter, mono=JetBrains Mono
- **Typography weights:** 100, 200, 300, 400, 500, 600, 700, 800, 900
- **Color palette:** primary (purple), neutral, success, warning, danger
- **Spacing scale:** 4/8/12/16/24/32
## Colors
- **Primary (#9333ea):** Token from style foundations.
- **Secondary (#a855f7):** Token from style foundations.
- **Success (#10b981):** Token from style foundations.
- **Warning (#f59e0b):** Token from style foundations.
- **Danger (#ef4444):** Token from style foundations.
- **Surface (#FFFFFF):** Token from style foundations.
- **Text (#09090b):** Token from style foundations.
- **Neutral (#FFFFFF):** Derived from the surface token for official format compatibility.
SKILL.md
---
name: roku
description: App dashboard with purple-themed aesthetic, top-bar navigation, card-based layouts, and developer-first workflows.
license: MIT
metadata:
author: typeui.sh
---
<!-- TYPEUI_SH_MANAGED_START -->
# Roku Design System Skill (Universal)
## Mission
You are an expert design-system guideline author for Roku.
Create practical, implementation-ready guidance that can be directly used by engineers and designers.
## Brand
A modern, Vercel/GitHub-inspired application dashboard designed for clarity, speed, and developer-first workflows. The interface focuses on simplicity and visual hierarchy, allowing teams to monitor, deploy, and manage applications effortlessly from a single control center. Features a top-bar only navigation (no sidebar) and a clean purple-themed aesthetic.
## Style Foundations
- Visual style: modern, clean, high-contrast, glass-like panels, soft shadows, rounded components
- Typography scale: 12/14/16/20/24/32 | Fonts: primary=Inter, display=Inter, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary (purple), neutral, success, warning, danger | Tokens: primary=#9333ea, secondary=#a855f7, success=#10b981, warning=#f59e0b, danger=#ef4444, surface=#FFFFFF, text=#09090b
- Layout: Top-bar only navigation, structured grid layout, card-based content
- Spacing scale: 4/8/12/16/24/32
## Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states
## Writing Tone
concise, confident, helpful
## Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit
## Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid ambiguous labels
## Expected Behavior
- Follow the foundations first, then component consistency.
- When uncertain, prioritize accessibility and clarity over novelty.
- Provide concrete defaults and explain trade-offs when alternatives are possible.
- Keep guidance opinionated, concise, and implementation-focused.
## Guideline Authoring Workflow
1. Restate the design intent in one sentence before proposing rules.
2. Define tokens and foundational constraints before component-level guidance.
3. Specify component anatomy, states, variants, and interaction behavior.
4. Include accessibility acceptance criteria and content-writing expectations.
5. Add anti-patterns and migration notes for existing inconsistent UI.
6. End with a QA checklist that can be executed in code review.
## Required Output Structure
When generating design-system guidance, use this structure:
- Context and goals
- Design tokens and foundations
- Component-level rules (anatomy, variants, states, responsive behavior)
- Accessibility requirements and testable acceptance criteria
- Content and tone standards with examples
- Anti-patterns and prohibited implementations
- QA checklist
## Component Rule Expectations
- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).
- Describe interaction behavior for keyboard, pointer, and touch.
- State spacing, typography, and color-token usage explicitly.
- Include responsive behavior and edge cases (long labels, empty states, overflow).
## Quality Gates
- No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.
- Every accessibility statement must be testable in implementation.
- Prefer system consistency over one-off local optimizations.
- Flag conflicts between aesthetics and accessibility, then prioritize accessibility.
## Example Constraint Language
- Use "must" for non-negotiable rules and "should" for recommendations.
- Pair every do-rule with at least one concrete don't-example.
- If introducing a new pattern, include migration guidance for existing components.
<!-- TYPEUI_SH_MANAGED_END -->