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.
design-system - Skill - OpenSmartRoute
Skillv1.0.0
design-system
This is the app's design system. New UI and surfaces moving off the existing styles should use it. This initial port does not migrate existing surfaces; that is a boundary of the PR, not a prohibition
Imported from block/buzz-app (src/shared/design-system/AGENTS.md). Install upstream with npx skills add block/buzz-app --skill design-system. Copyright stays with the author.
Design system handoff
This is the app's design system. New UI and surfaces moving off the existing styles should use it.
This initial port does not migrate existing surfaces; that is a boundary of the PR, not a prohibition on adoption.
Read DESIGN.md and MAINTAINING_DESIGN_SYSTEM.md before editing.
Use authored ramps and named type roles; keep Base UI behavior and Phosphor icons through ../icons.
Preserve keyboard-only focus and test light/dark and narrow/intermediate/wide views.
Components live in ui/, values in styles/, documentation metadata in tokens/ and ui/registry.ts.
The standalone viewer lives in tests/fixtures/design-system and imports the real shared components.
Do not import features, plugins, native adapters, or app startup into this system or viewer.
When wiring it into the app, use the shared components and tokens rather than the viewer's documentation furniture.
Integrate global styles deliberately through the host entry point instead of layering two resets, and keep the host appearance owner.
The theme helper is viewer-only; app surfaces read appearance through the host.
Run the root design:typecheck, design:check, design:test, and design:build scripts.
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.
block-buzz-app-design-system.ocm.jsonjson
{
"ocm": "1",
"id": "block-buzz-app-design-system",
"kind": "skill",
"name": "design-system",
"description": "This is the app's design system. New UI and surfaces moving off the existing styles should use it. This initial port does not migrate existing surfaces; that is a boundary of the PR, not a prohibition on adoption. Read DESIGN.md and MAINTAINING_DESIGN_SYSTEM.md before editing. Use authored ramps and named type roles; keep Base UI behavior and Phosphor icons through ../icons. Preserve keyboard-only focus and test light/dark and narrow/intermediate/wide views. Components live in ui/, values in styles/, documentation metadata in tokens/ and ui/registry.ts. The standalone viewer lives in tests/fixtures/design-system and imports the real shared components. Do not import features, plugins, native adapters, or app startup into this system or viewer. When wiring it into the app, use the shared components and tokens rather than the viewer's documentation furniture. Integrate global styles deliberately through the host entry point instead of layering two resets, and keep the host appearance owner. The theme helper is v",
"publisher": "block",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"This is the app's design system. New UI and surfaces moving off the existing styles should use it. This initial port does not migrate existing surfaces; that is a boundary of the PR, not a prohibition on adoption. Read DESIGN.md and MAINTAINING_DESIGN_SYSTEM.md before editing. Use authored ramps and named type roles; keep Base UI behavior and Phosphor icons through ../icons. Preserve keyboard-only focus and test light/dark and narrow/intermediate/wide views. Components live in ui/, values in styles/, documentation metadata in tokens/ and ui/registry.ts. The standalone viewer lives in tests/fixtures/design-system and imports the real shared components. Do not import features, plugins, native adapters, or app startup into this system or viewer. When wiring it into the app, use the shared components and tokens rather than the viewer's documentation furniture. Integrate global styles deliberately through the host entry point instead of layering two resets, and keep the host appearance owner. The theme helper is v"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-agents",
"repository": "https://github.com/block/buzz-app",
"path": "src/shared/design-system/AGENTS.md",
"ref": "b70b0c63fc1464f3e759951cbcb3a2a182cf07f5",
"url": "https://github.com/block/buzz-app/blob/b70b0c63fc1464f3e759951cbcb3a2a182cf07f5/src/shared/design-system/AGENTS.md",
"key": "block/buzz-app/src/shared/design-system/AGENTS.md"
}
},
"instructions": "# Design system handoff\n\nThis is the app's design system. New UI and surfaces moving off the existing styles should use it.\nThis initial port does not migrate existing surfaces; that is a boundary of the PR, not a prohibition on adoption.\nRead DESIGN.md and MAINTAINING_DESIGN_SYSTEM.md before editing.\nUse authored ramps and named type roles; keep Base UI behavior and Phosphor icons through ../icons.\nPreserve keyboard-only focus and test light/dark and narrow/intermediate/wide views.\nComponents live in ui/, values in styles/, documentation metadata in tokens/ and ui/registry.ts.\nThe standalone ",
"cost": {
"context_tokens": 297
}
}
Fetch it by URL: GET /api/v1/registry/block-buzz-app-design-system/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
