Toolkit / For AI
A shared starting point
Give an agent the same foundations you use. Readable rules, direct assets, and accurate product language.
Start here
Give an agent the Markdown entrypoint, or the matching SKILL.md below. Each skill works independently and includes the brand rules and direct asset links relevant to its task. No account or archive extraction is required to read the built guide.
Create an IVR Cloud screen for [task].
Read ai.md and the matching IVR skill first.
Use the supplied Tailwind v4 theme and component sources.
Use real product contracts; label any illustrative data.
Choose the right reference
| Task | Read |
|---|---|
| Messaging, identity, color, typography | ivr-brand / SKILL.md |
| App interfaces or marketing pages | ivr-ui / SKILL.md |
| Editable Word documents and PDF | ivr-documents / SKILL.md |
| Editable PowerPoint and PDF slides | ivr-presentations / SKILL.md |
| Repeated controls and HTML recipes | Component library |
| Flows, routes, call history, voicemail | Product specimen |
| Logos, fonts, CSS, tokens | Assets |
Use one skill independently
Open or download the relevant Markdown skill and give that single file to the agent. All resource links are absolute at https://brand.ivr.ro/, as in the TWR skills. They are maintained directly and copied unchanged by the build. In a local checkout, use skills/<name>/SKILL.md and the assets under brand/, templates/, and examples/ at the root.
The document and presentation skills contain direct Pandoc commands, independent Word/PowerPoint reference files, and separate XeLaTeX styling for PDF. Read the documents guide and presentations guide for human examples. Font installation and document rendering are output-task prerequisites; they are not website-build dependencies.
Preserve the meaning
Publication and deployment are separate operations in the current app. Do not collapse them into a generic “live” badge. The public homepage is Romanian; current account screens are English. Match the target surface’s locale and translate complete workflows consistently.
Use only supported product claims. Distinguish the supplied identity from proposed dark-mode and product patterns. Example organizations and records in this toolkit are fictional.
Use the actual assets
The theme, component layer, and fonts are independent of the guide’s Hugo layouts and demo JavaScript. Import the Tailwind sources into the application build and scan its own templates. Keep complete class names in source. Use outlined logos and the right light/dark asset for the background.
Download the complete toolkit for local work. Report the checks you performed and any browser or accessibility checks you could not complete.