QlooVibe Find your direction

YOUR PROJECT IS THE STARTING POINT

Good design
starts with
your TASTE.

Tell us what you’re building. Paste a description, README or design.md.
Explore design directions you can take straight to your coding agent.

Shape my project

Your context. Qloo taste data. A direction you can build.

A TASTE OF WHAT’S POSSIBLESTUDY / 01
INDEPENDENT SPIRIT
Less noise.
More feeling.
TYPE EXPLORATIONCharacter
meets clarity.
A little unexpected.
Entirely intentional.
THE COLOR STORY05 SWATCHES

Illustrative studies. Generate directions for your project below.

FROM CULTURE TO CREATIVE DIRECTIONColor palettes ↗Typography ↗Spacing & motion ↗Ready-to-use CSS ↗

What are you building?

Checking service…

Markdown or plain text · 20–8,000 characters. The file is read into the text box for review.

Include what it does, who it serves and how it should feel. Your text goes to a language model (Groq, with Cloudflare Workers AI as backup) to suggest references; those names go to Qloo for audience data.

Your text gives us context. Qloo supplies cultural relationships; our published design rules turn them into colors, type and spacing.

No account needed
Behind your brief Follow the data

Request details

After you create a brief, see which Qloo requests succeeded, were cached, or failed.

How it works

01

Check the audience.

Describe your project or enter references directly. Review the matched names before using a direction, especially when we suggested them.

02

Compare the choices.

Explore up to three palettes, font pairs and spacing systems. Each direction shows which choices came from audience data and which use defaults.

03

Use it in your build.

Copy the design brief to your coding agent or download the CSS. You can also check references and audit code against your chosen direction.

A starting point, with the sources to back it up.

Qloo provides taste relationships and descriptors, not colors or fonts. Our design mapping is a hypothesis, not a prediction of what every person will prefer. Every choice shows its source; choices without enough evidence are labeled as defaults.

Text and interface contrast pairs are checked. The completed interface still needs its own accessibility review. No language model writes the design tokens. Rule version: qv-rules-1.0.

How we tested the method