premium-frontend-design

kv0906/cc-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/kv0906/cc-skills --skill premium-frontend-design
0 commentsdiscussion
summary

$22

skill.md

Premium Frontend Design Skill

This skill guides creation of production-grade frontend interfaces that feel ALIVE — not generic, not copy-paste, but genuinely crafted experiences that users remember.

"The difference between a good interface and an unforgettable one is intentionality in every pixel."


Dependencies (Flexible — Choose What Fits)

This skill is framework-flexible. Pick packages based on user preference and project needs.

Core 3D (for WebGL templates)

pnpm add three @react-three/fiber @react-three/drei

Animation (choose based on user preference)

Library Best For Complexity Bundle Size
CSS/Tailwind Simple transitions, micro-interactions Low 0KB
Framer Motion React-native feel, layout animations, gestures Medium ~30KB
GSAP Complex timelines, scroll-triggered, text effects High ~60KB
GSAP + Club SplitText, ScrollTrigger, MorphSVG High ~80KB
# Framer Motion (simpler, React-idiomatic)
pnpm add framer-motion

# GSAP (powerful, timeline-based)
pnpm add gsap @gsap/react
# Note: SplitText, ScrollTrigger require GSAP Club license

Decision Guide:

  • User says "simple" or "lightweight" → CSS + Framer Motion
  • User says "complex animations" or "scroll effects" → GSAP
  • User says "text animations" or "split text" → GSAP + SplitText
  • User doesn't specify → Default to Framer Motion (simpler API)

Optional Enhancements

# Mesh gradients (for mesh-gradient-hero)
pnpm add @paper-design/shaders-react

# Icons
pnpm add lucide-react

# Charts/Sparklines (for dashboards)
pnpm add recharts
# or lightweight: pnpm add @visx/shape @visx/scale

Browser Compatibility Notes

  • backdrop-filter: Not supported in Firefox < 103 (add fallback bg)
  • WebGL: Provide CSS fallback for older devices
  • @starting-style: Chrome 117+, Safari 17.4+ (progressive enhancement)

Core Philosophy

The "Alive" Principle

An interface feels alive when:

  • It breathes: Subtle ambient animations, particles, or shader effects create constant but non-distracting motion
  • It responds: Micro-interactions acknowledge every user action with satisfying feedback
  • It has depth: Layers, parallax, glassmorphism, and shadows create dimensional space
  • It surprises: At least one element breaks expectations in a delightful way

Design Thinking (Before ANY Code)

Before writing a single line, answer these:

  1. Purpose: What problem does this solve? Who uses it?

  2. Tone: Pick ONE extreme direction (not a blend):

    • Brutally minimal
    • Maximalist chaos
    • Retro-futuristic / Cyberpunk
    • Organic / Natural
    • Luxury / Refined
    • Playful / Toy-like
    • Editorial / Magazine
    • Brutalist / Raw
    • Art Deco / Geometric
    • Industrial / Utilitarian
    • Bio-luminescent / Sci-fi
    • Mission Control / Technical
  3. The One Thing: What single element will someone remember? Every great interface has a signature moment.

  4. Constraints: Framework, performance budgets, accessibility requirements.

CRITICAL: Bold maximalism and refined minimalism both work. The key is intentionality, not intensity. A single, perfectly-executed animation beats 50 mediocre ones.


Wow + Clarity Framework

Use this whenever the brief is vague or when you need to justify design decisions. The goal is wow factor with purpose.

1. Hierarchy Guardrails

  • 1 hero flourish (shader, particle system, or globe). Everything else supports readability.
  • 1 supporting flourish (micro-interactions, animated stat card, or glowing CTA). No more.
  • Layout rule: Hero (wild) → Content blocks (calm) → Proof (calm) → CTA (highlighted).
  • If the page has more than one scroll-length of copy, every second section should be mostly static.

2. Typography Discipline

  • Max 2 headliner fonts (display + body). Monospace only for data.
  • Headline letter-spacing ≥ -0.04em. Anything tighter kills readability.
  • Body width target: 55–75 characters per line on desktop, 35–45 on mobile.
  • Always pair big display text with a plain supporting sentence under 80 characters.

3. Color & Contrast Rules

  • Limit neon usage to primary CTA + 1 accent. Everything else stays in zinc/neutral palette.
  • If background is busy (shader, gradients, particles), add a bg-black/70 or bg-slate-950/70 scrim behind text.
  • Keep contrast ratios ≥ 4.5:1 for body copy even if the aesthetic is cyberpunk.
  • Add a grayscale preview check before shipping: if it looks muddy, dial the palette back.

4. Motion Throttle

  • Default: CSS or Framer Motion with durations ≤ 400ms, easing cubic-bezier(0.34, 1.56, 0.64, 1).
  • Escalate to GSAP/WebGL only if the brief explicitly asks for cinematic or interactive experiences.
  • Max 1 continuous animation per viewport (e.g., shader OR wave bars, not both).
  • Provide a “calm mode”: disable non-essential motion when prefers-reduced-motion is on OR when user scrolls past hero.

5. When Requirements Are Vague

Situation Default Optional Upgrade
User only says “clean SaaS” mesh-gradient-hero + bento-grid Swap hero background for CPPN if they later ask for “more energy”
User says “dashboard” with no flair bento-grid + dashboard-widgets + CSS glow pills Add digital-liquid shader only after data viz is signed off
User says “hero section” but nothing else Text-first layout + CSS gradient Offer shader/globe as a suggestion, never as default

If the prompt does not explicitly mention WebGL, assume CSS-first and opt-in to shaders only when the user embraces the cost.


Anti-Patterns (NEVER Do This)

Visual Anti-Patterns

❌ White/light backgrounds as default (dark mode is premium) ❌ Generic gradients (purple-to-blue on white is AI slop) ❌ Evenly-distributed, timid color palettes ❌ Static, lifeless backgrounds ❌ Cookie-cutter component layouts ❌ Missing loading/transition states ❌ Jarring, un-eased animations

Typography Anti-Patterns

❌ Inter, Roboto, Arial, system fonts for headlines ❌ Same font for everything ❌ Default line-heights and letter-spacing ❌ Boring, predictable type scales

Code Anti-Patterns

❌ Inline styles scattered randomly ❌ No CSS variables for theming ❌ Animations without will-change or GPU acceleration ❌ Canvas/WebGL without requestAnimationFrame ❌ Missing cleanup in useEffect


Design System

1. Color Architecture

Rule: ONE dominant accent, everything else supports it.

// Premium Dark Theme (Default)
const colors = {
  // Backgrounds (layer from darkest to lightest)
  bg: {
    void: '#000000',      // True black for maximum contrast
    primary: '#050505',   // Main background
    elevated: '#0a0a0a',  // Cards, modals
    subtle: '#111111',    // Hover states
  },
  
  // Glass surfaces
  glass: {
    bg: 'rgba(255, 255, 255, 0.03)',
    border: 'rgba(255, 255, 255, 0.08)',
    hover: 'rgba(255, 255, 255, 0.06)',
  },
  
  // Text hierarchy
  text: {
    primary: '#ffffff',
    secondary: '#a1a1aa',   // zinc-400
    muted: '#71717a',       // zinc-500
    ghost: '#3f3f46',       // zinc-700
  },
  
  // Accent (choose ONE per project)
  accent: '#ff4d00',  // Neon Orange
  // accent: '#00f3ff',  // Neon Cyan
  // accent: '#ccff00',  // Neon Lime
  // accent: '#F5E445',  // Premium Yellow
  // accent: '#a855f7',  // Electric Purple
}

Accent Usage Rules:

  • Primary actions: Full accent color
  • Secondary elements: Accent at 20% opacity
  • Borders/lines: Accent at 30% opacity
  • Glows: Accent with blur, 40-60% opacity
  • Never use accent for large background areas

2. Typography System

Rule: Display font for impact, Body font for reading, Mono for data.

/* Tier 1: Display/Headlines - BOLD, characterful */
--font-display: 'Chakra Petch', 'Orbitron', 'Bebas Neue', 'Playfair Display';

/* Tier 2: Headings - Geometric, modern */
--font-heading: 'Manrope', 'Outfit', 'Syne', 'Space Grotesk';

/* Tier 3: Body - Clean, highly legible */
--font-body: 'Plus Jakarta Sans', 'DM Sans', 'Satoshi', 'General Sans';

/* Tier 4: Data/Code - ALWAYS monospace */
--font-mono: 'JetBrains Mono', 'Fira Code', 'IBM Plex Mono';

Typography Patterns:

/* Hero Headlines: Massive, tight, aggressive */
.headline {
  font-family: var(--font-display);
  font-size: clamp(3rem, 12vw, 10rem);
  font-weight: 800;
  line-height: 0.9;
  letter-spacing: -0.03em;
  text-transform: uppercase;
}

/* Section Titles */
.section-title {
  font-family: var(--font-heading);
  font-size: clamp(1.5rem, 4vw, 3rem);
  font-weight: 700;
  letter-spacing: -0.02em;
}

/* Technical Labels */
.label {
  font-family: var(--font-mono);
  font-size: 0.75rem;
  font-weight: 500;
  text-transform: uppercase;
  letter-spacing: 0.1em;
  color: var(--text-muted);
}

/* Data Display */
.data {
  font-family: var(--font-mono);
  font-variant-numeric: tabular-nums;
}

3. Spacing & Layout

Rule: Asymmetry creates interest. Grids are starting points, not prisons.

/* Spacing scale (use consistently) */
--space-1: 0.25rem;   /* 4px */
--space-2
how to use premium-frontend-design

How to use premium-frontend-design on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add premium-frontend-design
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/kv0906/cc-skills --skill premium-frontend-design

The skills CLI fetches premium-frontend-design from GitHub repository kv0906/cc-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/premium-frontend-design

Reload or restart Cursor to activate premium-frontend-design. Access the skill through slash commands (e.g., /premium-frontend-design) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.752 reviews
  • Dhruvi Jain· Dec 24, 2024

    Keeps context tight: premium-frontend-design is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Hiroshi Chawla· Dec 16, 2024

    Solid pick for teams standardizing on skills: premium-frontend-design is focused, and the summary matches what you get after install.

  • Mei Gonzalez· Dec 8, 2024

    premium-frontend-design has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Li Garcia· Dec 8, 2024

    We added premium-frontend-design from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Isabella Torres· Nov 27, 2024

    premium-frontend-design fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Mei Martin· Nov 27, 2024

    Solid pick for teams standardizing on skills: premium-frontend-design is focused, and the summary matches what you get after install.

  • Oshnikdeep· Nov 15, 2024

    Registry listing for premium-frontend-design matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Aanya Malhotra· Nov 15, 2024

    premium-frontend-design reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Nikhil Thompson· Nov 7, 2024

    We added premium-frontend-design from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Isabella Mehta· Nov 3, 2024

    Useful defaults in premium-frontend-design — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 52

1 / 6