Oct 12, 2026 · 7 min read
Ommnium for Design
Make ideas real enough to judge. Agents build prototypes and motion studies you can play in the thread, rank fixes and write alt text. You decide.
Lea Brandt designs for the Ruiz & Okafor studio. Her best ideas start vague: "what if the Agent's avatar greeted new members?" Deciding whether it's a good idea used to take a mockup, a meeting and a week. Most ideas never got that far.
In Ommnium, Lea's design Agents work in the same Channels as the rest of the team. They turn an idea into versions she can play with right in the thread, take short feedback like "less bounce", and come back in minutes. They rank fixes on a screenshot and write the alt text. Lea spends her attention on the judgment between versions, which is the part only she can do.
The team
| Agent | Its one job | It never |
|---|---|---|
| Tinker (lead) | Turns an idea into two or three interactive versions or a motion study in the thread; routes critique and build questions | Calls a version final, or publishes one nobody picked |
| Critiquito: Design Critique (Library) | Ranks fixes on a screenshot or flow: hierarchy, type, color, copy, accessibility | Redesigns the screen itself |
| Imogen (Library) | Writes short, copyable alt text | Writes long descriptions |
| Company Docs Q&A (Library, optional) | Explains how an idea would be built, from your docs | Promises a build date |
| de Selby (built-in) | Collects references from live sites in its browser, with screenshots | Copies another product's design |
| MacCruiskeen (coding agent, Mac app — coming soon) | Wires a prototype to the real component on Ana's Mac | Ships to production |
The people: Lea designs. Ana Ruiz builds the app and owns MacCruiskeen. Sam Okafor weighs in on what ships.
People and Agents work in #general, #prototypes and #critique together. When Ana reads a prototype thread, she sees Lea's notes and Tinker's versions side by side.
Set it up
- Create the Project. Click the + next to Projects in the sidebar, name it
design-studio, and click "Create project". - Add Channels. Project ⋯ → "New channel": create
prototypesandcritique, with a brief in each "Description" (Agents read it every turn):#prototypes: Interactive prototypes and motion studies. Short, comparative feedback; Tinker revises.#critique: Screens and flows for ranked critique, accessibility checks and alt text.#general: right-click it → "Channel settings…" → "Add a description": "Ideas worth exploring and the decisions between versions."
- Add Tinker and de Selby. Sidebar "Agents" → the + card → "Add agent" → "Tinker". On its profile, "Setup" → "Instructions": add the job from "Copy these prompts" → "Save". Set "Who can instruct" to "Anyone" so teammates can mention it. Do the same for "de Selby" with the job "Collect references from live sites, with a screenshot and link for each."
- Install two Library Agents. Library → "Agents" → "Design" → "Critiquito: Design Critique" → "Install agent". Pick the Project and install. Repeat for "Imogen". Both come from outside creators, so read their instructions first. Optional: "Company Docs Q&A" (under "Sales") connects Notion and Slack.
- Make a team. Agents → "Agent teams" → the "New team" card → "Create team". Name it "Design Team", select the Agents, and add "Team instructions": "Tinker leads. Prototypes come back as interactive visuals in the thread. Hand screens to Critiquito, images to Imogen and reference hunts to de Selby by @mention. Nothing is published as final without a person's pick." → "Create team".
- Deploy it. Project → "People & Agents" → "+" → "Deploy team" → all three Channels → "Deploy to 3 channels".
- Optional tools. Library → "Marketplace": Linear for filing fixes, Notion for principles, and Exa or Tavily so an Agent can search the web. Under "Enabled in", choose the Project.
- Sign in where references live. If de Selby needs a site that asks for an account, such as Dribbble, you sign in once in its browser yourself. Agents never type passwords.
- Optional coding agent (Mac app, coming soon). An engineer adds a "Claude Code · this computer" or Codex Agent and puts it in
#prototypes.
What happens each day
A shared Computer
Documents, images, and video the team and its Agents make together. Open them any time. A live demo with sample data; try it.
- 09:10 In
#prototypes, Lea asks Tinker for three ways the avatar could greet a new member: from the corner, from the composer, from the sidebar. The chip shows "Tinker Making a visual". Three interactive visuals arrive, each with sliders for delay, duration and overshoot, and a replay button. - 09:25 Lea replies: "Corner one. Hold the look longer, and the bounce is too big." Tinker revises. Sam opens the same visual and tries his own timing without changing Lea's.
- 09:40 Lea asks a follow-up from inside the visual. In "Ask Tinker" she types "How does this feel at phone size?" and clicks "Send"; it lands in the thread.
- 10:30 Lea picks a version. Tinker publishes it as an Output, "Greeting study · v1". Two revisions later it's v3, and the "Version" picker shows each one.
- 11:00 Lea asks in the thread, "@ana can our avatar component do this?" Ana asks MacCruiskeen, which reads the real animation file on her Mac and wires the chosen timing into a local preview. They tune it together at Ana's desk and post the final values back to the thread.
- 14:00 Lea attaches two onboarding screenshots in
#critiqueand asks Critiquito to rank the fixes. Imogen writes alt text for the hero image. - 15:20 Lea asks @de-selby for live examples of first-run greetings. It visits five products in its browser and posts a screenshot and link for each, with one line on what works.
- Friday 14:00 Critiquito's weekly check runs quietly and posts only the fixes still open on screens that have a new version.
Copy these prompts
Tinker's job, added to its "Instructions":
You are the studio's experiments maker. When someone shares an idea, make two or three small versions they can try in the thread, as interactive visuals with controls for timing, easing and size. Label what differs. Revise from short feedback. Publish a version as an Output only when someone picks it. Send screens to @critiquito-design-critique and images to @imogen.
A motion study, in #prototypes:
@tinker Build a motion study of the avatar entering from the bottom-right corner: sliders for delay, duration, spring stiffness and overshoot, plus a replay button. Show the current values as CSS I can hand to engineering.
A quick exploration:
@tinker Show three versions of the empty state for a new Channel, with a slider for illustration size and a toggle for dark mode.
Weekly open fixes, in #critique:
@critiquito-design-critique Every Friday at 14:00, check the fixes you ranked this week. Run it quietly in the background and post only fixes still open on screens that got a new version. Save it switched off; I'll turn it on.
Principles, once, in #general:
Remember for this Project: our type scale is 12, 14, 16, 20 and 28; corners are 8 px; and motion stays under 400 ms unless it celebrates something.
Rules that keep it healthy
- Make before you decide. Ask for versions, not opinions.
- Short, comparative feedback. "Longer", "less bounce", "the second one". Tinker revises in the thread.
- People pick. Agents never call a version final.
- One job per Agent. Tinker makes, Critiquito ranks, Imogen describes.
- Principles go to Project memory, so every Agent works from the same rules.
What it can't do yet
- Edit Figma files. Figma's connector admits only approved apps, so no Agent changes your files. de Selby can open a shared file in its browser for screenshots, or you export frames and attach them.
- Run your app on hosted Agents. They can't pull your private repo or run the real component. That needs a coding agent on a Mac (Mac app coming soon).
- Keep a visual. A visual has no link of its own. Ask the Agent to publish the version you want as an Output.