cosmic

Define neon-themed UI components with WCAG 2.2 AA accessibility and token-based styling.

Updated May 13, 2026
One-click install
npx skills add https://github.com/superpollo02/awesome-design-skill --skill cosmic-superpollo02
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cosmic
Source: https://github.com/superpollo02/awesome-design-skill/tree/main/skills/cosmic
Command: npx skills add https://github.com/superpollo02/awesome-design-skill --skill cosmic-superpollo02

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cosmic helps you consistently implement a futuristic sci-fi design system without drifting into inaccessible spacing, low-contrast colors, or unclear component states.

Core Features & Use Cases

  • Sci-fi visual foundations: Locks typography, neon color tokens, spacing rhythm, and rounded corners into a shared baseline.
  • Accessible interaction guidance: Enforces WCAG 2.2 AA expectations with keyboard-first behavior and visible focus states.
  • Implementation-ready rules: Provides do/don’t patterns and quality gates so agents and teams generate components that are coherent and testable.

Quick Start

Instruct your AI to generate Cosmic-compliant UI rules for your app’s core components, using the provided tokens, accessibility constraints, and explicit interaction states.

Frequently Asked Questions about cosmic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a neon-themed design system that meets WCAG 2.2 AA accessibility standards?

To build an accessible neon-themed design system, apply token-first guidance for neon colors, typography, and spacing that enforces WCAG 2.2 AA contrast requirements. This framework provides explicit state handling and keyboard-first interaction rules to ensure your futuristic UI remains fully accessible.

How do I generate consistent UI component states for sci-fi interfaces?

You generate consistent sci-fi UI component states by applying token-first guidance with explicit interaction handling for elements like buttons, inputs, and cards. This approach provides testable quality gates and do/don't patterns so your interactive interfaces maintain coherent state behavior.

Can I use design tokens to manage keyboard-first interaction behavior in my product UI?

Yes, you can use design tokens to enforce keyboard-first interaction behavior by applying token-first guidance that defines visible focus states and explicit component handling. This ensures your interactive product UI meets accessibility expectations through testable quality gates.

What's the best way to prevent color contrast drift when implementing futuristic UI components?

The best way to prevent contrast drift in futuristic UI components is to lock neon color tokens and typography into a shared baseline using design-tokenized styling. This enforces WCAG 2.2 AA satisfaction and provides testable quality gates to verify component coherence.

Does this sci-fi design system approach work for navigation and card components?

Yes, this sci-fi design system approach works for navigation and card components by providing design-tokenized styling and explicit state handling for interactive interfaces. It delivers consistent neon-themed implementations across core product component families.

Why do my neon UI components fail accessibility checks despite having distinct visual states?

Neon UI components fail accessibility checks when they lack WCAG 2.2 AA contrast compliance and keyboard-first behavior despite distinct visual states. Applying token-first guidance with explicit state handling and visible focus states resolves these testable quality gate failures.