luxury

Generate luxury dark UI design rules with typography and monochromatic tokens.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams consistently produce a premium-looking dark UI with bold typography, monochromatic depth, and accessibility-safe interaction patterns.

Core Features & Use Cases

  • Luxury visual foundations: Defines monochromatic color tokens, Oswald-based bold headings, and JetBrains Mono for labels/caps.
  • Implementation-ready design rules: Provides explicit Do/Don't guidance to preserve hierarchy, spacing rhythm, and consistent component behavior.
  • Accessibility-first interaction standards: Requires keyboard-first behavior, visible focus states, semantic HTML over ARIA, and high-contrast support.
  • Quality gates for review: Turns style intent into testable acceptance criteria and a QA checklist for code review.

Quick Start

Use this skill to generate or review the UI styles and component guidelines for a luxury dark-mode product page, including typography, tokens, and accessible interaction states.

Frequently Asked Questions about luxury

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

FAQPage Schema
How do I create a luxury dark mode design system with high contrast and premium typography?

Build a luxury dark UI by defining monochromatic color tokens, applying bold Oswald typography for headings, and using JetBrains Mono for labels to ensure premium visual hierarchy and consistent component behavior.

What are the best practices for ensuring accessibility in a high-contrast luxury UI?

Ensure accessibility in a high-contrast luxury UI by enforcing keyboard-first behavior, providing visible focus states, and using semantic HTML over ARIA to create interaction patterns that are safe and testable.

How do I turn UI design rules into testable QA acceptance criteria for a design system?

Turn UI design rules into testable QA acceptance criteria by applying quality gates that validate token-driven styling, explicit interaction states, and semantic accessibility to convert style intent into a reviewable checklist.

Can I use this approach to build component families like buttons, inputs, and modals for a luxury interface?

Yes, you can apply these token-driven styling rules to build component families like buttons, inputs, cards, navigation, and modals, using explicit guidance to preserve spacing rhythm and consistent behavior.

What typography pairs work best for a premium dark mode product page?

Oswald and JetBrains Mono work best for a premium dark mode product page, using bold Oswald headings for monochromatic depth and JetBrains Mono for labels to establish a strong visual hierarchy.