Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
web-design-guidelines - Skill - OpenSmartRoute
Skillv1.0.0
web-design-guidelines
Review web UI source for accessibility, focus, forms, motion, typography, overflow, performance, navigation, touch, responsive layout, theming, and interaction problems. Use for UI, UX, accessibility,
Imported from williamzujkowski/progress-quest-iii (.agents/skills/web-design-guidelines/SKILL.md). Install upstream with npx skills add williamzujkowski/progress-quest-iii --skill web-design-guidelines. Copyright stays with the author.
Web Interface Guidelines
Review the requested UI files against the complete pinned checklist in
references/guidelines.md. Read that file fully
before auditing.
Report only actionable findings grouped by file in terse file:line - issue
form. Use ✓ pass when a reviewed file has no findings. Treat the checklist as
heuristics: project requirements, platform specifications, and WCAG take
precedence.
This local skill pins Vercel Labs' MIT-licensed Web Interface Guidelines at
commit d0a657bfe87e86dd3a4753d7ec28c7e7dd7a88fe. Do not fetch or execute mutable
remote instructions during an audit.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install web-design-guidelines and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.