Check the audience.
Describe your project or enter references directly. Review the matched names before using a direction, especially when we suggested them.
YOUR PROJECT IS THE STARTING POINT
Tell us what you’re building. Paste a description, README or design.md.
Explore design directions you can take straight to your coding agent.
Your context. Qloo taste data. A direction you can build.
Illustrative studies. Generate directions for your project below.
Your text gives us context. Qloo supplies cultural relationships; our published design rules turn them into colors, type and spacing.
No account neededAfter you create a brief, see which Qloo requests succeeded, were cached, or failed.
Describe your project or enter references directly. Review the matched names before using a direction, especially when we suggested them.
Explore up to three palettes, font pairs and spacing systems. Each direction shows which choices came from audience data and which use defaults.
Copy the design brief to your coding agent or download the CSS. You can also check references and audit code against your chosen direction.
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.