Style gallery
Bold playful
Chunky rounded type, saturated two-color palette, illustrated characters, sticker-style badges
Light · Vivid playful · General brand · static site
A starting style vibld wrote for consumer, education, kids, creator sites. Chunky rounded type, saturated two-color palette, illustrated characters, sticker-style badges.
Build in this styleRead the build prompt
In the builder, open Gallery under the message and search for Bold playful.
What makes it
- chunky rounded headlines at 800 weight
- coral and blue on a cream canvas
- pill buttons with a hard offset shadow
- sticker-style badges, slightly tilted
Colors
Chunky rounded type, saturated two-color palette, illustrated characters, sticker-style badges.
- canvas
#fff8ec - surface
#ffffff - text / primary action label / link text / focus ring
#1e1b2e - muted text
#5e5873 - accent / primary action fill
#ff5a36 - divider (decorative), never behind text
#e4ddd5 - second accent
#3b5bff
Every checked pair, measured again
| Sample | Where | Ratio | Needs |
|---|---|---|---|
| Aa | body text on canvas | 15.89:1 | 4.5:1 |
| Aa | body text on surface | 16.78:1 | 4.5:1 |
| Aa | muted text on canvas | 6.38:1 | 4.5:1 |
| Aa | muted text on surface | 6.73:1 | 4.5:1 |
| Aa | primary action label on fill | 5.41:1 | 4.5:1 |
| Aa | link text on canvas | 15.89:1 | 4.5:1 |
| focus ring on canvas | 15.89:1 | 3:1 | |
| focus ring on surface | 16.78:1 | 3:1 | |
| second accent marks on canvas | 4.82:1 | 3:1 |
Typefaces
modular scale 1.414; no text below 12px
- NunitoHeadings
- FigtreeBody
Type scale
102px Nunito 800
72px Nunito 800
51px Nunito 800
36px Nunito 800
25px Figtree 500
18px Figtree 400
16px Figtree 400
14px Figtree 400
12px Figtree 400
Corners and shadows
- cards:
20px - images:
20px - inputs:
20px - buttons:
20px
No shadows: depth comes from surfaces and lines.
Spacing and imagery
comfortable density on a 4px base unit; container 1200px; section gap 80px; radius 20px
Placeholder or generated imagery only; partner marks are neutral placeholders.
Layout
- navigation: Pill-shaped floating nav, centered, with the action inside the pill.
- hero: Headline split over two lines with one word highlighted in a marker swash, illustration on the right, action as a pill button with a hard drop shadow.
- social proof: Review cards tilted slightly, star ratings, avatars as illustrations when no photo consent exists.
- pricing: Two plans at most, free and paid, toggle styled as a big switch.
- footer with grouped link columns and a legal line
- content sits in a 1200px centered container with 24px side padding (16px on mobile)
- sections are separated by 80px of vertical space on desktop, roughly half that on mobile
Patterns
- navigation
- hero
- social proof
- pricing
Components
- primary button: fill #ff5a36, label #1e1b2e; 20px radius; padding 14px 24px; type 16px/600
- card: surface fill; 20px radius; padding 24px
Interactions and states
- links underline on hover
- every interactive element shows a 2px #1e1b2e focus ring with 2px offset
- all motion is disabled under prefers-reduced-motion
- hover, focus-visible, active and disabled states for every button style
- mobile menu open and closed states
- forms: inline validation, sending, success and retryable error
Guardrails
Experience
- Keep one primary action style (#ff5a36 fill, #1e1b2e label) and use it once per view.
- The navigation follows its rule: Pill-shaped floating nav, centered, with the action inside the pill.
- The hero follows its rule: Headline split over two lines with one word highlighted in a marker swash, illustration on the right, action as a pill button with a hard drop shadow.
- The social proof follows its rule: Review cards tilted slightly, star ratings, avatars as illustrations when no photo consent exists.
- The pricing follows its rule: Two plans at most, free and paid, toggle styled as a big switch.
- Avoid corporate blue.
- Avoid thin 300-weight type.
- Avoid dense tables.
- Every number, quote, rating and partner mark is a placeholder the owner replaces; never invent real customers, logos or results.
Accessibility
- Text, links, focus rings and input borders use only the verified pairs listed in contrast checks.
- Focus ring: 2px solid #1e1b2e with 2px offset on every interactive element.
- Body text is 16px or larger at 1.5 line height; nothing is smaller than 12px.
- Decorative colors never carry text or the only signal of state.
- Respect prefers-reduced-motion; no autoplay video without a pause control.
Security
- Validate every form on the client and again on the server; reject unknown fields.
- Open external links with rel="noopener noreferrer" and never put secrets or API keys in client code.
Build prompt
The rules every style in the gallery assumes, then this style’s own ten sections, from goal to guardrails. A build in the style also gets its tokens as a file, so the colors and type above are exact.
The rules every style assumes
### How to use these prompts Paste an entry's build prompt into your coding agent as the first message. Each prompt names its own stack, tokens and acceptance criteria; the rules below apply to all of them and can be prepended once per project. ### Engineering baseline - TypeScript strict mode, no `any`, small typed components, feature folders, and one source of truth for design tokens (CSS variables consumed by Tailwind). - Validate every input with a shared zod schema on the client and again on the server or edge function. Never trust client-side checks alone. - Show loading, empty and error states for every async view. Surface errors in plain language with a retry, and log details to the console in development only. - Keep secrets out of the bundle. Only publishable keys (for example a Supabase anon key) belong in client code; service-role keys, API keys and webhooks live in server or edge-function environment variables. ### Data and auth baseline - Enable Row Level Security on every table before inserting data. Default-deny, then add the narrowest policies the feature needs (for a lead form: insert-only for anonymous users, select for a staff role). - Store roles in a separate table checked by a security-definer function, never in a user-editable profile field. - Rate-limit public endpoints (forms, auth, AI calls) and add a honeypot field or captcha to anonymous forms. - Take payments through a hosted checkout and verify webhooks by signature. Never handle raw card data. ### Accessibility and UX baseline - Target WCAG 2.2 AA: 4.5:1 contrast for normal text and 3:1 for large text, input borders, focus rings and meaningful icons or chart lines. Every palette in this catalog lists its verified pairs; re-check with a contrast tool after any color change. - Keep body text at 16px or larger with 1.5 line height, nothing below 12px, no light weights under 24px, and uppercase only for short labels. - Give every interactive element a visible focus ring, full keyboard support, semantic landmarks, labeled form fields, and alt text on meaningful images. - Respect `prefers-reduced-motion` for every animation. Give carousels and drag interactions keyboard and button alternatives, and never auto-advance them. - Build mobile-first and test at 375px, 768px and 1280px. ### Content guardrails - Use original copy, fictional sample data and placeholder or generated imagery. Do not reuse another product's name, logo, screenshots or marketing text. - Partner and customer logo rows use neutral placeholder marks. Label demo testimonials and metrics as samples. Collect the minimum personal data a form needs. ### Style preset baseline - Treat the entry's palette, type scale, radii, spacing and shadows as the complete token set. Do not introduce new colors; derive hover and pressed states by moving one step lighter or darker within the same hue, then re-check contrast. - Colors marked decorative (dividers, supporting accents) never sit behind text and never carry meaning on their own. - Fonts are open Google Fonts chosen to match the observed letterforms. Self-host them with `font-display: swap` and keep to the listed weights. - Keep the signature moves listed for the entry, and keep everything else quiet so they stay recognizable. - One primary action style per view. Secondary actions are outlined or text-only, and links are distinguishable by more than color (underline or weight).
### Goal
Build a responsive light-theme site in the "Bold playful" starting style: Chunky rounded type, saturated two-color palette, illustrated characters, sticker-style badges. Write all copy fresh for the product in the request.
### Stack
Use the stack the request and the project already have. Design tokens live as CSS variables mapped into the Tailwind theme.
### Pages & layout
Home page sections, in order:
- navigation: Pill-shaped floating nav, centered, with the action inside the pill.
- hero: Headline split over two lines with one word highlighted in a marker swash, illustration on the right, action as a pill button with a hard drop shadow.
- social proof: Review cards tilted slightly, star ratings, avatars as illustrations when no photo consent exists.
- pricing: Two plans at most, free and paid, toggle styled as a big switch.
- footer with grouped link columns and a legal line
- content sits in a 1200px centered container with 24px side padding (16px on mobile)
- sections are separated by 80px of vertical space on desktop, roughly half that on mobile
Leave out pricing when the product has none to show. Test at 375px, 768px and 1280px.
### Design system
```css
:root {
--color-canvas: #fff8ec;
--color-surface: #ffffff;
--color-text: #1e1b2e;
--color-muted-text: #5e5873;
--color-accent: #ff5a36;
--color-divider: #e4ddd5;
--color-second-accent: #3b5bff;
--text-12: 12px;
--text-14: 14px;
--text-16: 16px;
--text-18: 18px;
--text-25: 25px;
--text-36: 36px;
--text-51: 51px;
--text-72: 72px;
--text-102: 102px;
--radius: 20px;
--space-unit: 4px;
--container: 1200px;
}
```
Fonts: display Nunito, body Figtree (Google Fonts, self-hosted).
Type scale (size/weight/line-height tracking): 12px/400/1.5, 14px/400/1.5, 16px/400/1.5, 18px/400/1.5, 25px/500/1.4, 36px/800/1.18 -0.020em, 51px/800/1.12 -0.020em, 72px/800/1.06 -0.020em, 102px/800/1 -0.020em.
Spacing: comfortable density on a 4px base unit; container 1200px; section gap 80px; one corner radius, 20px, on cards, images, inputs and buttons.
Signature moves: chunky rounded headlines at 800 weight; coral and blue on a cream canvas; pill buttons with a hard offset shadow; sticker-style badges, slightly tilted.
### Components & interactions
- **primary button**: fill #ff5a36, label #1e1b2e; 20px radius; padding 14px 24px; type 16px/600
- **secondary button**: transparent fill, 1px border in the text color, 20px radius
- **card**: surface fill, 20px radius, padding 24px
- links underline on hover
- every interactive element shows a 2px #1e1b2e focus ring with 2px offset
- navigation collapses to a menu sheet under 768px, trapping focus while open
### Data & state
Content comes from typed local data. Handle hover, focus-visible, active and disabled states for every button, the mobile menu open and closed, and form validation, sending, success and error.
### Accessibility
- Text, links, focus rings and input borders use only the verified pairs listed in contrast checks.
- Focus ring: 2px solid #1e1b2e with 2px offset on every interactive element.
- Body text is 16px or larger at 1.5 line height; nothing is smaller than 12px.
- Decorative colors never carry text or the only signal of state.
- Respect prefers-reduced-motion; no autoplay video without a pause control.
Verified contrast: body text on canvas #1e1b2e on #fff8ec = 15.89:1; body text on surface #1e1b2e on #ffffff = 16.78:1; muted text on canvas #5e5873 on #fff8ec = 6.38:1; muted text on surface #5e5873 on #ffffff = 6.73:1; primary action label on fill #1e1b2e on #ff5a36 = 5.41:1; link text on canvas #1e1b2e on #fff8ec = 15.89:1; focus ring on canvas #1e1b2e on #fff8ec = 15.89:1; focus ring on surface #1e1b2e on #ffffff = 16.78:1; second accent marks on canvas #3b5bff on #fff8ec = 4.82:1.
### Security
- Validate every form on the client and again on the server; reject unknown fields.
- Open external links with rel="noopener noreferrer" and never put secrets or API keys in client code.
### Performance & SEO
- Images with explicit width and height, lazy-loaded below the fold; preload the display font only.
- One h1 per page, a descriptive title and meta description.
### Guardrails
- Keep one primary action style (#ff5a36 fill, #1e1b2e label) and use it once per view.
- The navigation follows its rule: Pill-shaped floating nav, centered, with the action inside the pill.
- The hero follows its rule: Headline split over two lines with one word highlighted in a marker swash, illustration on the right, action as a pill button with a hard drop shadow.
- The social proof follows its rule: Review cards tilted slightly, star ratings, avatars as illustrations when no photo consent exists.
- The pricing follows its rule: Two plans at most, free and paid, toggle styled as a big switch.
- Avoid corporate blue.
- Avoid thin 300-weight type.
- Avoid dense tables.
- Every number, quote, rating and partner mark is a placeholder the owner replaces; never invent real customers, logos or results.