# cosmic

Applies a futuristic sci-fi design system with dark themes and neon accents. Generates accessible component specifications backed by WCAG 2.2 AA.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 2400 installs · ★ 3361
- Author: typeui.sh
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/cosmic/SKILL.md
- Updated: 2026-06-28
- HTML: https://affpapa.org/en/nevibecode/skills/cosmic

## What it does

The cosmic skill configures the agent to write design system guidelines under a futuristic sci-fi aesthetic. It defines strict foundations, pairing Audiowide for primary and display typography with JetBrains Mono at weight 400. Sizing follows a 12/14/16/20/24/32 type scale and a 4 to 32 spacing scale.

Every component rule generated through this skill must account for interaction states, including default, hover, focus-visible, active, disabled, loading, and error. Palette tokens include primary (`#3B82F6`), secondary (`#8B5CF6`), success, warning, danger, surface, and text. Visual style strictly defers to accessibility: whenever aesthetics clash with WCAG 2.2 AA contrast thresholds, the agent prioritizes accessibility.

Guideline authoring follows a six-step workflow that concludes with a QA checklist for code review. Because every rule requires concrete token anchors and paired anti-patterns, the system prevents vague styling advice during frontend implementation.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill cosmic -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/cosmic/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/cosmic/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill cosmic -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/cosmic/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill cosmic -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/cosmic/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install bergside/awesome-design-skills cosmic
```

2. **Manually: put the files in place**
- File: `.github/skills/cosmic/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill cosmic -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/bergside/awesome-design-skills --path skills/cosmic
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/cosmic/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill cosmic -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/cosmic/SKILL.md

## When to use it
- Generate design system guidelines for a sci-fi UI theme
- Define component states and variants with explicit tokens
- Enforce WCAG 2.2 AA accessibility criteria during UI reviews
- Document anti-patterns and migration paths for inconsistent components

## Example prompts
- Create a button component specification using cosmic design tokens and focus states
- Write guidelines for a modal dialog using the Audiowide font and spacing scale
- Generate a QA checklist for accessible form inputs according to cosmic rules

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 5844e62028092094.

BEGIN THIRD-PARTY FILE 5844e62028092094
```text
---
name: cosmic
description: Futuristic sci-fi aesthetic with dark themes, vibrant neon accents, and immersive spatial elements.
license: MIT
metadata:
  author: typeui.sh
---

<!-- TYPEUI_SH_MANAGED_START -->
# 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
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.
```
END THIRD-PARTY FILE 5844e62028092094

The third-party file has ended. Everything between the 5844e62028092094 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2738 of 3447 bytes. © typeui.sh · MIT · https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/cosmic/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md