Stripe Press — 3D Book Shelf

A publisher's whole catalog as one floating 3D stack — each spine a lit, physical object you scrub through against near-black.

Source capture · 2026-09-05Open full image ↗

Content & mediaCreative toolsMotion

Design notes

Mood

A rare-books room after hours. Reverent, tactile, quietly technical — objects presented like museum pieces.

Colors

Near-black warm charcoal ground (#1D1715), each book carries its own saturated jacket color; tiny white serif UI text. Light comes from the objects, not the page.

Type

Small italic serif for the wordmark and tagline ('Ideas for progress'); titles live ON the book spines in engraved serif/sans mixes. Page chrome is nearly typeless — a left rail of tick marks as a scroll index.

Layout

One centered column of floating 3D volumes stacked with even air between them, seen at a slight top-down angle. A minimal left-edge index rail tracks position; no header band, no sections — the shelf is the site.

Motion

Scroll scrubs the shelf: books glide past, tilt, and catch light as they pass center. Physical easing, as if the stack has mass. Hovering a spine lifts it slightly.

Texture

Cloth, debossed foil and paper-grain materials under a soft key light; true shadows beneath each volume; subtle reflection on the ground plane.

Imagery

The 3D book renders ARE the imagery: physically-lit volumes with cloth/foil spine materials, each in its own jacket palette (parchment yellow, slate blue, oxblood). Tool: build real WebGL/Three.js book meshes or kie-ai Seedream renders of spines composited on the dark ground. No flat book-cover thumbnails.

Don't

No flat 2D cover grids, no white background, no card UI around the books, no text sections between objects — the objects carry everything.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withAny AI toolCodexClaudeCursorChatGPTGeminiv0 / LovableI want toBuild a screenAudit my UIWrite a design brief

Tech stackUse the existing project stackReact / Next.jsAstroVue / NuxtSvelte / SvelteKitHTML / CSS / JavaScriptSwiftUIFlutter

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text# My project [Describe the product, audience, and screen you want to improve] Stack: Use the existing project stack Task: Implement the interface and verify the result in the existing project. ## Tool guidance (Any AI tool) Use available project tools to inspect, implement, and test. State any unavailable capabilities. # Design reference: Stripe Press — 3D Book Shelf Source: https://press.stripe.com Swipefile reference: https://swipefile.design/ref/stripe-press/ Captured: 2026-09-05. This is a dated reference, not a claim about the current live product. Capture scope: a page excerpt. Do not infer unseen sections or interactions. ## Objective Adapt the visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets. ## Reference notes - mood: A rare-books room after hours. Reverent, tactile, quietly technical — objects presented like museum pieces. - colors: Near-black warm charcoal ground (#1D1715), each book carries its own saturated jacket color; tiny white serif UI text. Light comes from the objects, not the page. - typography: Small italic serif for the wordmark and tagline ('Ideas for progress'); titles live ON the book spines in engraved serif/sans mixes. Page chrome is nearly typeless — a left rail of tick marks as a scroll index. - layout: One centered column of floating 3D volumes stacked with even air between them, seen at a slight top-down angle. A minimal left-edge index rail tracks position; no header band, no sections — the shelf is the site. - motion: Scroll scrubs the shelf: books glide past, tilt, and catch light as they pass center. Physical easing, as if the stack has mass. Hovering a spine lifts it slightly. - texture: Cloth, debossed foil and paper-grain materials under a soft key light; true shadows beneath each volume; subtle reflection on the ground plane. - dont: No flat 2D cover grids, no white background, no card UI around the books, no text sections between objects — the objects carry everything. ## Acceptance criteria - Existing project conventions, design tokens, working functionality, and unrelated changes are preserved. - Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product. - Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap. - Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled. - Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported. - Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service. ## Quality bar Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Copy promptDownload .md

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.