The Orvio skill
A small optional skill that keeps your agent inside a product's design when it adds pages, adapts the product or restyles from it.
The Orvio skill is a short set of instructions for your AI agent. It is available now, it is optional, and it has not yet been evaluated (see below). It does not contain any product. The agent fetches the product through the Orvio tools or the CLI, and the skill tells it how to build with what it fetched.
Why it exists#
The tools and the CLI give your agent a product's source, tokens, pages and components. An agent without design skills, asked to add a page or adapt a product, tends to invent a new type scale, new cards and generic sections. The product's quality is lost on the first edit. The skill is there to prevent that.
Do you need it#
You do not need it for a straight download. orvio pull and the file tools work the same without it.
You may not need it if your agent already has strong design skills of its own. The skill adds a method and a checklist. It does not add craft, and where the product and the skill disagree, the product wins.
It helps most when your agent has no design guidance and you ask it to add to, adapt or restyle from a product.
Get it#
With the CLI
$ orvio skill install
This writes the skill as an Agent Skills folder named orvio (SKILL.md and a references/ folder) into .claude/skills/orvio of the folder you run it in. To put it somewhere else, for example for another agent, add --dir <path>. If a file is already there and differs, nothing is written unless you add --force. The command needs no sign-in and makes no network request: the skill is not product source and holds no product. See orvio skill.
With MCP
The Orvio server also offers the same text as an MCP prompt, under the name orvio_skill. Your tool lists it with the server's prompts. It sits behind the same sign-in, approval and membership as the tools. The prompt carries the skill's text and its three reference files in one message, since a prompt cannot point at files on your disk.
Not yet evaluated. Orvio has not yet run the side-by-side evaluation of the skill, so it does not say how much the skill improves an agent's work, and it names no agent as tested with it. It is optional and you can remove it at any time by deleting the folder.
What it does#
The skill makes the agent name a mode before it writes anything, fetch the product, and check its work at the end.
| Mode | When | Fixed | May change |
|---|---|---|---|
| Extend | You add a page, screen, section or state to the same product, in the same field | Everything: type scale, containers, spacing, surfaces, radii, colours, components, motion markers, navigation, voice | Content. A new pattern only when nothing fits, built from the tokens. |
| Adapt | You take the product into another field | The design system: type scale, spacing rhythm, surfaces, radii, palette roles, motion language | Structure, sections, content, data patterns, trust signals |
| Restyle | You want your own look, inspired by the product | The quality list and the licence | The look, through a system the agent declares first and builds only from |
In every mode the agent fetches the facts first, with get_product, read_tokens, get_page, get_component and read_file (for the publisher's notes, agent/instructions.md), or with orvio pull. It then renders its result and the reference page at 1440 and 390 wide, compares them side by side, and runs a checklist for the mode. The prompts that go with each mode are in the Prompt library.
It also carries four lines on the licence: use in unlimited projects while you are a member, client work included; a project started while you are a member stays licensed; never redistribute the product; no AI training on it. The text in the product's licenses/ folder is what counts. See The licence in practice.
The skill also treats imagery as part of the design direction: it reads the product's images, makes new ones in the same style and ratios, and writes precise generation prompts for your image model. See Generate images for your pages.
What it does not do#
- It holds no product facts. Everything about a product comes from the product.
- It adds no tool. It uses the nine tools you already have, or the CLI.
- It does not replace a designer's eye. It reduces drift. You still review the result.
- It does not contain Driss's own design skills or their option libraries.
- It is not for making catalog themes. It is for your projects.
Versions#
The skill has its own version and names the Orvio theme contract it was written for. The current contract is v5. For products without the contract's markers, the agent follows the product as it is.
Licence#
MIT. The skill is free to copy and share; the products it works with stay under the Orvio Member Licence.
Tools it has been tried with#
None are named yet. The evaluation with Claude and Codex is planned; Orvio will name a tool as tested only for the modes that tool passes. Any agent that reads Agent Skills folders or MCP prompts can load it, but Orvio makes no claim about how well it works with a given one.