fantasy

Create fantasy-themed design-system rules using typography, spacing, and color tokens.

1|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/PiercingXX/xx-stack --skill fantasy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fantasy
Source: https://github.com/PiercingXX/xx-stack/tree/main/packs/design/design-skills/fantasy
Command: npx skills add https://github.com/PiercingXX/xx-stack --skill fantasy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a fantasy-inspired aesthetic into clear, implementation-ready design-system guidance so teams stop guessing and build consistent UI.

Core Features & Use Cases

  • Brand-consistent foundations: Defines typography, spacing, and color tokens (e.g., primary #0250CC, secondary #FDC800) to keep the visual language coherent.
  • Component-ready rules: Provides opinionated do/don’t guidance plus workflow steps for authoring component guidance that includes states, responsive behavior, and edge cases.
  • Accessibility and QA gates: Requires WCAG 2.2 AA, keyboard-first interaction considerations, and testable acceptance criteria to prevent “pretty but unusable” designs.

Quick Start

Ask the AI to generate fantasy design-system component guidance that follows the provided tokens and includes required interaction states, accessibility acceptance criteria, and a code-review QA checklist.

Frequently Asked Questions about fantasy

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

FAQPage Schema
How do I create a fantasy-themed design system that engineers can actually implement?

To create a fantasy-themed design system, you need predefined typography, spacing, and color tokens combined with component guidelines covering interaction states and responsive behavior. This ensures visual language coherence while satisfying implementation requirements for engineering teams.

What is semantic token usage in UI component guidelines?

Semantic token usage in UI component guidelines refers to enforcing standardized typography and color values, such as primary #0250CC and secondary #FDC800, to maintain consistent visual language across fantasy-themed design systems without hardcoding values.

How do I include accessibility acceptance criteria in a design system?

Accessibility acceptance criteria in a design system must enforce WCAG 2.2 AA compliance, keyboard-first interaction considerations, and visible focus states. This prevents visually appealing fantasy themes from becoming unusable for people relying on assistive technologies.

Does this design system guidance cover empty and overflow edge cases for components?

Yes, the design system guidance covers empty and overflow cases alongside standard interaction states and responsive behavior. It provides opinionated do and don't workflow steps to document edge cases and anti-patterns for UI components.

Can I generate a testable QA checklist for UI component code reviews?

Yes, you can generate a testable QA checklist for UI component code reviews using a must and should rule structure. This checklist validates semantic token usage, accessibility requirements, and interaction states during the development workflow.

What is the best way to document anti-patterns in a fantasy design system?

The best way to document anti-patterns in a fantasy design system is to provide opinionated do and don't guidance within component rules. This includes workflow steps for authoring guidelines that explicitly state what to avoid during implementation.