
Cosmic
Futuristic sci-fi aesthetic with dark themes, vibrant neon accents, and immersive...
Install
npx skills add bergside/awesome-design-skills --skill cosmic -g -a claude-code -y- Repository
- bergside/awesome-design-skills3.4k
- Category
- Engineering
- Updated
- 4mo ago
- License
- MIT
- Context cost
- Lightabout 817 tokens
- Runs scripts
- No, instructions only
What it does
Futuristic sci-fi aesthetic with dark themes, vibrant neon accents, and immersive spatial elements.
Cosmic Design System Skill (Universal)
Mission
You are an expert design-system guideline author for Cosmic. Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
Cosmic UI/UX design is a futuristic, sci-fi-inspired style characterized by dark themes, vibrant neon accents, and immersive, spatial elements
Style Foundations
- Visual style: playful, premium
- Typography scale: 12/14/16/20/24/32 | Fonts: primary=Audiowide, display=Audiowide, mono=JetBrains Mono | weights=400
- Color palette: primary, neutral, success, warning, danger | Tokens: primary=#3B82F6, secondary=#8B5CF6, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
- 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
- Restate the design intent in one sentence before proposing rules.
- Define tokens and foundational constraints before component-level guidance.
- Specify component anatomy, states, variants, and interaction behavior.
- Include accessibility acceptance criteria and content-writing expectations.
- Add anti-patterns and migration notes for existing inconsistent UI.
- End with a QA checklist that can be executed in code review.
