Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
kesslerio avatar

Frontend Design Ultimate

  • 56 installs
  • 4 repo stars
  • Updated February 24, 2026
  • kesslerio/ultimate-frontend-design-openclaw-skill

Frontend Design Ultimate is an agent skill that turns text requirements into distinctive React + Tailwind + shadcn/ui static sites without mockups.

About

Frontend Design Ultimate is an agent skill for solo and indie builders who need distinctive static web interfaces without a design handoff. You describe the product, audience, and pages in plain language; the skill walks through explicit design thinking—purpose, audience, and performance constraints—before generating React components styled with Tailwind and shadcn/ui, with optional Framer Motion. It targets anti-generic “AI slop” visuals and mobile-first layouts suited to SaaS landings, portfolios, and lightweight dashboards. Two output paths keep shipping flexible: Vite for pure static HTML bundles and Next.js when you want a Vercel-oriented app structure. Node and npm are required on the machine. Use it when you are ready to implement UI, including during validation when a credible landing page helps prove demand, and during build when you want a memorable frontend fast.

  • React 18 + TypeScript + Tailwind CSS + shadcn/ui + Framer Motion stack
  • Design-thinking gate: commit to a bold aesthetic direction before any code
  • Anti–AI-slop aesthetics, mobile-first responsive patterns, and grain/texture editorial options
  • Vite single-file static bundle or Next.js workflow for Vercel-ready deploy
  • Landing pages, portfolios, dashboards, FAQ/pricing grids, and marketing sections from text briefs

Frontend Design Ultimate by the numbers

  • 56 all-time installs (skills.sh)
  • Ranked #1,248 of 2,245 Frontend Development skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 25, 2026 (Skillselion catalog sync)
npx skills add https://github.com/kesslerio/ultimate-frontend-design-openclaw-skill --skill frontend-design-ultimate

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs56
repo stars4
Security audit2 / 3 scanners passed
Last updatedFebruary 24, 2026
Repositorykesslerio/ultimate-frontend-design-openclaw-skill

What it does

Generate bold, production-grade marketing and product UIs from plain-text requirements without Figma mockups.

Who is it for?

Best when you're shipping landing pages, marketing sites, or dashboard shells and want bold, non-generic design from a written spec.

Skip if: Skip if you already have approved Figma systems and only need pixel-perfect reproduction, or backends/API-only work with no static UI.

When should I use this skill?

Building landing pages, marketing sites, portfolios, dashboards, or any static web UI from plain text requirements.

What you get

You get a committed aesthetic direction and a production-grade React/Tailwind implementation as Vite static output or a Next.js project ready to deploy.

  • Vite-based static site or Next.js project with React/Tailwind UI
  • Page sections such as hero, features, pricing, FAQ, and footer per brief

By the numbers

  • Stack: React 18 + TypeScript + Tailwind CSS + shadcn/ui + Framer Motion
  • Two output workflows: Vite (pure static) and Next.js (Vercel deploy)

Files

SKILL.mdMarkdownGitHub ↗

Frontend Design Ultimate

Create distinctive, production-grade static sites from text requirements alone. No mockups, no Figma — just describe what you want and get bold, memorable designs.

Stack: React 18 + TypeScript + Tailwind CSS + shadcn/ui + Framer Motion Output: Vite (static HTML) or Next.js (Vercel-ready)

Quick Start

"Build a SaaS landing page for an AI writing tool. Dark theme, 
editorial typography, subtle grain texture. Pages: hero with 
animated demo, features grid, pricing table, FAQ accordion, footer."

---

Design Thinking (Do This First)

Before writing any code, commit to a BOLD aesthetic direction:

1. Understand Context

  • Purpose: What problem does this interface solve? Who uses it?
  • Audience: Developer tools? Consumer app? Enterprise? Creative agency?
  • Constraints: Performance requirements, accessibility needs, brand guidelines?

2. Choose an Extreme Tone

Pick ONE and commit fully — timid designs fail:

ToneCharacteristics
Brutally MinimalSparse, monochrome, massive typography, raw edges
Maximalist ChaosLayered, dense, overlapping elements, controlled disorder
Retro-FuturisticNeon accents, geometric shapes, CRT aesthetics
Organic/NaturalSoft curves, earth tones, hand-drawn elements
Luxury/RefinedSubtle animations, premium typography, restrained palette
Editorial/MagazineStrong grid, dramatic headlines, whitespace as feature
Brutalist/RawExposed structure, harsh contrasts, anti-design
Art Deco/GeometricGold accents, symmetry, ornate patterns
Soft/PastelRounded corners, gentle gradients, friendly
Industrial/UtilitarianFunctional, monospace, data-dense

3. Define the Unforgettable Element

What's the ONE thing someone will remember? A hero animation? Typography treatment? Color combination? Unusual layout?

---

Aesthetics Guidelines

Typography — NEVER Generic

BANNED: Inter, Roboto, Arial, system fonts, Open Sans

DO: Distinctive, characterful choices that elevate the design.

Use CaseApproach
Display/HeadlinesBold personality — Clash, Cabinet Grotesk, Satoshi, Space Grotesk (sparingly), Playfair Display
Body TextRefined readability — Instrument Sans, General Sans, Plus Jakarta Sans
Monospace/CodeDM Mono, JetBrains Mono, IBM Plex Mono
Pairing StrategyContrast weights (thin display + bold body), contrast styles (serif + geometric sans)

Size Progression: Use 3x+ jumps, not timid 1.5x increments.

Color & Theme

BANNED: Purple gradients on white, evenly-distributed 5-color palettes

DO:

  • Dominant + Sharp Accent: 70-20-10 rule (primary-secondary-accent)
  • CSS Variables: --primary, --accent, --surface, --text
  • Commit to dark OR light: Don't hedge with gray middle-grounds
  • High contrast CTAs: Buttons should pop dramatically
:root {
  --bg-primary: #0a0a0a;
  --bg-secondary: #141414;
  --text-primary: #fafafa;
  --text-secondary: #a1a1a1;
  --accent: #ff6b35;
  --accent-hover: #ff8555;
}

Motion & Animation

Priority: One orchestrated page load > scattered micro-interactions

High-Impact Moments:

  • Staggered hero reveals (animation-delay)
  • Scroll-triggered section entrances
  • Hover states that surprise (scale, color shift, shadow depth)
  • Smooth page transitions

Implementation:

  • CSS-only for simple animations
  • Framer Motion for React (pre-installed via init scripts)
  • Keep durations 200-400ms (snappy, not sluggish)

Spatial Composition

BANNED: Centered, symmetrical, predictable layouts

DO:

  • Asymmetry with purpose
  • Overlapping elements
  • Diagonal flow / grid-breaking
  • Generous negative space OR controlled density (pick one)
  • Off-grid hero sections

Backgrounds & Atmosphere

BANNED: Solid white/gray backgrounds

DO:

  • Gradient meshes (subtle, not garish)
  • Noise/grain textures (SVG filter or CSS)
  • Geometric patterns (dots, lines, shapes)
  • Layered transparencies
  • Dramatic shadows for depth
  • Blur effects for glassmorphism
/* Subtle grain overlay */
.grain::before {
  content: '';
  position: fixed;
  inset: 0;
  background: url("data:image/svg+xml,...") repeat;
  opacity: 0.03;
  pointer-events: none;
}

---

Mobile-First Patterns

See [references/mobile-patterns.md](references/mobile-patterns.md) for detailed CSS.

Critical Rules

PatternDesktopMobile Fix
Hero with hidden visual2-column gridSwitch to display: flex (not grid)
Large selection listsHorizontal scrollAccordion with category headers
Multi-column formsSide-by-sideStack vertically
Status/alert cardsInlinealign-items: center + text-align: center
Feature grids3-4 columnsSingle column

Breakpoints

/* Tablet - stack sidebars */
@media (max-width: 1200px) { }

/* Mobile - full single column */
@media (max-width: 768px) { }

/* Small mobile - compact spacing */
@media (max-width: 480px) { }

Font Scaling

@media (max-width: 768px) {
  .hero-title { font-size: 32px; }      /* from ~48px */
  .section-title { font-size: 24px; }   /* from ~32px */
  .section-subtitle { font-size: 14px; } /* from ~16px */
}

---

Build Workflow

Option A: Vite (Pure Static)

# 1. Initialize
bash scripts/init-vite.sh my-site
cd my-site

# 2. Develop
npm run dev

# 3. Build static files
npm run build
# Output: dist/

# 4. Bundle to single HTML (optional)
bash scripts/bundle-artifact.sh
# Output: bundle.html

Option B: Next.js (Vercel Deploy)

# 1. Initialize
bash scripts/init-nextjs.sh my-site
cd my-site

# 2. Develop
npm run dev

# 3. Deploy to Vercel
vercel

---

Project Structure

Vite Static

my-site/
├── src/
│   ├── components/     # React components
│   ├── lib/           # Utilities, cn()
│   ├── styles/        # Global CSS
│   ├── config/
│   │   └── site.ts    # Editable content config
│   ├── App.tsx
│   └── main.tsx
├── index.html
├── tailwind.config.ts
└── package.json

Next.js

my-site/
├── app/
│   ├── layout.tsx
│   ├── page.tsx
│   └── privacy/page.tsx
├── components/
├── lib/
├── config/
│   └── site.ts
└── tailwind.config.ts

---

Site Config Pattern

Keep all editable content in one file:

// config/site.ts
export const siteConfig = {
  name: "Acme AI",
  tagline: "Write better, faster",
  description: "AI-powered writing assistant",
  
  hero: {
    badge: "Now in beta",
    title: "Your words,\nsupercharged",
    subtitle: "Write 10x faster with AI that understands your style",
    cta: { text: "Get Started", href: "/signup" },
    secondaryCta: { text: "Watch Demo", href: "#demo" },
  },
  
  features: [
    { icon: "Zap", title: "Lightning Fast", description: "..." },
    // ...
  ],
  
  pricing: [
    { name: "Free", price: 0, features: [...] },
    { name: "Pro", price: 19, features: [...], popular: true },
  ],
  
  faq: [
    { q: "How does it work?", a: "..." },
  ],
  
  footer: {
    links: [...],
    social: [...],
  }
}

---

Pre-Implementation Checklist

Run this before finalizing any design:

Design Quality

  • [ ] Typography is distinctive (no Inter/Roboto/Arial)
  • [ ] Color palette has clear dominant + accent (not evenly distributed)
  • [ ] Background has atmosphere (not solid white/gray)
  • [ ] At least one memorable/unforgettable element
  • [ ] Animations are orchestrated (not scattered)

Mobile Responsiveness

  • [ ] Hero centers on mobile (no empty grid space)
  • [ ] All grids collapse to single column
  • [ ] Forms stack vertically
  • [ ] Large lists use accordion (not horizontal scroll)
  • [ ] Font sizes scale down appropriately

Form Consistency

  • [ ] Input, select, textarea all styled consistently
  • [ ] Radio/checkbox visible (check transparent-border styles)
  • [ ] Dropdown options have readable backgrounds
  • [ ] Labels use CSS variables (not hardcoded colors)

Accessibility

  • [ ] Color contrast meets WCAG AA (4.5:1 text, 3:1 UI)
  • [ ] Focus states visible
  • [ ] Semantic HTML (nav, main, section, article)
  • [ ] Alt text for images
  • [ ] Keyboard navigation works

---

shadcn/ui Components

10 common components pre-installed (button, badge, card, accordion, dialog, navigation-menu, tabs, sheet, separator, avatar, alert). Add more with npx shadcn@latest add [name] or install all with npx shadcn@latest add --all.

See [references/shadcn-components.md](references/shadcn-components.md) for full component reference.

Most used for landing pages:

  • Button, Badge — CTAs and labels
  • Card — Feature cards, pricing tiers
  • Accordion — FAQ sections
  • Dialog — Modals, video players
  • NavigationMenu — Header nav
  • Tabs — Feature showcases
  • Carousel — Testimonials

---

References

  • [references/design-philosophy.md](references/design-philosophy.md) — Extended anti-AI-slop guidance
  • [references/mobile-patterns.md](references/mobile-patterns.md) — Detailed responsive CSS
  • [references/shadcn-components.md](references/shadcn-components.md) — Component quick reference
  • [templates/site-config.ts](templates/site-config.ts) — Full siteConfig example

---

Examples

Prompt → Output

Input:

"Portfolio site for a photographer. Minimal, editorial feel.
Grid gallery with lightbox, about section, contact form."

Design Decisions:

  • Tone: Editorial/Magazine
  • Typography: Cormorant Garamond (display) + Inter... wait, banned. Plus Jakarta Sans (body)
  • Color: Near-black bg (#0c0c0c), warm white text (#f5f5f0), copper accent (#b87333)
  • Unforgettable: Full-bleed hero image with text overlay that reveals on scroll
  • Motion: Gallery images fade in staggered on scroll

Output: Complete Next.js project with responsive gallery, lightbox component, and contact form with validation.

---

Based on Anthropic's frontend-design, web-artifacts-builder, and community frontend-design-v2 skills.

Related skills

How it compares

Use instead of generic “make me a landing page” chat when you want enforced design thinking plus a fixed React/shadcn stack.

FAQ

Who is frontend-design-ultimate for?

and developers using Claude Code, Cursor, or similar agents who need distinctive marketing or app UI fast, with Node/npm available locally.

When should I use frontend-design-ultimate?

During Validate when you need a credible landing or pricing page to test demand, and during Build when you are implementing hero sections, feature grids, dashboards, or full static marketing sites from a text brief.

Is frontend-design-ultimate safe to install?

Review the Security Audits panel on this Prism page and the skill’s GitHub source before granting filesystem and shell access for npm installs and project generation.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.