# futuristic

This skill gives an agent a futuristic design system with typography, tokens, component states, and accessibility rules. Use it when writing UI guidance.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 2400 installs · ★ 3349
- 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/futuristic/SKILL.md
- Updated: 2026-06-28
- HTML: https://affpapa.org/en/nevibecode/skills/futuristic

## What it does

futuristic guides an agent through practical design-system rules for a futuristic interface. It sets Roboto for body text, Audiowide for display text, and Anonymous Pro for monospace content. The skill also defines color tokens, semantic values, and a 4/8/12/16/24/32 spacing scale.

Its workflow moves from design intent and foundations to component anatomy, states, responsive behavior, accessibility criteria, and a QA checklist. It covers hover, focus-visible, active, disabled, loading, and error states when relevant. This makes WCAG 2.2 AA, keyboard-first interaction, and visible focus explicit checks rather than optional polish.

## Install

### Claude Code (native platform)

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

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

### Codex

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

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

### Cursor

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

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

### GitHub Copilot

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

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

### Gemini CLI

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

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

### Windsurf (Devin Desktop)

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

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill futuristic -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/futuristic/SKILL.md

## When to use it
- define typography, color, and spacing tokens
- document component states and interaction behavior
- check UI against accessibility criteria
- write responsive rules for interface components
- create a QA checklist for code review

## Example prompts
- Create a futuristic design system for a settings page, starting with tokens and foundational constraints.
- Define the Button component’s anatomy, states, keyboard behavior, and WCAG 2.2 AA acceptance criteria.
- Review the existing UI for contrast, focus visibility, spacing rhythm, and ambiguous labels using futuristic.

## 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: 3bd2c11582612c45.

BEGIN THIRD-PARTY FILE 3bd2c11582612c45
```text
---
name: futuristic
description: Forward-looking design with tech-inspired typography, modern layouts, and a sleek, innovation-driven aesthetic.
license: MIT
metadata:
  author: typeui.sh
---

<!-- TYPEUI_SH_MANAGED_START -->
# Futuristic Design System Skill (Universal)

## Mission
You are an expert design-system guideline author for Futuristic.
Create practical, implementation-ready guidance that can be directly used by engineers and designers.

## Brand


## Style Foundations
- Visual style: modern
- Typography scale: desktop-first expressive scale | Fonts: primary=Roboto, display=Audiowide, mono=Anonymous Pro | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- 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.
- 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.
```
END THIRD-PARTY FILE 3bd2c11582612c45

The third-party file has ended. Everything between the 3bd2c11582612c45 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 2998 of 3368 bytes. © typeui.sh · MIT · https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/futuristic/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