RED × Neynar · Clanker

Clanker redesign — engineering handoff

The Clanker redesign, handed over cleanly. Two surfaces so far — the token-detail page and the token-creation flow — each a self-contained section here, both built on one design system. Everything is tagged so you know exactly where to build to spec and where you have room to adapt. This explorer grows page by page; the system is the spine and only grows, it doesn't fork.

NEYN-12112 · token detailNEYN-12118 · token creationSurface: clanker.world · web · desktop + mobileDesign: RED
Detail Token-detail page — NEYN-12112 · the reference surface
🖥️
The live page
The working prototype. Three token states (established / early / fresh), light + dark, desktop + mobile. Toggle states via the ⚙ FAB, bottom-right.
Open the prototype →
📐
Page spec
The token page's anatomy: every region mapped to a component, the full state matrix, the interaction inventory, and the data contract (real vs mock).
Open the spec →
🎨
Design system
The shared styleguide — tokens + every component, rendered from the same CSS the pages ship. One system for both sections; this is where every class is spec'd.
Open the system →
Create Token-creation flow — NEYN-12118 · the /deploy journey
🚀
The live page
The create/deploy form (+ success and deployments). One Token form with an opt-in tokenized-agent section; wallet-first; four add-ons; live preview; hard-block validation. Light + dark, desktop + mobile.
Open the prototype →
📐
Page spec
The creation flow's anatomy: every region + step, the state matrix (agent on/off, wallet, chain, pool/fee mode, add-ons), the interaction inventory, and the inverse data contract (form → record → receipt).
Open the spec →
🎨
Design system
The same shared styleguide — the creation components (form fields, dropzone, option chips, agent toggle, summary card, reward builder) live in §13–§15 under the same tokens.
Open the system →

01The one thing to internalise: Locked vs Adapt vs Global

This handoff's job is to make your job easier — to not make you guess — while leaving you room to adapt where reality demands it. So every token, component and region carries one of three tags:

🔒 Locked
Build to spec. The visual system — tokens, the chip / badge / button family, type, spacing, radius, and the core interaction states. Matching these exactly is what keeps the whole app reading as one product. If you think one needs to change, change it in the design system first.
🔧 Adapt
Direction set, details flex. Real data wiring, exact copy, error/empty/loading handling, performance, and anything backend. Keep the shape and the states; adapt the plumbing to ground truth.
🌐 Global · in flux
Shared, and expected to move. The nav and footer are global components (spec'd once in the design system, referenced by both page specs). What's here is a strong, considered proposal — but input from the other pages will very likely reshape them. Build them modular; don't hard-couple page logic to their current form.
Quick test: visual + reusable → Locked.   touches live data or a backend → Adapt.   nav or footer → Global-in-flux.

02How this handoff is built to scale

This is deliberately structured as a template so pages drop into the same shape without re-litigating the system. The token-detail page came first; the token-creation flow is the second surface, and it slotted into the exact same structure — the proof the template works:

03What this prototype is (and isn't)

Read this before you open the source, so you calibrate what to take literally.

04The state model

Each surface renders from independent axes on <body data-*> (in the prototype you flip them via review chrome; in production they come from data + auth). The token-detail axes:

AxisValuesDrivesIn production, comes from
data-viewervisitor · adminShows/hides the Admin button + drawer and the update composer.Is the connected wallet the token admin?
data-agentagent · noagent · v1lockedThe Agent section, and whether social (Farcaster/X) feed rows + filters show.The token's on-chain + agent config.
data-agefresh · early · establishedThe token-age risk banner + which of the three token pages you're on.Pool age / trade history depth.
data-themelight · darkPalette. Toggled by the on-page ☀/☾ control; persists.User preference.

The token-creation flow has its own axis set (full detail in the creation spec §02):

AxisValuesDrivesIn production, comes from
data-walletconnected · disconnectedWallet-first auth: every CTA becomes “Connect Wallet”; admin + first reward recipient prefill from the address.Privy / wallet connection.
data-agentoff · onReveals the inline tokenized-agent section (+ preview sub-card + ToC item); CTA → “Clank + Agent”.Did the creator opt in? (Base-only.)
chainBase · 6 moreRe-derives pair token, reward type, sniper default, start mcap, agent + preclank availability.Creator's chain choice.
fee / poolstatic·dynamic / rec·legacyFee tier active vs dimmed; starting mcap locked vs editable.Creator's choices.
data-themelight · darkPalette. Same control, drives every page.User preference.
Why three separate token pages (detail)? established = $CLANKER (mature, agent), early = $AIRGAP (thin, cast-only, zero trades), fresh = $BRIAN (just-launched, no agent). They're the eval set — proof the same page adapts to very different tokens. The creation flow is a single /deploy page whose sections recompute from the chain + agent axes.

05Region-by-region: what's locked, what adapts

The two page specs drill into each region; this is the combined map. Full component specs (with live examples) are in the design system. The canonical region detail for each surface lives in that surface's spec §01 Anatomy (detail · creation).

RegionSectionStabilityNotes for engineering
Nav (logo, search, theme toggle, Launch, hamburger/account menu, scrolled collapsed masthead)Both🌐 GlobalStrong proposal; expect change. The account menu (connected/disconnected wallet states) mirrors clanker.world's Privy menu. On creation, the nav Launch CTA cross-links to /deploy; wallet-first identity lives here, not on a primary CTA.
Masthead / identity (avatar, name, verified, agent status, address, handles)Detail🔒 🔧Layout + the three agent-status states locked. Address full desktop / truncated mobile. Data + copy adapt.
Chart · Activity · Evidence · Swap consoleDetail🔒 🔧All interaction states locked (row/expand, swap focus, one-box no-divider). Live data + quoting + wallet connect are Adapt. Timeline is under review — build decoupled.
Create form (identity · description · fees · rewards · pool/supply · add-ons)Create🔒 🔧Field set, validation UX (MFLOW), the one-chip selectors, the hard-block deploy order + hidden-section skipping are locked. Chain ground truth (7 chains) is verified from the live form. Real chain deploy is Adapt.
Tokenized-agent section (inline opt-in, name/voice/model/mode/platforms/funding)Create🔒 shape · 🔧 wireLayout + Base-only gating + the “Proposed” tag are locked. Inference model (venice.ai now / OpenRouter soon) is chosen & recorded; the inference backend + X-API-key linking are Adapt.
Live preview rail → success receipt → deploymentsCreate🔒 🔧The inverse fill (form → window.TOKEN-shaped preview → launch record → receipt) is locked. Fixtures/runway are mock → Adapt to real records.
ToC / stepper (hanging section index, 3 responsive tiers)Create🔒Per-section state (done/todo/invalid/opt/na), scrollspy, and the ≥1320 / 1040–1319 / drawer tiers are locked. See creation spec §01.
FooterBoth🌐 GlobalGlobal; expect change. Columns + socials + legal are a proposal.
RED · NEYN-12112 (token detail) + NEYN-12118 (token creation) · This handoff is a living artifact — the design system is the single source of truth; if the build forces a change, reflect it there first so the system and the app never drift. Questions → RED.