OpenVerb Standard Library
The starter verbs every app should have
Theme, navigation, search, modals, toasts, forms, and sessions. A common baseline so your AI agent can immediately operate any site — without DOM hacks or brittle selectors.
What This Is
The Standard Library is not a complete list of all possible verbs. OpenVerb is designed so developers create their own verb libraries for their own domains. This stdlib gives you the starter verbs that virtually every app needs, so an AI agent can immediately:
- ✓ Switch themes (light/dark/system)
- ✓ Navigate pages and discover routes
- ✓ Search on-site content
- ✓ Show toast notifications
- ✓ Open and close modals
- ✓ Fill and submit forms
- ✓ Check session and preferences
7 families, 19 verbs. Your app adds its own verb libraries on top of these for domain-specific actions.
Verb Families (Level 0)
| Family | Verbs | Purpose |
|---|---|---|
| ui.theme | get, set | Theme (light/dark/system) |
| ui.nav | list_pages, go, back | Navigation & route discovery |
| ui.search | query, open_result | On-site search |
| ui.toast | show, dismiss | Notifications & feedback |
| ui.modal | open, close, list | Modal dialogs |
| ui.form | list, fill, submit, reset | Form interaction |
| user.session | get, logout, get_preferences | User session & preferences |
Quick Start
1. Install
# npm npm install openverb @openverb/stdlib # Python (copy manifests from repo) pip install openverb
2. Use the manifests
The JSON verb definitions live in manifests/. Import them or load from the package:
import { findVerb, getAllVerbs } from "@openverb/stdlib";
// Get a specific verb definition
const uiNavGo = findVerb("ui.nav.go");
// Get all 19 starter verbs
const verbs = getAllVerbs();3. Implement handlers
Use one of the reference implementations or write your own. The stdlib includes:
- Vanilla JS —
reference/vanilla/verbs.js - React —
reference/react/useOpenVerb.ts - Next.js —
reference/nextjs/verbs.ts
4. Wire up your AI
When your AI receives a verb call, dispatch it to your handler. The client applies the effect (e.g. router.push(path) for navigation).
Example: The "Accounting Page" Flow
This is the canonical flow that makes AI navigation feel natural:
- User: "I want to know about the accounting stuff"
- AI calls
ui.nav.list_pages - AI sees a route with tags matching "accounting"
- AI: "There's an Accounting page. Do you want me to take you there?"
- User: "Yes"
- AI calls
ui.nav.go({ routeId: "accounting" }) - Client navigates to
/accounting
The key: maintain a route registry so the AI knows what pages exist. The AI uses id to navigate — it never guesses URLs.
Documentation & Resources
GitHub Repository
Source code, manifests, reference implementations, and issue templates
Website Starter Verbs (Full Spec)
Complete verb definitions with input/output schemas for all 19 verbs
Navigation Patterns
Patterns, anti-patterns, and framework-specific guidance
npm Package
Install @openverb/stdlib — TypeScript types, manifests, and helpers
See It In Action
The Standard Library is integrated into real apps. Try asking the AI to navigate or change the theme:
Design Principles
Framework-agnostic core
Manifests are JSON. Handlers are framework-specific (vanilla, React, Next.js).
Deterministic
The AI uses registries (routes, modals, forms) — no guessing URLs or selectors.
Auditable
Every verb call has typed input/output. Log, replay, and review.
Composable
Verbs are small and independent. Combine them for complex flows.
Part of the OpenVerb Ecosystem
The Standard Library is the verb catalog layer. It works with the OpenVerb Framework packages:
| Package | Purpose |
|---|---|
| @openverb/stdlib | Standard verb definitions (this package) |
| @openverb/runtime | Execution runtime |
| @openverb/sdk | Client SDK & React hooks |
| openverb | Core framework (npm & PyPI) |