futuristic skill
✓ VerifiedGenerates implementation-ready design system guidelines focusing on modern typography, semantic tokens, and accessibility standards.
- GitHub stars
- 3,629
- Files
- 2
- Last commit
- Jun 28, 2026
- License
- MIT
- Allowed tools
- —
What does the futuristic skill do?
futuristic generates implementation-ready design system guidelines focusing on modern typography, semantic tokens, and accessibility standards.
Summary generated from the skill's SKILL.md.
About the futuristic skill
Creating implementation-ready design system guidelines for tech-inspired interfaces is what this skill enables. Developers and designers use it to generate structured documentation that covers typography scales, semantic tokens, and accessibility standards. It produces comprehensive guides that include component anatomy, interaction states, and responsive behavior, ensuring that engineering teams have clear instructions for building modern layouts.
An agent should load this skill when a project requires a cohesive visual language based on specific foundations like the Roboto, Audiowide, and Anonymous Pro font families. The output follows a strict workflow that moves from high-level design intent to granular component rules and QA checklists. It prioritizes WCAG 2.2 AA compliance and semantic tokens over raw hex values to ensure consistency across a digital product. By providing concrete defaults and explicit interaction states, it helps prevent common UI issues like low contrast or inconsistent spacing rhythms.
What an agent can do with it
- 1Generate component documentationCreate detailed rules for UI components including their anatomy, variants, and required states like hover or loading.
- 2Establish design tokensDefine a foundational system of semantic tokens for colors, spacing, and typography to ensure visual consistency.
- 3Ensure accessibility complianceDevelop testable accessibility acceptance criteria that follow WCAG 2.2 AA standards.
- 4Create code review checklistsProduce a quality assurance checklist that developers can use during the code review process.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the futuristic skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the futuristic skill in Claude Code
~/.claude/skills/futuristic/SKILL.md
$ npx degit bergside/awesome-design-skills/skills/futuristic ~/.claude/skills/futuristicInstall the futuristic skill in Claude Code (project)
.claude/skills/futuristic/SKILL.md
$ npx degit bergside/awesome-design-skills/skills/futuristic .claude/skills/futuristicInstall the futuristic skill in Codex
~/.agents/skills/futuristic/SKILL.md
$ npx degit bergside/awesome-design-skills/skills/futuristic ~/.agents/skills/futuristicInstall the futuristic skill in Gemini CLI
~/.gemini/skills/futuristic/SKILL.md
$ npx degit bergside/awesome-design-skills/skills/futuristic ~/.gemini/skills/futuristicInstall the futuristic skill in Claude.ai
npx degit bergside/awesome-design-skills/skills/futuristic futuristic && zip -r futuristic.zip futuristic # claude.ai → Customize → Skills → + → Create skill → Upload a skill → futuristic.zip
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work · What to fix for more points
- Source repository linked and reachablebergside/awesome-design-skills/skills/futuristic is public and reachablegithub.com/bergside/awesome-design-skills/tree/HEAD/skills/f ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-06-28github.com/bergside/awesome-design-skills/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/bergside/awesome-design-skills/blob/HEAD/skills/f ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/bergside/awesome-design-skills/blob/HEAD/skills/f ↗Pass
- SKILL.md follows the Agent Skills formatthe description does not say when to use the skillgithub.com/bergside/awesome-design-skills/blob/HEAD/skills/f ↗Finding
SKILL.md
View on GitHubFuturistic 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
- 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.
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.
Files in this skill
2futuristic skill questions
How do I install the futuristic skill in Claude Code?
Run npx degit bergside/awesome-design-skills/skills/futuristic ~/.claude/skills/futuristic. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the futuristic skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What fonts are used in the Futuristic design system?
The system uses Roboto for primary text, Audiowide for display elements, and Anonymous Pro for monospaced content.
What accessibility standards does this skill follow?
The design system adheres to WCAG 2.2 AA standards and emphasizes keyboard-first interactions and visible focus states.
What is the required structure for generated design guidance?
Guidance must include context, design tokens, component-level rules, accessibility requirements, content standards, anti-patterns, and a QA checklist.