frontend-distinct

Generates distinctive frontend interfaces with token-driven design systems and complete interaction states.

2|2|Updated Dec 23, 2017
One-click install
npx skills add https://github.com/xriu/dotfiles --skill frontend-distinct-xriu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-distinct
Source: https://github.com/xriu/dotfiles/tree/main/home/.skills/frontend-distinct
Command: npx skills add https://github.com/xriu/dotfiles --skill frontend-distinct-xriu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated interfaces often converge on generic template aesthetics—default fonts, purple gradients, and predictable card layouts. This Skill enforces intentional art direction so every UI build has a distinct visual identity, complete interaction states, and production-grade accessibility. ## Core Features & Use Cases - Art Direction Enforcement: Commits to a radical design direction (editorial, brutalist, retro-futurist, etc.) with a functional signature element unique to each build. - Token-Driven Design System: Defines CSS custom properties for color, typography, spacing, radius, shadow, and motion before any layout work begins. - Complete State Coverage: Requires hover, focus, disabled, loading, error, and empty states plus failure handling for network and data issues. - Use Case: Ask for a landing page for a coffee subscription brand, and receive a complete interface with a defined art direction brief, custom typography pairing, orchestrated entrance motion, and WCAG-conscious focus states—rather than a generic Tailwind template. ## Quick Start Use the frontend-distinct skill to design a landing page for my product with a bold editorial art direction and full interaction states.

Frequently Asked Questions about frontend-distinct

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

FAQPage Schema
How do I make AI-generated UI not look like a template?▼

Commit to one radical art direction before writing code, define design tokens first, and invent a functional signature element such as a morphing frame or typographic hero. Avoid default fonts like Inter and predictable hero-plus-three-cards layouts.

What design tokens should a frontend design system include?▼

Define CSS custom properties for color roles, typography scales with line heights, spacing steps, radius, shadows, and motion durations with easing curves. Tokens should drive all styling decisions rather than one-off values.

Does this approach work with Tailwind or component frameworks?▼

Yes, but default Tailwind appearance with minimal tokenization is explicitly rejected. The framework must be configured through the token system so the output reflects the chosen art direction rather than recognizable defaults.

What interaction states must every UI component implement?▼

Every interactive element needs default, hover, active, focus-visible, disabled, loading, error, and empty states where applicable. Failure paths like network errors must be visually intentional and on-brand, never silent or browser-default.

How is accessibility handled in generated interfaces?▼

Interfaces require semantic HTML, keyboard navigation for all interactive elements, visible focus styling integrated into the aesthetic, and respect for prefers-reduced-motion with clean fallbacks. Touch targets must be at least 44 pixels on mobile.