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.
tapps-domain-frontend - Skill - OpenSmartRoute
Skillv1.0.0
tapps-domain-frontend
Frontend/UX TAPPS workflow: playbook, UI library docs, and quality gate on scored files. Use when building UI components, accessibility fixes, or client-side routing changes.
Imported from wtthornton/agentforge-stream-plugin (.tapps-mcp/backups/2026-08-04-005048/.claude/skills/tapps-domain-frontend/SKILL.md). Install upstream with npx skills add wtthornton/agentforge-stream-plugin --skill tapps-domain-frontend. Copyright stays with the author.
Domain playbook workflow — same quality gate as the standard TAPPS pipeline.
Session bootstrap. Call tapps_session_start() if not already called this session.
Load playbook. Call tapps_domain_playbook(domain="user-experience") (or read bundled checklist from the response). Follow its workflow and checklist.
Library docs. For each entry in lookup_hints, call tapps_lookup_docs(library=..., topic=...) before using those APIs.
Domain tools. Run the tools listed in recommended_tools on changed files in scope.
Edit loop. After each Python file change, call tapps_quick_check(file_path=...).
Close out. Invoke /tapps-finish-task with the task_type=frontend. Do not declare done without validate + checklist.
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}'
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
