Nick's enterprise design system. Enforces his visual standards on every web project — typography, color, layout, spacing, components, and anti-patterns. Must be referenced before any build spec is written. Produces "Enterprise Confidence with Clean Authority" — never generic AI design.
Nick's Design System — "Enterprise Confidence with Clean Authority"
When to Use
Before writing ANY build spec for a web project, read this entire file and incorporate every applicable section into the Claude Code prompt. No exceptions.
Design Philosophy
The design should feel like it belongs at the top of its industry. Not because it's flashy — because it's structured, intentional, and unapologetically polished. The design doesn't try hard. It just is.
Every element earns its place. Nothing decorative without purpose. Nothing trendy that ages in six months. Clean lines, strong brand presence, architecture that rewards exploration.
Feature sections MUST alternate layout direction (text-left/visual-right → visual-left/text-right).
ALWAYS screenshot the competitor before building and match/exceed their visual density.
Run visual review skill DURING development, not just after deploy.
Pre-Build Checklist
Before passing any spec to Claude Code, verify:
Brand accent color chosen for this project
Typography: Inter loaded, scale applied
Hero section: dark bg, large headline, clear CTA
Spacing: generous, follows 4px grid
Navigation: sticky, mega-menu if complex
Footer: comprehensive, multi-column
Responsive: mobile-first, all breakpoints covered
Animations: subtle fade-up on scroll, hover states on interactive elements
Images: no stock photos, using geometric/abstract/custom
Anti-patterns: none of the 14 anti-patterns present
Accessibility: contrast ratios met, focus states visible, semantic HTML
SEO: meta tags, Open Graph, structured heading hierarchy
1---2name: nick-design-system3description: Nick's enterprise design system. Enforces his visual standards on every web project — typography, color, layout, spacing, components, and anti-patterns. Must be referenced before any build spec is written. Produces "Enterprise Confidence with Clean Authority" — never generic AI design.4---56# Nick's Design System — "Enterprise Confidence with Clean Authority"78## When to Use9Before writing ANY build spec for a web project, read this entire file and incorporate every applicable section into the Claude Code prompt. No exceptions.1011## Design Philosophy12The design should feel like it belongs at the top of its industry. Not because it's flashy — because it's structured, intentional, and unapologetically polished. The design doesn't try hard. It just is.1314Every element earns its place. Nothing decorative without purpose. Nothing trendy that ages in six months. Clean lines, strong brand presence, architecture that rewards exploration.1516Reference sites: Accenture, Atlassian, Adobe, NVIDIA, Rocket Companies.1718---1920## Typography2122### Font Stack23- **Primary:** Inter (headings + body) — clean, modern, enterprise-grade sans-serif24- **Alternate:** Plus Jakarta Sans or DM Sans for projects needing warmer personality25- **Monospace:** JetBrains Mono (code blocks, data displays)26- Always load via Google Fonts or next/font for performance2728### Scale (Desktop)29| Element | Size | Weight | Line Height | Letter Spacing |30|---------|------|--------|-------------|----------------|31| Display/Hero | 56–72px (3.5–4.5rem) | 700–800 | 1.05–1.1 | -0.02em |32| H1 | 48px (3rem) | 700 | 1.1 | -0.02em |33| H2 | 36px (2.25rem) | 600–700 | 1.15 | -0.01em |34| H3 | 28px (1.75rem) | 600 | 1.2 | -0.01em |35| H4 | 22px (1.375rem) | 600 | 1.3 | 0 |36| Body Large | 18px (1.125rem) | 400 | 1.6 | 0 |37| Body | 16px (1rem) | 400 | 1.6 | 0 |38| Body Small | 14px (0.875rem) | 400 | 1.5 | 0 |39| Caption/Label | 12px (0.75rem) | 500 | 1.4 | 0.02em |4041### Scale (Mobile)42- Hero: 36–44px43- H1: 32px44- H2: 26px45- H3: 22px46- Body: 16px (never smaller)4748### Rules49- Headlines are LARGE and DECLARATIVE — short statements that hit, not paragraphs50- Headlines should read like mission statements: tell what you ARE, not what you sell51- Examples of good headlines: "Let There Be Change", "Help Everyone Home", "World Leader in AI Computing"52- Max 8–12 words per hero headline53- Subheadlines: 1–2 sentences max, Body Large size, lighter weight (400)54- Never use more than 2 font families per project5556---5758## Color System5960### Palette Architecture61Every project gets a branded palette. No random colors. Each color earns its spot.6263#### Neutral Foundation64```65--gray-50: #FAFAFA /* Page backgrounds */66--gray-100: #F5F5F5 /* Section alternates */67--gray-200: #E5E5E5 /* Borders, dividers */68--gray-300: #D4D4D4 /* Disabled states */69--gray-400: #A3A3A3 /* Placeholder text */70--gray-500: #737373 /* Secondary text */71--gray-600: #525252 /* Body text (light bg) */72--gray-700: #404040 /* Strong body text */73--gray-800: #262626 /* Headlines (light bg) */74--gray-900: #171717 /* Dark backgrounds */75--gray-950: #0A0A0A /* Deepest dark */76```7778#### Brand Accent Options (pick ONE primary per project)79```80/* Purple — authority, innovation (Accenture-inspired) */81--purple-500: #A100FF82--purple-600: #7B00CC83--purple-700: #5C00998485/* Green — growth, fintech, trust */86--green-500: #00C85387--green-600: #00A84388--green-700: #0085338990/* Blue — reliability, enterprise (Atlassian-inspired) */91--blue-500: #0052CC92--blue-600: #0747A693--blue-700: #0038849495/* Red — energy, boldness (Adobe/Rocket-inspired) */96--red-500: #E5193797--red-600: #C7152F98--red-700: #A0112899```100101#### System Colors102```103--success: #16A34A104--warning: #EAB308105--error: #DC2626106--info: #2563EB107```108109### Color Rules110- Dark heroes with light text are strong openers — use them111- White/light section backgrounds are fine but must feel SPACIOUS and DELIBERATE, not empty112- Alternate between dark and light sections for rhythm113- Accent color used sparingly: CTAs, key highlights, hover states, brand moments114- Never use gradients as backgrounds (they look generic/AI). Solid colors or subtle texture only115- If gradient is needed, keep it very subtle (5–10% opacity shift), never rainbow116- Text contrast: minimum 4.5:1 ratio always117118---119120## Spacing System121122### Base Unit: 4px123```124--space-1: 4px (0.25rem)125--space-2: 8px (0.5rem)126--space-3: 12px (0.75rem)127--space-4: 16px (1rem)128--space-5: 20px (1.25rem)129--space-6: 24px (1.5rem)130--space-8: 32px (2rem)131--space-10: 40px (2.5rem)132--space-12: 48px (3rem)133--space-16: 64px (4rem)134--space-20: 80px (5rem)135--space-24: 96px (6rem)136--space-32: 128px (8rem)137```138139### Section Spacing140- Between major sections: 96–128px (space-24 to space-32)141- Section internal padding: 64–96px vertical (space-16 to space-24)142- Content max-width: 1280px (80rem) with auto margins143- Generous whitespace is MANDATORY — the page must breathe144- Never stack content blocks without adequate spacing145146### Container Widths147```148--container-sm: 640px /* Narrow content, forms */149--container-md: 768px /* Blog posts, articles */150--container-lg: 1024px /* Standard content */151--container-xl: 1280px /* Full layouts */152--container-2xl: 1536px /* Wide layouts, dashboards */153```154155---156157## Layout Patterns158159### Navigation160- **Style:** Clean horizontal nav with mega-menu capability for complex sites161- Mega-menus signal ecosystem depth — use them when there are 3+ product/service areas162- Nav should feel structured and layered — "there's a lot here" without clutter163- Sticky nav on scroll with subtle backdrop blur + shadow164- Mobile: full-screen overlay menu, not a tiny hamburger dropdown165- Nav height: 64–80px desktop, 56–64px mobile166167### Hero Sections168- GO BIG. Full-viewport or near-full-viewport heroes169- Dark background with light text is the default strong opener170- One clear headline (large, declarative), one subheadline, one CTA171- Hero image/video should be cinematic or tech-forward, never generic stock172- If no custom imagery: use abstract geometric patterns, not stock photos173- Subtle entrance animations (fade up, not bounce)174175### Content Sections176- Alternate light/dark backgrounds for visual rhythm177- Use CSS Grid for complex layouts, Flexbox for simpler arrangements178- Card grids: 3-column on desktop, 2 on tablet, 1 on mobile179- Cards should have consistent height within a row180- Section titles centered or left-aligned (be consistent within a project)181182### Footer183- Comprehensive, multi-column footer (enterprise signal)184- Include: nav links, company info, social links, legal185- Dark background preferred186- Not an afterthought — it should feel intentional187188---189190## Component Standards191192### Buttons193```css194/* Primary CTA */195padding: 14px 32px;196font-size: 16px;197font-weight: 600;198border-radius: 8px;199transition: all 0.2s ease;200/* Use brand accent color as background */201202/* Secondary/Outline */203Same sizing, transparent bg, 2px border in brand color204205/* Ghost */206No border, brand color text, subtle hover background207```208- Minimum touch target: 44x44px209- Never use rounded-full (pill) buttons — they look generic210- Hover: subtle lift (translateY -1px) + shadow, or darken bg 10%211- Active: scale(0.98) for tactile feel212213### Cards214```css215background: white; /* or gray-900 on dark sections */216border-radius: 12px;217padding: 32px;218border: 1px solid var(--gray-200); /* light mode */219transition: all 0.3s ease;220```221- Hover: subtle shadow elevation + slight translateY222- No heavy borders or outlines223- Image cards: image fills top, content below with consistent padding224- Always equal height in grids225226### Forms227- Large input fields (48–52px height)228- 12px border-radius on inputs229- Clear labels above inputs (never floating labels — they're confusing)230- Visible focus states with brand color ring231- Error states: red border + message below field232- Group related fields logically233234### Tables/Data235- Clean horizontal lines, no vertical borders236- Alternating row backgrounds (very subtle)237- Sticky headers on long tables238- Responsive: horizontal scroll or card-stack on mobile239240---241242## Animation & Motion243244### Principles245- Motion should feel purposeful, not decorative246- Everything is subtle — no bouncing, no spinning, no excessive parallax247- If a user wouldn't notice it consciously, it's working248249### Standard Transitions250```css251/* Default */252transition: all 0.2s ease;253254/* Hover effects */255transition: all 0.3s cubic-bezier(0.4, 0, 0.2, 1);256257/* Page transitions / section reveals */258transition: all 0.5s cubic-bezier(0.4, 0, 0.2, 1);259```260261### Scroll Animations262- Fade-up on scroll for content sections (use Framer Motion or CSS intersection observer)263- Stagger children: 50–100ms delay between items264- Never animate more than opacity + transform265- Reduce motion: respect `prefers-reduced-motion`266267---268269## Imagery & Media270271### Rules272- NO generic stock photography. Ever.273- Acceptable: custom photography, tech-forward renders, cinematic imagery, abstract geometric patterns, brand illustrations274- If no budget for custom imagery: use abstract/geometric patterns, subtle gradient meshes, or icon-based illustrations275- Hero images should be high-quality, full-bleed or contained with purpose276- Icons: Lucide React (consistent, clean line style)277- Icon size: 20–24px inline, 32–48px for feature blocks278279---280281## Responsive Design282283### Breakpoints (Tailwind defaults)284```285sm: 640px286md: 768px287lg: 1024px288xl: 1280px2892xl: 1536px290```291292### Rules293- Mobile-first approach always294- Touch targets minimum 44x44px295- Body text never below 16px on mobile296- Test at: 375px (phone), 768px (tablet), 1280px (laptop), 1920px (desktop)297- Navigation collapses to mobile menu at `lg` breakpoint298- Images are always responsive with proper aspect ratios299- No horizontal scroll on any viewport300301---302303## Anti-Patterns (NEVER DO THESE)3043051. **Generic AI gradients** — rainbow or purple-blue-pink gradients everywhere3062. **Cookie-cutter SaaS templates** — the Stripe clone look everyone uses3073. **Floating labels on forms** — confusing and look broken3084. **Tiny hamburger dropdowns** — use full-screen mobile menus3095. **Stock photo heroes** — smiling business people shaking hands3106. **Rounded-full pill buttons** — generic and trendy3117. **Excessive animations** — bouncing, spinning, parallax overload3128. **Low-contrast text** — gray on gray, light text on light backgrounds3139. **Cluttered layouts** — insufficient spacing, cramming content31410. **Sloppy responsive** — content overflowing, breaking at random widths31511. **Generic "SaaS purple"** — that same washed-out purple every AI tool uses31612. **Testimonial carousels with stock headshots** — if you can't get real photos, use text-only testimonials31713. **"Built with [framework]" energy** — the site should feel custom, not template-derived31814. **Decorative blobs or circles** — those amorphous SVG shapes in the background319320---321322## Homepage / Landing Page Minimum Standard323324EVERY landing page must include AT LEAST these sections (12-15 minimum):3251. **Rich hero** — gradient bg, device mockup (CSS phone/laptop), headline, dual CTAs, trust chips3262. **Trust/press bar** — "Featured in" logos (TechCrunch, Forbes, etc.)3273. **Featured content cards** — with gradient headers, shadows, hover elevation, ratings, badges3284. **How It Works** — 3-4 steps with numbered badges and icons3295. **Feature showcase (audience 1)** — alternating text+visual layout with UI mockup3306. **Feature showcase (audience 2)** — reversed layout with dashboard/product mockup3317. **Stats section** — large numbers on dark gradient with glass-morphism cards3328. **Testimonials** — star ratings, avatar initials, quotation marks, author details3339. **Pricing** — clear card with feature checklist and CTA33410. **FAQ accordion** — 6+ questions with expand/collapse33511. **Final CTA** — dark gradient, big headline, dual buttons, app store badges33612. **Comprehensive footer** — multi-column, social icons, legal links337338### Key Rules:339- NEVER ship a sparse homepage. Visual density = credibility.340- ALWAYS use static/hardcoded demo data so homepage looks rich without database dependency.341- ALWAYS build device mockups with CSS (phone frames, dashboard previews) — they prove the product exists.342- ALWAYS alternate section backgrounds (gradient, dark, gray-50, white) for visual rhythm.343- Feature sections MUST alternate layout direction (text-left/visual-right → visual-left/text-right).344- ALWAYS screenshot the competitor before building and match/exceed their visual density.345- Run visual review skill DURING development, not just after deploy.346347## Pre-Build Checklist348349Before passing any spec to Claude Code, verify:350351- [ ] Brand accent color chosen for this project352- [ ] Typography: Inter loaded, scale applied353- [ ] Hero section: dark bg, large headline, clear CTA354- [ ] Spacing: generous, follows 4px grid355- [ ] Navigation: sticky, mega-menu if complex356- [ ] Footer: comprehensive, multi-column357- [ ] Responsive: mobile-first, all breakpoints covered358- [ ] Animations: subtle fade-up on scroll, hover states on interactive elements359- [ ] Images: no stock photos, using geometric/abstract/custom360- [ ] Anti-patterns: none of the 14 anti-patterns present361- [ ] Accessibility: contrast ratios met, focus states visible, semantic HTML362- [ ] SEO: meta tags, Open Graph, structured heading hierarchy
Run npx skillmds@latest add nickgallick/nick-design-system in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Nick's enterprise design system. Enforces his visual standards on every web project — typography, color, layout, spacing, components, and anti-patterns. Must be referenced before any build spec is written. Produces "Enterprise Confidence with Clean Authority" — never generic AI design. It is listed under Design & Media on SkillMD.
SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
nickgallick (@nickgallick) published this skill. Their other Agent Skills are listed on their SkillMD profile.