Crappy Presentations — Bold Orange Studio

Cream-and-orange agency site built from huge black grotesque type, flat color blocks, and hand-drawn doodle mascots.

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

Design notes

Mood

Loud, confident, a little irreverent — an agency that wants you to smile before you buy.

Colors

Cream base #FAF6EC, near-black text/logo #121212, vivid orange block #EE6C2E, white #FFFFFF, small yellow accent badge #F5D949.

Type

A heavy, rounded grotesque (like Poppins ExtraBold or General Sans Bold) at huge sizes with tight tracking for headlines; simple, small sans body text for contrast.

Layout

Big centered hero statement, full-bleed orange block housing a numbered accordion list (01-04), stacked two-column proof/portfolio sections, rotated sticker-badge callouts breaking the grid.

Motion

Accordion items expand and collapse on click; rotated badge callouts suggest a hand-placed tilt; simple hover/scale states on buttons and cards.

Texture

Flat solid color blocks with zero gradients, black hand-drawn doodle illustrations, pill buttons with arrow icons, no drop shadows — everything flat and graphic.

Imagery

Generate: black hand-drawn line-art doodle mascots (a triangle character, jigsaw puzzle pieces, a sunglasses-wearing figure) and colorful flat-graphic presentation-slide thumbnails. Tool: kie-ai GPT-Image or nanobanana for the illustrated line-art style; no photography needed.

Don't

No gradients, no photographic hero imagery, no muted or desaturated colors, no serif type, no soft pastel tones.

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: Crappy Presentations — Bold Orange Studio Source: https://www.crappypresentations.com/ Swipefile reference: https://swipefile.design/ref/crappypresentations/ 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: Loud, confident, a little irreverent — an agency that wants you to smile before you buy. - colors: Cream base #FAF6EC, near-black text/logo #121212, vivid orange block #EE6C2E, white #FFFFFF, small yellow accent badge #F5D949. - typography: A heavy, rounded grotesque (like Poppins ExtraBold or General Sans Bold) at huge sizes with tight tracking for headlines; simple, small sans body text for contrast. - layout: Big centered hero statement, full-bleed orange block housing a numbered accordion list (01-04), stacked two-column proof/portfolio sections, rotated sticker-badge callouts breaking the grid. - motion: Accordion items expand and collapse on click; rotated badge callouts suggest a hand-placed tilt; simple hover/scale states on buttons and cards. - texture: Flat solid color blocks with zero gradients, black hand-drawn doodle illustrations, pill buttons with arrow icons, no drop shadows — everything flat and graphic. - dont: No gradients, no photographic hero imagery, no muted or desaturated colors, no serif type, no soft pastel tones. ## 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.