Skip to content
Free-first App Links

Link dock for Free Tools & App Sites

Starts with your first three and includes the broader free-first list. Every button opens in a new tab.

You can swap any URL or label directly in the anchors. All buttons are already set to open in a new tab.

How I build Beautiful $10,000 Websites with AI (AntiGravity)

VIDEO

AI-Powered Design Intelligence for Gorgeous, Modern UIs

Purpose: This framework provides a comprehensive template for prompting AI agents to create beautiful, functional, and high-performing user interfaces. Based on the UI/UX Pro Max methodology with 67+ design styles, 95+ color palettes, and proven interaction patterns.

Simply copy and paste your desired sections here 👉 https://aistudio.google.com/apps


📋 The Complete Design Prompt Template

When requesting a design from an AI agent, structure your prompt using these 5 Core Dimensions:

1. PATTERN & LAYOUT (The Skeleton)

2. STYLE & AESTHETIC (The Skin)

3. COLOR & THEME (The Palette)

4. TYPOGRAPHY (The Voice)

5. ANIMATIONS & INTERACTIONS (The Soul)



đŸ—ïž DIMENSION 1: Pattern & Layout

Don’t just say: “Create a landing page”

Instead, specify the functional pattern based on your product type:

Product-Specific Patterns

SaaS (General)

Pattern: Hero + Features + Social Proof + CTA
Focus: Value proposition first, feature showcase second
Layout: Full-width hero, 3-column features, testimonial carousel, sticky CTA

Micro SaaS

Pattern: Minimal & Direct + Live Demo
Focus: Get straight to product utility, show don't tell
Layout: Centered hero with embedded demo, minimal navigation, single CTA

E-commerce (Luxury)

Pattern: Feature-Rich Showcase + Immersive Gallery
Focus: Large imagery, high-end feel, storytelling
Layout: Full-screen hero slider, grid gallery, product details with zoom

Fintech/Crypto

Pattern: Conversion-Optimized + Trust Signals
Focus: Clear data visualization, security badges, transparent pricing
Layout: Split hero (visual + form), live stats dashboard, trust indicators

Analytics Dashboard

Pattern: Bento Grid + Actionable Insights
Focus: Data density with clarity, scannable metrics
Layout: Modular card system, hierarchical information, quick filters

Portfolio/Agency

Pattern: Storytelling + Case Studies
Focus: Visual impact, project showcases, personality
Layout: Full-screen sections, horizontal scroll galleries, immersive transitions


🎹 DIMENSION 2: Style & Aesthetic

Glassmorphism

Keywords: Frosted glass, transparent layers, blurred background, depth, vibrant backdrop
Technical: backdrop-filter: blur(10px), rgba backgrounds, layered cards
Use When: Modern apps, dashboards, overlays, modals
Avoid: Low-contrast backgrounds, accessibility issues

Aurora UI

Keywords: Vibrant gradients, smooth blend, Northern Lights effect, mesh gradient, luminous
Technical: Multi-stop gradients, animated hue rotation, glow effects
Use When: Landing pages, hero sections, creative portfolios
Avoid: Text-heavy interfaces, professional/corporate contexts

Soft UI Evolution (Neumorphism 2.0)

Keywords: Soft shadows, subtle gradients, rounded corners (12-16px), monochromatic, tactile
Technical: box-shadow: inset + outset, same-color palette, minimal contrast
Use When: Mobile apps, minimalist interfaces, wellness/health apps
Avoid: Complex data displays, accessibility-critical applications

Linear/Vercel Aesthetic

Keywords: Dark mode, subtle borders (1px), high contrast, minimalist, developer-centric
Technical: #0A0A0A background, #1A1A1A cards, #333 borders, white text
Use When: Developer tools, SaaS platforms, technical products
Avoid: Consumer-facing, playful brands

Bento Grid

Keywords: Modular, clean, organized, information-dense, modern, structured
Technical: CSS Grid, varying card sizes, consistent gaps (16-24px)
Use When: Dashboards, feature showcases, content-heavy pages
Avoid: Simple single-purpose pages

Liquid Glass

Keywords: Fluid shapes, blurred transparency, organic movement, glossy, dynamic
Technical: SVG blobs, backdrop-filter, animated transforms
Use When: Creative agencies, modern SaaS, interactive experiences
Avoid: Traditional industries, conservative audiences

Additional High-Impact Styles

  • Brutalism: Raw, bold, unconventional, high-contrast, geometric
  • Y2K Revival: Metallic, chrome effects, bold colors, retro-futuristic
  • Claymorphism: 3D inflated, soft shadows, playful, tactile
  • Gradient Mesh: Complex multi-color gradients, organic flow
  • Minimalist Luxury: Maximum white space, serif typography, subtle gold accents
  • Cyberpunk: Neon colors, glitch effects, tech-noir, high energy
  • Organic/Biomorphic: Nature-inspired shapes, earth tones, flowing forms

🎹 DIMENSION 3: Color & Theme

Specify color moods to set the right emotional tone:

Color Psychology & Palettes

Trust & Professionalism (Finance, Healthcare, Enterprise)

--primary: #0F172A (Navy)
--cta: #0369A1 (Blue)
--background: #F8FAFC (Light Grey)
--text: #1E293B (Slate)
--accent: #3B82F6 (Bright Blue)

Mood: Reliable, secure, established

Vibrant & Modern (Tech Startups, Creative Tools)

--primary: #6366F1 (Indigo)
--cta: #10B981 (Emerald)
--background: #FFFFFF (Pure White)
--text: #1E293B (Slate)
--accent: #F59E0B (Amber)

Mood: Innovative, energetic, forward-thinking

Luxury & Premium (High-end Products, Fashion)

--primary: #1C1917 (Stone Dark)
--cta: #CA8A04 (Gold)
--background: #FAFAF9 (Cream)
--text: #292524 (Warm Black)
--accent: #78716C (Taupe)

Mood: Sophisticated, exclusive, timeless

Healthcare/Wellness (Medical, Fitness, Mental Health)

--primary: #0891B2 (Cyan)
--cta: #059669 (Health Green)
--background: #FFFFFF (Clean White)
--text: #0F172A (Deep Blue)
--accent: #06B6D4 (Bright Cyan)

Mood: Calm, trustworthy, clean

Creative/Playful (Consumer Apps, Entertainment)

--primary: #EC4899 (Pink)
--cta: #8B5CF6 (Purple)
--background: #FEF3C7 (Warm Cream)
--text: #1F2937 (Charcoal)
--accent: #F59E0B (Orange)

Mood: Fun, approachable, energetic

Dark Mode Excellence

--background: #0A0A0A (True Black)
--surface: #1A1A1A (Card Background)
--border: #333333 (Subtle Borders)
--text: #FFFFFF (Pure White)
--text-secondary: #A3A3A3 (Grey)
--accent: #3B82F6 (Blue) or #10B981 (Green)

Technical: Ensure 15:1 contrast ratio for text


Color System Best Practices

✅ DO:
- Use 60-30-10 rule (60% dominant, 30% secondary, 10% accent)
- Ensure WCAG AA compliance (4.5:1 for text)
- Create semantic color tokens (--color-success, --color-error)
- Test in both light and dark modes

❌ DON'T:
- Use more than 3 primary colors
- Use pure black (#000) on pure white (#FFF) - too harsh
- Rely on color alone for information (accessibility)
- Use low-contrast grey text (#CCC on #FFF)


✍ DIMENSION 4: Typography

Font pairings create personality. Match fonts to your brand voice:

Strategic Font Pairings

Modern/Tech (SaaS, Developer Tools)

Headings: Inter (Variable Font)
Body: Roboto or System UI
Mono: JetBrains Mono (for code)

Personality: Clean, scalable, professional
Weights: 400 (regular), 600 (semibold), 700 (bold)

Elegant/Luxury (Fashion, Premium Services)

Headings: Playfair Display
Body: Montserrat
Accents: Cormorant Garamond

Personality: Sophisticated, high-contrast, editorial
Weights: 300 (light), 400 (regular), 700 (bold)

Friendly/Consumer (Apps, E-commerce)

Headings: Poppins
Body: Open Sans
Alternative: Nunito + Lato

Personality: Approachable, balanced, warm
Weights: 400 (regular), 600 (semibold), 800 (extrabold)

Brutalist/Bold (Creative Agencies, Art)

Headings: Space Grotesk
Body: JetBrains Mono or IBM Plex Sans
Alternative: Archivo Black + Work Sans

Personality: Raw, technical, unconventional
Weights: 400 (regular), 700 (bold)

Editorial/Content-Heavy (Blogs, News)

Headings: Merriweather
Body: Source Sans Pro
Alternative: Lora + Raleway

Personality: Readable, trustworthy, classic
Weights: 300 (light), 400 (regular), 700 (bold), 900 (black)



✹ DIMENSION 5: Animations & Interactions

This is what transforms “good” into “Pro Max”. Explicitly request these:

Micro-Interactions

Button Interactions

/* Hover Effects */
- Scale up: transform: scale(1.02)
- Lift: box-shadow elevation + translateY(-2px)
- Ripple: Radial gradient animation from click point
- Glow: Outer glow on hover (box-shadow with color)
- Border beam: Animated gradient border (Linear-style)

/* Timing */
- Duration: 150-300ms
- Easing: cubic-bezier(0.4, 0, 0.2, 1)

Input Focus States

/* Focus Glow */
- Ring: 2-4px outline with brand color at 50% opacity
- Glow: Soft box-shadow with brand color
- Border shift: Border color change + subtle scale
- Label float: Animated label moving up on focus

/* Accessibility */
- Always visible focus indicators
- Minimum 3px outline width
- High contrast (3:1 ratio)

Card Hover Effects

/* Premium Card Interactions */
- Lift + Shadow: translateY(-4px) + shadow increase
- Tilt: 3D perspective tilt on hover (subtle, 2-3deg)
- Glow border: Animated gradient border reveal
- Content reveal: Hidden content slides in on hover
- Image zoom: Scale image 1.05x inside container


Scroll Animations

Reveal on Scroll

// Staggered Entrance
- Fade up: opacity 0→1 + translateY(20px→0)
- Stagger delay: 100ms between elements
- Trigger: When element is 20% in viewport
- Duration: 600ms
- Easing: ease-out

Parallax Effects

// Layered Depth
- Hero background: Scroll speed 0.5x
- Foreground elements: Scroll speed 1.2x
- Subtle only: Max 20-30px movement
- Performance: Use transform, not position

Progress Indicators

/* Reading Progress */
- Top bar: Fixed position, width based on scroll %
- Circular: SVG circle with stroke-dashoffset
- Smooth: transition: width 100ms linear


Page Transitions

Route Changes

/* Smooth Navigation */
- Fade: opacity transition 200ms
- Slide: translateX(-100%→0) 300ms
- Blur: filter: blur(0→10px→0)
- Crossfade: Overlap old/new content

Modal/Dialog Animations

/* Entrance */
- Backdrop: opacity 0→1 (200ms)
- Content: scale(0.95→1) + opacity 0→1 (300ms)
- Stagger: Backdrop first, then content

/* Exit */
- Reverse animation
- Faster duration (200ms)


Loading States

Skeleton Loaders

/* Content Placeholders */
- Shimmer effect: Linear gradient animation
- Shape matching: Match final content layout
- Color: Light grey (#E5E7EB) on white
- Animation: 1.5s infinite ease-in-out

Spinners & Progress

/* Loading Indicators */
- Spinner: Rotating circle with gradient
- Progress bar: Indeterminate animation
- Pulse: Scale + opacity animation
- Duration: 1-2s infinite


Advanced Effects

Beams & Glows (Linear/Vercel Style)

/* Border Beams */
- Animated gradient border
- Conic gradient rotation
- Subtle glow effect
- Use for: CTAs, featured cards, premium elements

/* Implementation */
background: linear-gradient(90deg, transparent, #3B82F6, transparent);
animation: beam 2s infinite;

Mesh Gradients

/* Animated Backgrounds */
- Multi-color gradient mesh
- Slow hue rotation (60s+)
- Blur for organic feel
- Use for: Hero sections, backgrounds

Glassmorphism Blur

/* Glass Effect */
backdrop-filter: blur(10px) saturate(180%);
background: rgba(255, 255, 255, 0.1);
border: 1px solid rgba(255, 255, 255, 0.2);


Animation Performance Rules

✅ DO:
- Use transform and opacity (GPU accelerated)
- Set will-change for animated elements
- Use requestAnimationFrame for JS animations
- Debounce scroll events
- Prefer CSS animations over JS when possible
- Test on low-end devices

❌ DON'T:
- Animate width, height, or position
- Use animations longer than 500ms for interactions
- Animate during user input (blocks interaction)
- Use too many simultaneous animations
- Forget prefers-reduced-motion media query
- Animate on scroll without throttling


Accessibility Considerations

/* Respect User Preferences */
@media (prefers-reduced-motion: reduce) {
  * {
    animation-duration: 0.01ms !important;
    animation-iteration-count: 1 !important;
    transition-duration: 0.01ms !important;
  }
}


đŸš« Anti-Patterns: What to AVOID

Tell the agent explicitly what NOT to do:

Design Anti-Patterns

❌ Flash Over Function
- No animations that block user action
- No transitions longer than 300ms for interactions
- No auto-playing videos with sound
- No infinite scroll without pagination option

❌ Low Contrast Crimes
- No light grey (#CCC) on white backgrounds
- No pure white text on pure black (too harsh)
- Ensure WCAG AA minimum (4.5:1 for text)
- Test with color blindness simulators

❌ Over-Cluttered Chaos
- No more than 3 primary colors
- No more than 2 font families
- No more than 5 font sizes in a single view
- No inconsistent spacing (use 8px grid system)

❌ Mystery Meat Navigation
- Icons must have labels or tooltips
- No hamburger menus on desktop
- No hidden navigation without clear affordance
- No "clever" navigation that confuses users

❌ Mobile Hostility
- No tiny tap targets (minimum 44x44px)
- No horizontal scrolling (unless intentional carousel)
- No hover-dependent interactions on touch
- No fixed elements that cover content

❌ Performance Sins
- No unoptimized images (use WebP, lazy loading)
- No render-blocking resources
- No layout shifts (CLS > 0.1)
- No heavy animations on page load

UX Anti-Patterns

❌ Form Frustrations
- No labels inside inputs (accessibility issue)
- No "clear all" without confirmation
- No validation only on submit
- No disabled submit buttons (show errors instead)

❌ Content Crimes
- No walls of text without hierarchy
- No auto-playing carousels (users miss content)
- No "click here" links (not descriptive)
- No Lorem Ipsum in production

❌ Accessibility Failures
- No keyboard navigation traps
- No missing alt text on images
- No color-only information conveyance
- No auto-focus on page load (except search)


Vercel MCP:

  1. Grab API key here 👉  https://vercel.com/account/tokens
  2. Replace “INSERT_VERCEL_API_KEY” with your token.
  3. Copy and paste the below prompt.

I would like you to add the below Vercel MCP to my MCP config within Antigravity. Please confirm when this is done and that you have access.

“vercel”: { “command”: “npx”, “args”: [ “-y”, “@robinson_ai_systems/vercel-mcp” ], “env”: { “VERCEL_TOKEN”: “INSERT_VERCEL_API_KEY” } }

ui/ux skills

https://github.com/nextlevelbuilder/ui-ux-pro-max-skill.git

Gorgeous UI Dashboards

💡Metaprompt

Goal: Build a production-ready, senior-level data dashboard web app that is calm, clear, and fast. This is a tool interface, not a marketing page.

Required Tech Stack (Opinionated)

Use this stack unless impossible:

  1. Framework: Next.js 16 (App Router) + React 19 + TypeScript. (Leveraging the stable React Compiler).

  1. AI Orchestration: Vercel AI SDK. (Essential for streaming LLM responses, tool calling, and handling UI states for AI).

  1. Styling: Tailwind CSS v4.0. (Using the high-performance Oxide engine and native container queries).

  1. Component System: shadcn/ui (Radix UI Primitives).

  1. Data Layer: TanStack Query v5 (Client-side sync) + Next.js use cache (Server-side caching).

  1. Data Grid: TanStack Table v8. (For complex logs, user lists, and analytics).

  1. Validation & Forms: Zod + React Hook Form. (Unified validation for client inputs and Server Actions).

  1. Database/ORM: Drizzle ORM. (Lighter and more “Edge-ready” than Prisma for 2025 serverless environments).

  1. Authentication: Clerk or Auth.js v5. (Clerk for rapid RBAC deployment; Auth.js for self-hosted control).

  1. Security: OWASP Top 10 (2025) + Rate Limiting (via Upstash/Redis for AI endpoints).

  1. We will integrate the datasource from supabase

App Architecture Requirements

  • Use a single source of truth for data (API/database). The UI reads from query cache, not random component state.

  • Separate:

    • Server state (TanStack Query)

    • UI state (local component state)

    • Form state (React Hook Form)

  • Use Next.js App Router patterns for layout:

    • /app/(dashboard)/layout.tsx with persistent sidebar

    • route-level loading/error boundaries

    • server components for initial data where appropriate, client components for interactivity. Next.js+2Next.js+2

Design Frameworks to Apply (Non-negotiable)

  • Information Architecture (IA): Organize by user goals/decisions, not by features.

  • Cognitive Load Reduction: Reduce visual noise; make scanning effortless.

  • Progressive Disclosure: Default view is simple; advanced controls appear only when needed.

  • Perceived Performance: UI should feel instant via optimistic updates, skeletons, and non-blocking interactions.

UI/UX Specifications (Senior Bar)

1) Layout & Hierarchy

  • Strict grid; consistent spacing scale.

  • Main content dominates; navigation is visually quiet.

  • No oversized logos/banners. This is a tool.

2) Color & Token System

  • Neutral base + one accent used only for primary actions/highlights.

  • System colors:

    • red = error/destructive

    • green = success

  • Contrast must be readable. Never use color as the only indicator.

3) Navigation

  • Persistent left sidebar:

    • grouped links

    • clear active state

    • settings/logout at bottom

  • Top bar only for global page actions + global search (optional).

4) Tables (Core Dashboard Utility)

Use TanStack Table features:

  • Search + filters + sort

  • Pagination (client or server)

  • Row selection with bulk actions (selection reveals contextual toolbar)

  • Column visibility + responsive columns tanstack.com+1

5) Charts (Keep them Functional)

  • Only line and bar charts.

  • Always include axes, labels, values, gridlines.

  • Tooltips on hover.

  • Choose chart approach:

    • Use Recharts for simple “business dashboards”

    • Use ECharts if dataset is large/high-frequency updates
      (Prefer functional clarity over fancy visuals.) LogRocket Blog+2strapi.io+2

6) Interaction Patterns (Radix-backed)

  • Popover for small, non-blocking actions (display options, quick filters). radix-ui.com

  • Dialog/Modal for complex or blocking flows (create/edit item). radix-ui.com

  • Toast notifications for success/error/warning.

  • Optimistic UI for common mutations:

    • immediate UI update, rollback on failure

    • use TanStack Query optimistic updates or React’s useOptimistic pattern tanstack.com+1

7) States & Trust (Must be designed)

For every data region/component, implement:

  • Loading (skeletons)

  • Empty state (clear CTA)

  • Error state (recoverable, retry)

  • Success confirmation (toasts)
    Users should never wonder “did that work?”

Data Layer Requirements (Be Explicit)

Define:

  • Data entities (e.g., Users, Projects, Links, Events, Metrics)

  • Which endpoints power which cards/tables/charts

  • Refresh strategy:

    • polling vs websocket vs manual refresh

  • Caching rules:

    • stale time, refetch on focus, invalidation on mutation (TanStack Query)

Security & “Responsible App” Defaults

  • Enforce RBAC/permissions server-side (not just UI hiding).

  • Validate all inputs with Zod on server.

  • Avoid exposing secrets to client.

  • Add basic audit logging hooks for key actions (create/update/delete).

  • Follow OWASP Top 10 mindset: secure defaults, least privilege, safe error handling. OWASP+1

Deliverables (What you must output)

  1. A working Next.js dashboard app scaffold:

    • routes, layout, sidebar, top actions

  2. One “Dashboard Overview” page with:

    • KPI cards

    • a table with filtering/sorting/selection + bulk actions

    • a line chart + bar chart

  3. A “Create/Edit” flow:

    • modal dialog form with validation + toast + optimistic update

  4. Fully implemented loading/empty/error states

  5. Clean, consistent component patterns and tokens

Final Quality Gate

  • Understandable in <10 seconds

  • Calm, professional, data-first

  • Accessible keyboard navigation (Radix primitives help here) radix-ui.com+1

  • Fast-feeling interactions (optimistic updates + good loading UX)

💡UI Focus, Navigation

You are a senior product designer reviewing and improving an existing application UI.
Your goal is to strengthen hierarchy, focus, and navigation so the design disappears and the data becomes the hero.

Core principle

The UI should point toward the data, not compete with it.

1. Primary focus

  • Identify the single most important insight or decision this screen supports.

  • Make that element visually dominant on first glance.

  • All other elements must clearly support or defer to it.

2. Sidebar audit (critical)

Perform a full review of all sidebars (left, right, collapsible, contextual):

  • Validate the purpose of each sidebar:

    • Is it global navigation, local navigation, utilities, or context?

    • If the purpose is unclear, recommend removal or consolidation.

  • Reduce visual weight:

    • Lower contrast, lighter typography, minimal icon emphasis.

    • Sidebars should frame the content, not compete with it.

  • Evaluate item priority:

    • Remove rarely used or redundant items.

    • Group related actions and enforce clear hierarchy.

    • Highlight current location subtly, not loudly.

  • Check discoverability vs noise:

    • If something needs constant visibility, justify why.

    • Otherwise, recommend progressive disclosure or collapse.

3. Navigation discipline

  • Clearly separate global navigation from local, page-specific navigation.

  • Prevent navigation from pulling attention away from the data.

  • Navigation exists to orient, not to sell or decorate.

4. Color & focus

  • Use a neutral base palette across most UI surfaces.

  • Apply accent colors sparingly to reinforce hierarchy or active focus.

  • Reserve system colors (success, warning, error) strictly for state feedback.

5. Visual restraint

  • Identify decorative or stylistic elements that do not improve understanding.

  • De-emphasize secondary information through scale, contrast, and spacing.

  • Avoid multiple competing focal points.

6. Outcome test

At a 3-second glance, the user should instantly know:

  • what matters most

  • where to look

  • what action or insight comes next

Dynamics & Trust

You are a senior product designer and UX engineer reviewing an existing application.
Your goal is to increase user trust by improving interaction clarity, feedback, and system reliability.

Core principle

Trust is built through clear intent, immediate feedback, and consistent behavior.

1. Interaction intent

For every interactive element (filters, sorting, bulk actions, buttons):

  • Identify the user’s intent before the action.

  • Ensure the interaction communicates:

    • What will happen

    • When it will happen

    • Whether it can be undone

  • Flag any actions that feel ambiguous, surprising, or irreversible without warning.

2. Filters, sorting & bulk actions

  • Ensure filters and sorting:

    • Clearly indicate when they are active

    • Show what data is being affected

    • Update results quickly and predictably

  • Bulk actions must:

    • Confirm scope (what + how many items)

    • Prevent accidental destructive actions

    • Provide clear success or failure feedback

3. Modals vs popovers (intent matters)

  • Use modals only for:

    • Blocking decisions

    • Destructive actions

    • Multi-step or high-commitment tasks

  • Use popovers / inline UI for:

    • Quick edits

    • Previews

    • Low-risk actions

  • Flag any misuse where interruption is too heavy or too light for the action’s intent.

4. Feedback & system states

Audit all feedback mechanisms:

  • Loading states:

    • Always acknowledge input immediately

    • Show progress if delays exceed a brief threshold

  • Toasts and notifications:

    • Be concise and informative

    • Confirm outcomes, not just actions

    • Avoid stacking or flooding the user

  • Error states:

    • Explain what went wrong

    • Explain what the user can do next

    • Never blame the user

5. Speed, consistency & reliability

  • Interactions should feel:

    • Fast

    • Predictable

    • Consistent across screens

  • Identify:

    • Delayed responses without feedback

    • Inconsistent behaviors for similar actions

    • UI states that feel “uncertain” or unstable

6. Trust test

After any interaction, the user should feel:

  • “The system understood me”

  • “The system responded clearly”

  • “I can trust this to behave the same way next time”

If not, recommend changes.

Output format

Gorgeous UI Dashboards
Inspiration links plus three prompts. All links open in a new tab.
Inspiration
Dribbble shots

Tip: keep this list as a quick visual benchmark for calm, data-forward layouts and restrained navigation.

Metaprompt
Build spec
Goal: Build a production-ready, senior-level data dashboard web app that is calm, clear, and fast. This is a tool interface, not a marketing page.

Required Tech Stack (Opinionated)
Use this stack unless impossible:
Framework: Next.js 16 (App Router) + React 19 + TypeScript.
AI Orchestration: Vercel AI SDK.
Styling: Tailwind CSS v4.0.
Component System: shadcn/ui (Radix UI Primitives).
Data Layer: TanStack Query v5 (Client-side sync) + Next.js use cache (Server-side caching).
Data Grid: TanStack Table v8.
Validation and Forms: Zod + React Hook Form.
Database and ORM: Drizzle ORM.
Authentication: Clerk or Auth.js v5.
Security: OWASP Top 10 (2025) + Rate Limiting (Upstash or Redis) for AI endpoints.
Datasource: integrate the datasource from Supabase.

App Architecture Requirements
Use a single source of truth for data (API or database). The UI reads from query cache, not random component state.
Separate:
- Server state (TanStack Query)
- UI state (local component state)
- Form state (React Hook Form)

Use Next.js App Router patterns:
- /app/(dashboard)/layout.tsx with persistent sidebar
- route-level loading and error boundaries
- server components for initial data where appropriate, client components for interactivity.

Design Frameworks to Apply (Non-negotiable)
- Information Architecture: Organize by user goals and decisions, not by features.
- Cognitive Load Reduction: Reduce visual noise, make scanning effortless.
- Progressive Disclosure: Default view is simple, advanced controls appear only when needed.
- Perceived Performance: UI should feel instant via optimistic updates, skeletons, non-blocking interactions.

UI and UX Specifications (Senior Bar)
1) Layout and Hierarchy
- Strict grid, consistent spacing scale.
- Main content dominates, navigation is visually quiet.
- No oversized logos or banners. This is a tool.

2) Color and Token System
- Neutral base + one accent used only for primary actions and highlights.
- System colors:
  - red = error or destructive
  - green = success
- Contrast must be readable. Never use color as the only indicator.

3) Navigation
- Persistent left sidebar:
  - grouped links
  - clear active state (subtle)
  - settings and logout at bottom
- Top bar only for global page actions and optional global search.

4) Tables (Core Dashboard Utility)
Use TanStack Table features:
- Search + filters + sort
- Pagination (client or server)
- Row selection with bulk actions (selection reveals contextual toolbar)
- Column visibility + responsive columns

5) Charts (Keep them Functional)
- Only line and bar charts.
- Always include axes, labels, values, gridlines.
- Tooltips on hover.
Choose chart approach:
- Recharts for simple business dashboards
- ECharts if dataset is large or high-frequency updates
Prefer functional clarity over fancy visuals.

6) Interaction Patterns (Radix-backed)
- Popover for small, non-blocking actions (display options, quick filters).
- Dialog and modal for complex or blocking flows (create and edit item).
- Toast notifications for success, error, warning.
- Optimistic UI for common mutations:
  - immediate UI update, rollback on failure
  - use TanStack Query optimistic updates or React’s useOptimistic pattern

7) States and Trust (Must be designed)
For every data region and component, implement:
- Loading (skeletons)
- Empty state (clear CTA)
- Error state (recoverable, retry)
- Success confirmation (toasts)
Users should never wonder “did that work?”

Data Layer Requirements (Be Explicit)
Define:
- Data entities (e.g., Users, Projects, Links, Events, Metrics)
- Which endpoints power which cards, tables, charts
Refresh strategy:
- polling vs websocket vs manual refresh
Caching rules:
- stale time, refetch on focus, invalidation on mutation (TanStack Query)

Security and “Responsible App” Defaults
- Enforce RBAC and permissions server-side (not just UI hiding).
- Validate all inputs with Zod on server.
- Avoid exposing secrets to client.
- Add basic audit logging hooks for key actions (create, update, delete).
- Follow OWASP Top 10 mindset: secure defaults, least privilege, safe error handling.

Deliverables (What you must output)
A working Next.js dashboard app scaffold:
- routes, layout, sidebar, top actions
- One “Dashboard Overview” page with:
  - KPI cards
  - a table with filtering, sorting, selection + bulk actions
  - a line chart + bar chart
- A “Create and Edit” flow:
  - modal dialog form with validation + toast + optimistic update
- Fully implemented loading, empty, error states
- Clean, consistent component patterns and tokens

Final Quality Gate
- Understandable in under 10 seconds
- Calm, professional, data-first
- Accessible keyboard navigation
- Fast-feeling interactions (optimistic updates + good loading UX)
UI Focus, Navigation
Designer audit
You are a senior product designer reviewing and improving an existing application UI.
Your goal is to strengthen hierarchy, focus, and navigation so the design disappears and the data becomes the hero.

Core principle
The UI should point toward the data, not compete with it.

1. Primary focus
Identify the single most important insight or decision this screen supports.
Make that element visually dominant on first glance.
All other elements must clearly support or defer to it.

2. Sidebar audit (critical)
Perform a full review of all sidebars (left, right, collapsible, contextual):
Validate the purpose of each sidebar:
- Is it global navigation, local navigation, utilities, or context?
- If the purpose is unclear, recommend removal or consolidation.
Reduce visual weight:
- Lower contrast, lighter typography, minimal icon emphasis.
Sidebars should frame the content, not compete with it.
Evaluate item priority:
- Remove rarely used or redundant items.
- Group related actions and enforce clear hierarchy.
Highlight current location subtly, not loudly.
Check discoverability vs noise:
- If something needs constant visibility, justify why.
- Otherwise, recommend progressive disclosure or collapse.

3. Navigation discipline
Clearly separate global navigation from local, page-specific navigation.
Prevent navigation from pulling attention away from the data.
Navigation exists to orient, not to sell or decorate.

4. Color and focus
Use a neutral base palette across most UI surfaces.
Apply accent colors sparingly to reinforce hierarchy or active focus.
Reserve system colors (success, warning, error) strictly for state feedback.

5. Visual restraint
Identify decorative or stylistic elements that do not improve understanding.
De-emphasize secondary information through scale, contrast, and spacing.
Avoid multiple competing focal points.

6. Outcome test
At a 3-second glance, the user should instantly know:
- what matters most
- where to look
- what action or insight comes next
Dynamics and Trust
UX engineer audit
You are a senior product designer and UX engineer reviewing an existing application.
Your goal is to increase user trust by improving interaction clarity, feedback, and system reliability.

Core principle
Trust is built through clear intent, immediate feedback, and consistent behavior.

1. Interaction intent
For every interactive element (filters, sorting, bulk actions, buttons):
Identify the user’s intent before the action.
Ensure the interaction communicates:
- What will happen
- When it will happen
- Whether it can be undone
Flag any actions that feel ambiguous, surprising, or irreversible without warning.

2. Filters, sorting and bulk actions
Ensure filters and sorting:
- Clearly indicate when they are active
- Show what data is being affected
- Update results quickly and predictably
Bulk actions must:
- Confirm scope (what and how many items)
- Prevent accidental destructive actions
- Provide clear success or failure feedback

3. Modals vs popovers (intent matters)
Use modals only for:
- Blocking decisions
- Destructive actions
- Multi-step or high-commitment tasks
Use popovers or inline UI for:
- Quick edits
- Previews
- Low-risk actions
Flag any misuse where interruption is too heavy or too light for the action’s intent.

4. Feedback and system states
Audit all feedback mechanisms:
Loading states:
- Always acknowledge input immediately
- Show progress if delays exceed a brief threshold
Toasts and notifications:
- Be concise and informative
- Confirm outcomes, not just actions
- Avoid stacking or flooding the user
Error states:
- Explain what went wrong
- Explain what the user can do next
- Never blame the user

5. Speed, consistency and reliability
Interactions should feel:
- Fast
- Predictable
- Consistent across screens
Identify:
- Delayed responses without feedback
- Inconsistent behaviors for similar actions
- UI states that feel uncertain or unstable

6. Trust test
After any interaction, the user should feel:
- The system understood me
- The system responded clearly
- I can trust this to behave the same way next time
If not, recommend changes.

Output format
List specific interaction improvements.
Explain how each change increases trust.
Do not add new features, only refine interaction clarity, feedback, and consistency.