Changelog

A brand you can steer

August was mostly about the space you work in: finding things, seeing where you are up to, and making a brand look like yours from the first screen.

A setup checklist on the brand overview#

A new brand now opens on a checklist rather than an empty dashboard, so the next useful thing to do is always on screen. The overview is quieter for it, with the panels that were competing for attention pulled back.

Browse the whole brand from the command menu#

The command menu searches your components, blocks, and tokens, and your rule groups and individual rules. Results carry enough context to tell two similarly named rules apart. Connecting an AI tool is now an action in there too, rather than something you go looking for.

Your logo, wherever the brand is named#

An organization can upload its own logo, and a brand shows its logo everywhere it is named. The organization switcher also shows which plan you are on.

Import a shadcn preset#

Bring a shadcn style preset into a brand, and the brand records the shadcn configuration its previews render under, so component examples preview under your own tokens rather than the default theme.

Brand settings#

Brands have their own settings screen, where a brand's own lifecycle lives, including taking a brand and its live projects to the trash.

Rule search that finds the right rules

search_rules used to return nothing for the kind of multi-word request an agent naturally forms from a task, and single words returned hundreds of unranked rules. Both are fixed, in one piece of work.

What changed#

• Synonyms. A curated list expands your terms, so a search for login also finds rules written about sign in and authentication. The list is versioned with the code, and an expanded term always ranks below the word you actually typed.
• Relevance ranking. Results are scored on how much of your query a rule really covers, rather than on matching any single common word.
• A floor, and an honest empty result. Below a confidence threshold the search returns no rules and names the terms that matched nothing, instead of filling the response with whatever scored above zero. An agent can now tell a miss from a hit, which it could not before.
• Scope and limit. The tool takes optional section and limit arguments, and results are capped, with required rules protected from the cap so a broad query cannot drop the mandatory ones.

A task description like "login form with email and password fields" now returns a ranked, capped set you can build from.

Docs launched

Published the UI Rules documentation site, covering brands, styles, library, rules, projects, the agent, connecting AI tools over MCP, and organization, account, and billing.