Aurora UI

You are building a web application using Next.js with Tailwind.
Read existing project instructions and reuse installed components where available.

## Project
Project brief: Not specified
Target users: Not specified
Page purpose: SaaS
Framework: Next.js
CSS approach: Tailwind
UI library: Custom / no library
Tone: Professional

## Visual direction
Base theme: Aurora UI (visual-effect)
- Soft ambient gradient glows behind elements
- Aurora-like color transitions from purple to teal to pink
- Frosted glass panels over gradient backgrounds
- Subtle animated color shifts suggesting movement
- Dark base palette with luminous accent areas
- Depth created through layered translucent surfaces

## Resolved style
Use this final token set. It already includes the selected layers. These values take precedence over conflicting base characteristics.
Color palette: primary #7C3AED, secondary #2DD4BF, accent #F472B6, background #0F0B1A, text #E2E8F0
Typography: Plus Jakarta Sans for headings, Inter for body text
Load the declared fonts with the required weights. Use system fallbacks when a font is unavailable.
```css
:root {
  --tx-surface-bg: #0F0B1A;
  --tx-font-heading: "Plus Jakarta Sans", sans-serif;
  --tx-font-body: "Inter", sans-serif;
  --tx-surface-bg-image: radial-gradient(ellipse 80% 50% at 30% 50%, rgba(124,58,237,0.12), transparent), radial-gradient(ellipse 50% 40% at 70% 30%, rgba(45,212,191,0.08), transparent);
  --tx-card-bg: rgba(255,255,255,0.04);
  --tx-card-border: rgba(255,255,255,0.08);
  --tx-card-border-width: 1px;
  --tx-card-radius: 1rem;
  --tx-card-shadow: 0 4px 24px rgba(124,58,237,0.1);
  --tx-card-backdrop-blur: 12px;
  --tx-card-border-hover: rgba(124,58,237,0.3);
  --tx-card-shadow-hover: 0 8px 32px rgba(124,58,237,0.15);
  --tx-font-heading-weight: 700;
  --tx-font-body-weight: 400;
  --tx-text-muted: rgba(226,232,240,0.7);
  --tx-text-subtle: rgba(226,232,240,0.5);
  --tx-link-color: #7C3AED;
  --tx-button-radius: 0.75rem;
  --tx-input-bg: rgba(255,255,255,0.05);
  --tx-input-border: rgba(255,255,255,0.1);
  --tx-text: #E2E8F0;
  --tx-primary: #7C3AED;
  --tx-secondary: #2DD4BF;
  --tx-accent: #F472B6;
  --tx-media-filter: none;
}
```
Use the CSS variables in your own components. Apply the heading and body font variables to their respective elements.

## Layout
- Keep gradients behind solid or translucent content panels.

## Interaction
- Animate background color slowly and stop background motion when reduced motion is requested.

## Suitability notes
Use these limitations to assess the chosen page purpose. Explain any mismatch before applying an unsuitable treatment.
- Aurora UI: Long reading pages with animated backgrounds behind text.

## Components
Generate the following components in this style:
- Hero
- Navbar
- Cards
- Footer

## Quality requirements
Choose section order and visual emphasis from the real content and page purpose. Add only sections needed for the task.
Use supplied content. Label sample data. Do not invent testimonials, customer logos, statistics, or compliance claims.
Every interactive control must perform its declared action or be clearly labeled as a demo.
Include loading, empty, error, success, disabled, and focus states where applicable.
Use semantic HTML, visible keyboard focus, readable text contrast, and labeled form fields.
Ensure responsive design (mobile-first). Preserve reading order and avoid horizontal page overflow.
Respect prefers-reduced-motion. Keep essential content visible when animations are disabled.

## Verification
Check representative desktop and mobile widths, keyboard interaction, and relevant component states. Run available project checks and report what was actually verified.
Use Tailwind utility classes with the declared tokens.
Product context is incomplete. Label assumptions and treat the result as a draft until the missing context is supplied.