Coolors — Palette generator

Creative ToolsSee it livecoolors.co

Five large color columns make a palette the primary workspace rather than a small preview.

Coolors — Palette generator — captured interface — Viewport capture · opening screen

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

Creative tools

Why this pattern works

Let direct color comparison dominate the screen and keep utility actions at its edges.

Design notes

Surface: Palette generator
Navigation: Viewing, export, and save controls occupy a compact toolbar above the palette.
Layout: Equal-width swatches fill the page with hexadecimal values near the base of each column.
Density: The working preview takes most of the space, with compact controls grouped around it.
Color: The selected five-color palette provides almost the entire visual surface.
Type: Use minimal labels on large swatches so hue relationships remain easy to judge.
Pattern: Let direct color comparison dominate the screen and keep utility actions at its edges.
States: A public palette URL after dismissing onboarding; no account or saved palette was created.
Don't: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

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 withI want to

Tech stack

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: Coolors — Palette generator
Source: https://coolors.co/301a4b-6db1bf-ffeaec-f39a9d-3f6c51
Swipefile reference: https://swipefile.design/ref/coolors-palette/
Captured: 2026-09-04. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Palette generator
- nav: Viewing, export, and save controls occupy a compact toolbar above the palette.
- layout: Equal-width swatches fill the page with hexadecimal values near the base of each column.
- density: The working preview takes most of the space, with compact controls grouped around it.
- color: The selected five-color palette provides almost the entire visual surface.
- typography: Use minimal labels on large swatches so hue relationships remain easy to judge.
- pattern: Let direct color comparison dominate the screen and keep utility actions at its edges.
- states: A public palette URL after dismissing onboarding; no account or saved palette was created.
- dont: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

Useful for: Let direct color comparison dominate the screen and keep utility actions at its edges.

## 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.

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

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Let direct color comparison dominate the screen and keep utility actions at its edges.

Coolors — Palette generator

Make it your own

Keep exploring