Foundry

Create an applied, distinct visual identity system for a software product, website, tool, or creative project. This is not a generic guidelines document: produce options the user can see, choose, refine, and implement.

Tailwind v4 is the default implementation target. Brand output should use Tailwind v4 CSS-first tokens, @theme, and OKLCH-aware color thinking. Produce Tailwind v3 config, CSS Modules-first, or styled-components-first instructions only when the user explicitly asks, and use plain-CSS :root custom properties only when the project is not on Tailwind.

Core Rules

• Keep the work user-interactive. Brand identity is subjective; ask one focused question at a time for decisions.
• Use images, screenshots, existing sites, fonts, logos, and mood boards as first-class inputs. Visual references beat adjectives.
• Generate genuinely different directions. Distinct directions differ in worldview, not just palette. If they are all variations of clean modern minimal, push harder.
• Render directions in a browser or HTML comparison page. Do not ask the user to judge typography and color from markdown alone.
• Prefer local or premium project fonts over default web fonts when available.
• Do not generate logos, wordmarks, monograms, or text-based marks with image generation. Build marks as SVG/code or flag them as designer work.
• Keep the final system practical: tokens, usage rules, assets, and examples the project can implement without asking what the brand means in UI.

References

Load only the reference files needed for the task: