Pixel / 8-bit

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: Games & entertainment
Framework: Next.js
CSS approach: Tailwind
UI library: Custom / no library
Tone: Professional

## Visual direction
Base theme: Pixel / 8-bit (visual-style)
- Pixel art and short bitmap headings
- Square panels with stepped borders and offset shadows
- A limited palette with clear status labels
- Deliberate spacing that follows a small consistent grid

## Resolved style
Use this final token set. It already includes the selected layers. These values take precedence over conflicting base characteristics.
Color palette: primary #5B21B6, secondary #0F766E, accent #FBBF24, background #F0E7FF, text #2E1065
Typography: Press Start 2P for headings, Space Mono for body text
Load the declared fonts with the required weights. Use system fallbacks when a font is unavailable.
```css
:root {
  --tx-surface-bg: #F0E7FF;
  --tx-font-heading: "Press Start 2P", sans-serif;
  --tx-font-body: "Space Mono", sans-serif;
  --tx-surface-bg-image: none;
  --tx-card-bg: #FFFFFF;
  --tx-card-border: #2E1065;
  --tx-card-border-width: 3px;
  --tx-card-radius: 0;
  --tx-card-shadow: 4px 4px 0 #2E1065;
  --tx-card-backdrop-blur: 0px;
  --tx-card-border-hover: #111111;
  --tx-card-shadow-hover: 6px 6px 0 #2E1065;
  --tx-font-heading-weight: 400;
  --tx-font-body-weight: 400;
  --tx-text-muted: #4C1D95;
  --tx-text-subtle: #5B21B6;
  --tx-link-color: #5B21B6;
  --tx-button-radius: 0;
  --tx-input-bg: #FFFFFF;
  --tx-input-border: #2E1065;
  --tx-text: #2E1065;
  --tx-primary: #5B21B6;
  --tx-secondary: #0F766E;
  --tx-accent: #FBBF24;
  --tx-media-filter: none;
}
```
Use the CSS variables in your own components. Apply the heading and body font variables to their respective elements.

## Layout
- Use square panels, stepped shadows, and a limited palette with consistent spacing.
- Use bitmap fonts only for short headings. Keep controls large enough for touch input.

## Interaction
- Use short stepped button states. Avoid flashing effects and provide static alternatives to sprite motion.

## Suitability notes
Use these limitations to assess the chosen page purpose. Explain any mismatch before applying an unsuitable treatment.
- Pixel / 8-bit: Long reading pages and formal workflows that need neutral typography.

## 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.