OMORO Style Library

Build an authentic multi-style blend from two to five Omoro styles. The first two styles anchor the visual direction; added styles are treated as influence layers. Returns defining rendering techniques, visible contribution requirements, fidelity checks, palette and three coordinated mockup prompts: one hero and two distinct supporting applications, presented as a large hero left and two stacked applications right.

Build an original character brief grounded in Omoro styles. Returns an Omoro Characters-compatible JSON file and a detailed image prompt; it does not generate images or save anything to an account. Import the JSON at omoro.io/characters to keep editing there.

Create a separate Omoro-designed style guide, palette/type sheet, or application brief for one style or a user-selected blend. Its visual system is grounded in each style's documented rendering techniques, palette, typography, and composition. This does not change blend_styles' established hero plus two supporting mockups.

Build a concrete UI Lab direction brief from a product archetype, visual language, Omoro style and optional palette. Returns layout geometry, palette roles, typography/material guidance, keep/avoid rules and a paste-ready prompt.

Put two styles side by side: their attribute profiles with the gap on each axis, their palettes, and their documented periods. Use it to explain how two visual languages actually differ.

Rank palettes by their closest swatch to a supplied hex colour. Use when a user has a brand colour or image-derived hex and needs compatible Omoro palettes.

Rank styles by how closely they sit to a target visual position. Give only the axes you care about; the rest are ignored rather than assumed. Each axis runs -1 to 1. This answers questions prose cannot, such as which styles are simultaneously minimal, cool, geometric and digital.

One reference brand or design system to work from: its verified palette with roles and usage, typefaces with free alternatives, tokens (type scale, spacing, radius, grid, motion), principles and sources. format "skill" returns a SKILL.md an assistant can follow (or the user can save), "prompt" a short paste-in prompt, "data" the raw values. Make the user's own work in its spirit; never copy logos or trademarks.

Retrieve one named Omoro palette by slug, including its parent style, mood and five named hex swatches.

Show the Omoro MCP welcome guide, including how to search styles and palettes, build UI directions, and create an original character with the character builder.

The full record for one style: palette with named swatches, the eight-axis attribute profile, typography pairing, documented period and origin, visual markers, related styles, a canonical hero image, and the page's labelled visual gallery.

List the reference brand systems and public design systems Omoro has documented from official sources (e.g. Aesop, Stripe, IKEA, IBM Carbon, Material 3): slug, name, kind, category, a one-line summary and key colours. Use get_brand_system for one in full.

List Omoro's named colour palettes. Optionally narrow to a parent style. Each result includes a palette name, mood, parent style and five named hex swatches.

List documented aesthetic styles. Optionally narrow by mood group or category. Returns the short listing: slug, name, url, group, a one-line summary and the five palette hex codes.

List the product archetypes and visual languages supported by Omoro UI Lab. Use this before building a direction when you need to choose the right interface structure.

Free-text search across palette names, parent styles and mood descriptions. Use this for queries such as "quiet warm studio" or "nightclub neon".

Free-text search across style names and summaries. Use when you know roughly what you are looking for but not the slug. For finding styles by visual character rather than by name, find_styles_by_attributes is the better tool.

Return three distinct, Omoro-grounded brand routes for a user. First translate only supported personal taste signals into numeric taste_axes, include the exact known palette and known brand_context, then call this tool. Each route includes an automatically selected style blend, signature visuals, positioning and message framework, and voice guidance. Use Omoro for the page frame only; let each blend's defining features lead its route. Present all three as choices and do not invent missing brand facts or collapse the options into one generic style.

Suggest the simplest Omoro landing-page or WebGL direction for a user's goal. Returns a recommended layout, an optional interactive scene, and a few calibration questions before building.