Minimal landing page redesign

[ponderingdemocritus]

Summary

Radically simplified all 4 client landing pages to minimal dark terminal aesthetic. Removed marketing copy, focused on routing (games/entrypoints), pricing, and supporting protocols.

Changes

• lucid-docs: Marketing site reduced from ~600 to 150 lines. Hero + games table + protocols grid + footer only.
• CLI adapters: TanStack headless/UI and Next.js dashboards restyled with dark monospace theme, table layouts, sharp edges.
• All functionality preserved: health polling, payments, invoke/stream, wallet integration.

Design

Dark theme (zinc-950), monospace typography, 1px borders, emerald accents for prices, no rounded corners or gradients. Added landing.html HTML prototype for reference.

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

This PR radically simplifies all four client landing pages — the docs marketing site, Next.js dashboard, TanStack UI dashboard, and TanStack headless adapter — replacing the previous gradient/rounded card aesthetic with a minimal dark terminal style (zinc-950 background, monospace type, 1px borders, emerald accents). A static landing.html prototype is also added as a design reference.

Key changes:

• lucid-docs/src/routes/index.tsx: ~600-line marketing page reduced to ~150 lines. The new layout introduces a custom <header> with logo and nav links rendered inside HomeLayout, which already provides a site-wide Fumadocs header — this will produce duplicate navigation on the page and needs to be resolved before merging.
• packages/cli/adapters/next/components/dashboard.tsx: Entrypoints now expand/collapse via <details>; hero section surfaces agent metadata. HealthCard and WalletSummary are stripped of their own styling via !important overrides to fit the inline header bar.
• packages/cli/adapters/tanstack/ui/src/routes/index.tsx: Entrypoints use a click-to-expand accordion pattern driven by a new expandedEntry state. All functional paths (invoke, stream, cancel, copy curl) are preserved.
• packages/cli/adapters/tanstack/headless/src/routes/index.tsx: Minimal list view updated to match the new style; rows show cursor-pointer without a click handler, giving misleading interactivity cues.

Confidence Score: 3/5

• Not safe to merge until the duplicate header issue in lucid-docs is resolved — it will produce double navigation on the primary marketing page.
• The three CLI adapter files are in good shape (scores 4–5) and the redesign intent is clear and well-executed. However, the docs marketing page (the most user-visible surface) has a likely P1 bug: a custom header rendered inside HomeLayout will double-up the site navigation. That single issue affects the primary user path for the landing page and warrants holding off on merge until confirmed or fixed.
• lucid-docs/src/routes/index.tsx — verify that the custom <header> inside HomeLayout does not duplicate the Fumadocs site header.

Important Files Changed

Filename	Overview
lucid-docs/public/landing.html	New static HTML prototype matching the redesign aesthetic. Well-structured with design tokens, responsive breakpoints, and self-contained styling. Serves as a reference file only.
lucid-docs/src/routes/index.tsx	Marketing home page redesigned from ~600 to ~150 lines. A custom <header> with logo/nav is rendered inside HomeLayout, which already renders its own site header via baseOptions() — this will produce visually duplicate navigation on the page.
packages/cli/adapters/next/components/dashboard.tsx	Next.js dashboard restyled with terminal aesthetic; entrypoints now use <details> expand pattern. Minor: conflicting transition-colors/transition-transform classes on the row arrow span will suppress the color animation.
packages/cli/adapters/tanstack/headless/src/routes/index.tsx	Headless adapter updated to match the new dark terminal style. Rows carry cursor-pointer without any click handler, giving misleading interactivity cues, but otherwise functionally correct.
packages/cli/adapters/tanstack/ui/src/routes/index.tsx	TanStack UI dashboard restyled; expand/collapse now driven by a single expandedEntry state (one-at-a-time). All functional paths (invoke, stream, cancel, copy curl) preserved. Clean refactor with no logic regressions spotted.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["User visits /"] --> B["HomeLayout (Fumadocs)"]
    B --> C["Built-in Fumadocs Header\n(logo + nav from baseOptions())"]
    B --> D["Page Content div"]
    D --> E["⚠️ Custom <header>\n(lucid. + docs + github)"]
    E --> F["Hero Section\nAgent commerce infrastructure"]
    F --> G["Games Table\n6 rows → /docs/examples"]
    G --> H["Protocols Grid\nx402 · A2A · ERC-8004 · SIWX · MPP"]
    H --> I["Footer\nMIT · chains"]

    style E fill:#f87171,color:#fff
    style C fill:#34d399,color:#000

Loading

Comments Outside Diff (3)

1. lucid-docs/src/routes/index.tsx, line 544-575 (link)

   Duplicate header inside HomeLayout

   A custom <header> element containing the logo, docs link, github link, and status indicator is now rendered inside HomeLayout. Fumadocs' HomeLayout already renders a site-wide navigation header configured via baseOptions(). This will result in two stacked headers on the page — the Fumadocs nav on top and this new custom one below.

   The old code relied entirely on HomeLayout for the top navigation. If the intent is to replace the Fumadocs header with this custom one, HomeLayout should be swapped for a bare layout wrapper, or the baseOptions() nav should be configured to null/false to suppress the built-in header. Otherwise, the page will have visually duplicate navigation.

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: lucid-docs/src/routes/index.tsx
   Line: 544-575
   
   Comment:
   **Duplicate header inside `HomeLayout`**
   
   A custom `<header>` element containing the logo, docs link, github link, and status indicator is now rendered inside `HomeLayout`. Fumadocs' `HomeLayout` already renders a site-wide navigation header configured via `baseOptions()`. This will result in two stacked headers on the page — the Fumadocs nav on top and this new custom one below.
   
   The old code relied entirely on `HomeLayout` for the top navigation. If the intent is to replace the Fumadocs header with this custom one, `HomeLayout` should be swapped for a bare layout wrapper, or the `baseOptions()` nav should be configured to `null`/`false` to suppress the built-in header. Otherwise, the page will have visually duplicate navigation.
   
   How can I resolve this? If you propose a fix, please make it concise.

2. packages/cli/adapters/next/components/dashboard.tsx, line 1372 (link)

   Conflicting transition-* classes cancel out color transition

   Both transition-colors and transition-transform are applied to the same element. Because both utilities set the CSS transition shorthand property, whichever one is generated later in Tailwind's stylesheet will win — in practice this means transition-transform takes effect and the group-hover:text-emerald-500 color change will no longer animate smoothly.

   Replace both with transition-all, or use the single combined utility that covers both:

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: packages/cli/adapters/next/components/dashboard.tsx
   Line: 1372
   
   Comment:
   **Conflicting `transition-*` classes cancel out color transition**
   
   Both `transition-colors` and `transition-transform` are applied to the same element. Because both utilities set the CSS `transition` shorthand property, whichever one is generated later in Tailwind's stylesheet will win — in practice this means `transition-transform` takes effect and the `group-hover:text-emerald-500` color change will no longer animate smoothly.
   
   Replace both with `transition-all`, or use the single combined utility that covers both:
   
   
   
   How can I resolve this? If you propose a fix, please make it concise.

3. packages/cli/adapters/tanstack/headless/src/routes/index.tsx, line 1553-1583 (link)

   cursor-pointer with no click handler creates misleading UX

   The row <div> carries cursor-pointer in its class list, implying it is interactive, but there is no onClick handler attached. In the headless adapter, there is no expand/detail panel wired up, so clicking a row does nothing. Removing cursor-pointer (or replacing it with cursor-default) would avoid confusing users who expect the rows to be actionable.

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: packages/cli/adapters/tanstack/headless/src/routes/index.tsx
   Line: 1553-1583
   
   Comment:
   **`cursor-pointer` with no click handler creates misleading UX**
   
   The row `<div>` carries `cursor-pointer` in its class list, implying it is interactive, but there is no `onClick` handler attached. In the headless adapter, there is no expand/detail panel wired up, so clicking a row does nothing. Removing `cursor-pointer` (or replacing it with `cursor-default`) would avoid confusing users who expect the rows to be actionable.
   
   
   
   How can I resolve this? If you propose a fix, please make it concise.

Prompt To Fix All With AI

This is a comment left during a code review.
Path: lucid-docs/src/routes/index.tsx
Line: 544-575

Comment:
**Duplicate header inside `HomeLayout`**

A custom `<header>` element containing the logo, docs link, github link, and status indicator is now rendered inside `HomeLayout`. Fumadocs' `HomeLayout` already renders a site-wide navigation header configured via `baseOptions()`. This will result in two stacked headers on the page — the Fumadocs nav on top and this new custom one below.

The old code relied entirely on `HomeLayout` for the top navigation. If the intent is to replace the Fumadocs header with this custom one, `HomeLayout` should be swapped for a bare layout wrapper, or the `baseOptions()` nav should be configured to `null`/`false` to suppress the built-in header. Otherwise, the page will have visually duplicate navigation.

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: packages/cli/adapters/next/components/dashboard.tsx
Line: 1372

Comment:
**Conflicting `transition-*` classes cancel out color transition**

Both `transition-colors` and `transition-transform` are applied to the same element. Because both utilities set the CSS `transition` shorthand property, whichever one is generated later in Tailwind's stylesheet will win — in practice this means `transition-transform` takes effect and the `group-hover:text-emerald-500` color change will no longer animate smoothly.

Replace both with `transition-all`, or use the single combined utility that covers both:

```suggestion
                <span className="text-sm text-zinc-700 transition-all group-hover:text-emerald-500 inline-block group-hover:translate-x-0.5">
```

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: packages/cli/adapters/tanstack/headless/src/routes/index.tsx
Line: 1553-1583

Comment:
**`cursor-pointer` with no click handler creates misleading UX**

The row `<div>` carries `cursor-pointer` in its class list, implying it is interactive, but there is no `onClick` handler attached. In the headless adapter, there is no expand/detail panel wired up, so clicking a row does nothing. Removing `cursor-pointer` (or replacing it with `cursor-default`) would avoid confusing users who expect the rows to be actionable.

```suggestion
                className="grid grid-cols-[1fr_120px_100px] items-center border-b border-[#1a1a1a] transition-colors hover:bg-[rgba(34,197,94,0.08)] hover:border-[#2a2a2a]"
```

How can I resolve this? If you propose a fix, please make it concise.

_{Last reviewed commit: "refactor: redesign l..."}

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	lucid-agents	1b57f2b	Commit Preview URL Branch Preview URL	Mar 21 2026, 12:05 PM