Prompt library

Run `orvio pull sotto ./site`, then read the licence in the new folder and the file `agent/instructions.md`. Tell me how to run the project and what I should change first.

Using Orvio, add the complete current release of sotto to my project as the starting point. Keep its file structure, tell me which files you added, and read its licence first.

Using Orvio, search for products for an invoicing dashboard. Compare the two closest by their pages, tokens and framework, and recommend one before you build anything.

Use my connected Orvio MCP server to take inspiration from "Sotto" (identifier: sotto, current release 0.1.3) on Orvio. First, my stack: if you can see my project, use its framework and conventions (React, Vue, Svelte, Astro, plain HTML…). If you can't tell, ask me which framework I use before writing any code. 1. Call get_product with "sotto". Check that the release is 0.1.3 (if not, tell me which one you are using) and note its pages and components. 2. Call read_tokens with "sotto" for its colours, type and spacing, and turn them into my theme (CSS variables, a Tailwind config, or whatever my project uses). 3. Call get_page or get_component for the parts closest to what I'm building. Study their layout, spacing, states and responsive behaviour. 4. Call read_release with "sotto" once, for the licence and the publisher's notes for agents. Then build it my way. The product is static HTML, CSS and JavaScript: treat it as the design source, not code to paste. Rebuild it as clean, idiomatic components in my framework. Keep its craft (spacing, type scale, states, motion, accessibility), connect it to my own data and routes, and follow the product's licence. No MCP connection? Use the command line: run `orvio login` once, then `orvio pull sotto` (it adds the release to ./sotto; without a global install, `npx orvio pull sotto`), and read the files from there.

Using Orvio, read Sotto's design tokens and its home page. Restyle my site in that spirit with my own content and brand; adapt, don't copy.

Using Orvio, take Sotto as the design source. First ask me which framework my project uses, then rebuild the pages I name as idiomatic components in it.

Using Orvio, get sotto/page/pricing and rebuild it as React components with Tailwind, using the product's tokens as my theme. Keep its spacing, states and accessibility.

Using Orvio, get sotto/page/index and rebuild it as Vue 3 single-file components with my project's conventions. Move the product's colours and type into my existing theme and keep its responsive behaviour.

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.

Using Orvio, list the files of Sotto under source/css/, read the main stylesheet and explain how it is organised.

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.

Using Orvio, find a product for a calm editorial website and show me its pages, then its colour tokens with their values.

Using Orvio, show me Sotto's colour tokens with their values.

Using Orvio, read Sotto's colour tokens and compare them with the brand colours in tailwind.config.js. Tell me which of mine are closest, and where contrast between text and background would suffer.

Using Orvio, read Sotto's colour, type and spacing tokens and write them as CSS variables for my project, grouped and named for my codebase.