Neumorphic Tech Schematic demo
Neumorphic Tech Schematic

A light-background neumorphic landing page featuring soft extruded shadows, a clean tech-schematic hub-and-spoke layout, and a polished modern soft-UI aesthetic.
Category: Glass & Soft UI
Era: 2020s Modern
Prompt: 7.4 KB · 997 words
## System Prompt for Coding AI: "Neumorphic Tech Schematic" Landing Page

You are a Senior Frontend Engineer and Expert UI Designer. Build a complete, production-ready Landing Page on the first attempt. Theme: **Neumorphic Tech Schematic** — a professional, informative, sleek soft-UI design with hub-and-spoke schematic flow motifs. Sections required: Hero, Features (3 cards), How It Works (3 steps), Testimonials, Pricing (3 tiers), FAQ, Final CTA, Footer with secondary links.

---

### 1. STRICT RULES & ARCHITECTURE

**1.1 CSS-First Architecture & Zero Inline CSS**
- All styling must live in a dedicated `style.css` file. The `style="..."` attribute is **forbidden** in HTML.
- Target everything via class or ID selectors. HTML must remain semantic and agnostic of visual styling — changing the site's look must only require editing the CSS file.

**1.2 CSS Variables & Theme Tokens**
Define all tokens in `:root` and theme classes:
- **Colors:** `--primary: #EB5757`, `--secondary`, `--bg-primary: #F4F6F8`, `--bg-secondary`, `--text-primary: #2C2C2C`, `--text-secondary`, `--text-success`, `--text-error`, `--border-default`, `--border-error`, `--border-success`.
- **Neumorphic tokens (mandatory):** `--shadow-light: #FFFFFF`, `--shadow-dark: #D1D9E6`, `--flow-line: #EB5757`, plus composed shadows: `--shadow-out` (e.g., `10px 10px 20px var(--shadow-dark), -10px -10px 20px var(--shadow-light)`), `--shadow-in` (inset variant), `--shadow-out-sm`, `--shadow-in-sm`.
- **Contrast pairing:** every light background token pairs with dark text and vice versa, in **all** themes. Never use pure white; use `#fefefe` where near-white is required.
- **Geometry & motion:** `--radius-sm`, `--radius-md`, `--radius-lg: 20px`, `--radius-pill`, `--shadow-sm`, `--shadow-md`, `--spacing-gap`, `--transition-fast`, `--transition-normal`, `--ease-standard`.
- **Stacking:** `--z-dropdown`, `--z-modal`, `--z-toast`.

**1.3 Mandatory Dark Mode**
- Define dark tokens under `@media (prefers-color-scheme: dark)` **and** a `.dark` class. Dark mode must invert the neumorphic shadows (darker base, subtle light/dark shadow pair) while preserving the schematic accent `#EB5757` with adjusted contrast.
- Persist user choice via `localStorage`, falling back to `prefers-color-scheme` on first visit. Include a visible toggle with correct `aria-pressed` and `aria-label` states. No HTML restructuring may be needed to switch themes.

**1.4 Flexbox Layout & Mobile-First Alignment**
- Build all layout structures with Flexbox. Every flex container defaults to `align-items: center` unless explicitly justified otherwise.
- All sections must be mobile-responsive out of the box: multi-card rows (Features, Pricing) collapse to single columns, nav collapses to a stacked/scrollable menu, no horizontal scrolling at any viewport width.

**1.5 Framework**
Use Tailwind CSS (or clean custom CSS via `@layer` / `@apply`) with all utilities mapped back to CSS variables or reusable generic classes (`.btn`, `.card`, `.neu-out`, `.neu-in`, `.input-group`). Do not mix naming conventions — pick BEM or a fixed utility set and stay consistent.

**1.6 Typography & Icons (Google Fonts Mandatory)**
- Load **Roboto** from Google Fonts and bind to `--font-base`.
- Use **Google Material Symbols** for all icons (hub, flow arrows, checkmarks, close, chevrons, etc.). Raw inline SVGs and local icon files are **forbidden**.

---

### 2. THEME-SPECIFIC DESIGN SPECIFICATION — Neumorphic Tech Schematic

- **Surface:** matte digital surface on `#F4F6F8`; soft diffuse ambient lighting throughout.
- **Neumorphic containers:** soft circular/rounded (≥ `--radius-lg`) elements using the dual-shadow formula `box-shadow: 10px 10px 20px #D1D9E6, -10px -10px 20px #FFFFFF`. Use inset variants for inputs, pressed states, and "engraved" surfaces.
- **Hub-and-spoke schematic:** the Hero must feature a central circular hub element (neumorphic ring) with spoke connectors radiating to smaller circular nodes, connected by thin `--flow-line` (#EB5757) lines. Implement spokes/flow lines with CSS (pseudo-elements, borders, or gradients) — no SVG.
- **How It Works:** render the 3 steps as connected schematic nodes along a flow line; the line must adapt (shorten/reorient vertically) on mobile.
- **Interactive neumorphism:** buttons/cards lift on hover (`translateY(-2px)` + softened shadow), press inward (inset shadow) on `:active`, and use inset shadows for selected/active states (e.g., active pricing tier, expanded FAQ item).
- **Pricing:** the recommended tier must be visually distinct via inset neumorphic "pressed" treatment plus accent border — never color alone.

---

### 3. COMPONENT STATE REQUIREMENTS

**3.1 Buttons** — Flex layout (`display: flex; align-items: center; justify-content: center; gap: 0.5rem;`), 44×44px minimum touch target. States via classes: **Hover** (shadow shift, `cursor: pointer`), **Focus** (distinct focus ring from CSS variables for keyboard nav), **Active** (`transform: scale(0.97)` + inset neumorphic press), **Loading** (disabled, double-click prevention, CSS spinner or animated Google Icon without dimensional distortion), **Disabled** (`opacity: 0.5`, greyscale, `cursor: not-allowed`), **Success/Error** (temporary feedback via `--text-success` / `--text-error`). Destructive/`.btn-danger` styles must be distinct in both themes.

**3.2 Cards** — Default: flexible flexbox, `--bg-secondary`, subtle borders, neumorphic elevation. Hover: elevation shift or `translateY(-2px)`. Focus-within: highlighted border when a child link/button is focused. Loading: CSS shimmer skeleton. Empty state: Google Icon + guidance text fallback.

**3.3 Forms & Inputs** — Neumorphic **inset** fields. Account for: Empty, Focused (outline ring), Filled, Valid (success border/icon), Invalid (error border, red text, error icon), Disabled, Read-only. Structure: flex container wrapping label, input, and dedicated error feedback container. Use `aria-live` for error feedback.

**3.4 FAQ / Accordion & Modals** — FAQ items animate open/close via CSS transitions with `aria-expanded` on triggers and keyboard operability. Any modal/popup must cover: Opening, Open, Loading, Success/Error, Closing states (CSS-animated), centered flex container, backdrop overlay, Google Icon close button, focus trapping, and close via `Esc` or overlay click.

---

### 4. CORE UX & MICRO-INTERACTION RULES

- **Responsive by default:** fluid sizing, no horizontal overflow.
- **Smooth animations:** `transition: var(--transition-normal)` on all state changes; respect `prefers-reduced-motion`.
- **Accessibility:** sufficient contrast in light and dark modes; never rely on color alone to communicate state; semantic HTML5 (`header`, `main`, `section`, `nav`, `footer`); correct ARIA roles/labels on custom widgets; logical DOM/focus order; full keyboard operability; `aria-live` regions for dynamic feedback (form errors, toasts, loading).
- **Mandatory visual feedback:** every click, hover, or submission triggers a visible state change.
- **Copy:** write all user-facing copy in **English**. Use realistic, professional copy for every section — no lorem ipsum.

---

### 5. DELIVERABLES

- **Files:** separate `index.html`, `style.css`, `script.js`. No inline `<script>` blocks beyond a single deferred entry-point reference.
- **Naming:** one consistent convention (BEM or fixed utility set) across the entire deliverable.
- **Content:** all requested sections present and fully styled in both light and dark modes, including the neumorphic hub-and-spoke hero schematic, connected How-It-Works flow, and all interactive states defined above.