Identifiers

Ask for exactly one product, page, component or token with a short identifier.

Plain words work. When you want precision, use an identifier. Paste it into your prompt and your tool fetches exactly that. Every product page on the website lists the identifiers of its release, pages and components.

The forms#

The product part is the product's catalog slug. It is unique in Orvio.

Rules#

• No version. Identifiers never carry a version. The tools always use the latest release.
• Pages use the route without the first and last slash. The home page is index: sotto/page/index. A page without a route uses its entry file without the extension.
• Components use the component's name.
• Tokens use the token's name in the source, such as --sotto-blush.

When two things share a name#

Orvio makes identifiers unique. When two components share a name, every one gets an @ and a short suffix made from where it lives, such as sotto/component/button@css-buttons. Tokens that share a name across themes get the theme's label instead. If a collision remains inside one file, ~1, ~2 follow.

Ask a tool and it tells you. If an identifier is ambiguous, the answer is ambiguous_identifier and lists the exact identifiers to use.

Where to find them#

• On the product page, in the identifiers list.
• In the result of search_products and get_product: every product, page and component comes with its identifier.
• In read_tokens: every token has one.

Pages and components by name#

get_page and get_component also accept the parts separately: product with page or component. For a page, page can be a route, a title or an entry path.

Release-local ids#

Inside the release's own index files you may see ids like pg-…, cmp-…, tok-…. The tools accept them as input, but they never print them as identifiers. Use the identifiers above.