Frontend Design Ultimate
Generate bold, production-grade marketing and product UIs from plain-text requirements without Figma mockups.
Overview
Frontend Design Ultimate is an agent skill most often used in Build (also Validate landing work) that turns text requirements into distinctive React + Tailwind + shadcn/ui static sites without mockups.
Install
npx skills add https://github.com/kesslerio/ultimate-frontend-design-openclaw-skill --skill frontend-design-ultimateWhat is this skill?
- 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
- Stack: React 18 + TypeScript + Tailwind CSS + shadcn/ui + Framer Motion
- Two output workflows: Vite (pure static) and Next.js (Vercel deploy)
Adoption & trust: 1 installs on skills.sh; 3 GitHub stars; 2/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You know what pages you need but lack a memorable visual direction and a fast path from a text brief to shippable React UI.
Who is it for?
Solo builders shipping landing pages, marketing sites, or dashboard shells who want bold, non-generic design from a written spec.
Skip if: Teams that 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 do I get? / Deliverables
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
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Build because the skill outputs React/Tailwind/shadcn implementations, even though it is often invoked while shaping landing and dashboard experiences earlier in the journey. Frontend is the primary artifact: pages, layouts, motion, and responsive patterns—not backend APIs or deploy pipelines.
Where it fits
Ship a dark-themed pricing and FAQ landing to test signups before the full product exists.
Implement hero, features grid, and dashboard shell with shadcn/ui and Tailwind from a one-paragraph product brief.
Refresh marketing pages with distinctive typography and motion for a launch announcement.
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.
Common Questions / FAQ
Who is frontend-design-ultimate for?
Indie and solo builders 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.
SKILL.md
READMESKILL.md - Frontend Design Ultimate
# 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: | Tone | Characteristics | |------|-----------------| | **Brutally Minimal** | Sparse, monochrome, massive typography, raw edges | | **Maximalist Chaos** | Layered, dense, overlapping elements, controlled disorder | | **Retro-Futuristic** | Neon accents, geometric shapes, CRT aesthetics | | **Organic/Natural** | Soft curves, earth tones, hand-drawn elements | | **Luxury/Refined** | Subtle animations, premium typography, restrained palette | | **Editorial/Magazine** | Strong grid, dramatic headlines, whitespace as feature | | **Brutalist/Raw** | Exposed structure, harsh contrasts, anti-design | | **Art Deco/Geometric** | Gold accents, symmetry, ornate patterns | | **Soft/Pastel** | Rounded corners, gentle gradients, friendly | | **Industrial/Utilitarian** | Functional, 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 Case | Approach | |----------|----------| | Display/Headlines | Bold personality — Clash, Cabinet Grotesk, Satoshi, Space Grotesk (sparingly), Playfair Display | | Body Text | Refined readability — Instrument Sans, General Sans, Plus Jakarta Sans | | Monospace/Code | DM Mono, JetBrains Mono, IBM Plex Mono | | Pairing Strategy | Contrast 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 ```css :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`) - Scro