What's in a release
The folders and files of a release, and what each one is for.
A release is one version of a product, packaged the same way for every product. You get it as a ZIP, with orvio pull, or through the MCP tools.
The layout#
A release
orvio.json agent/ instructions.md pages.json components.json assets.json catalog/ catalog.json design-system/ tokens.json licenses/ LICENSE.md source/ …the product, as its authors wrote it validation/ inventory.json report.json review.json
What each part is#
| Path | What it is |
|---|---|
source/ | The product itself, in its own structure and framework. Files are byte for byte as authored. |
orvio.json | The manifest: name, version, type, framework, entry points, commands, licence. |
agent/instructions.md | The publisher's notes for AI agents. Each section states its source. |
agent/pages.json | The product's pages: route, title, entry file, the components they use. |
agent/components.json | The product's components: name, file and lines, props, what they depend on. |
agent/assets.json | The images and other assets, with their SHA-256 and rights status. |
design-system/tokens.json | The design tokens found in the source. See Design tokens. |
catalog/catalog.json | The product's catalog metadata: tagline, summary, categories, tags and the previews it declares. |
licenses/ | The product's licence, and third-party notices when the product has any. |
validation/ | A list of every file with its size and SHA-256, and the checks that were run. |
Static HTML or React#
Orvio supports two kinds of source today: static HTML, CSS and JavaScript, and React (JSX and TSX). Most of the catalog is static HTML. Your agent converts a product to your framework: see Port to your framework.
Read it through the tools#
| You want | Tool |
|---|---|
| The overview, licence, notes for agents and file tree | read_release |
| Facts: framework, pages, components | get_product |
| The file list with sizes and SHA-256 | list_release_files |
| One file | read_file |
| A page or component with the files it needs | get_page, get_component |
Prompts for pages and components#
ComponentsAdd one component
Using Orvio, find the component in Sotto closest to a pricing table with a yearly toggle, show me its source, then add it to my project with my styles.
Works with Remote MCP·Replace the highlighted parts
PagesList pages, then add one
Using Orvio, list Sotto's pages and components with what each is for, then add the pricing page to my project with the files it needs.
Works with Remote MCP·Replace the highlighted parts
PagesUnderstand how the styles are organised
Using Orvio, list the files of Sotto under source/css/, read the main stylesheet and explain how it is organised.
Works with Remote MCP·Replace the highlighted parts
Pages and components are listed as the release records them. A page's file list is an observation by Orvio's analysis, not proof that the page renders on its own. The result says whether it is complete.
Was this page clear? Yes · Not reallyEdit suggestions: support@orvio.design