Answers from the documentation; checking which model is on duty
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.
Instruction file imported from reactive/data-client (.cursor/rules/library-goals.mdc). Copyright stays with the author.
Library Goals Alignment
When editing library code in packages/*, read GOALS.md and weigh changes against it. It is the source of truth for project priorities — do not rely on a summary of it.
Evaluate design decisions (new APIs, abstractions, dependencies) against the goals before implementing.
When goals conflict for a given change (e.g. bundle size vs. performance), resolve the trade-off using the priorities expressed in GOALS.md, and note the reasoning (in a PR, under its GOALS impact section).
If a requested change works against the goals, say so and propose an alternative that stays aligned.
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 slotcurl-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 library-goals 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.
{
"ocm": "1",
"id": "reactive-data-client-library-goals-rule",
"kind": "skill",
"name": "library-goals",
"description": "Consider project goals when changing library code",
"publisher": "reactive",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github-cursor-rules"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Consider project goals when changing library code"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-cursor-rules",
"repository": "https://github.com/reactive/data-client",
"path": ".cursor/rules/library-goals.mdc",
"ref": "7adefeea939a693b19398666f4e395ad24e12be2",
"url": "https://github.com/reactive/data-client/blob/7adefeea939a693b19398666f4e395ad24e12be2/.cursor/rules/library-goals.mdc",
"key": "reactive/data-client/.cursor/rules/library-goals.mdc"
},
"applies_to": "packages/**"
},
"instructions": "# Library Goals Alignment\n\nWhen editing library code in `packages/*`, read [GOALS.md](../../GOALS.md) and weigh changes against it. It is the source of truth for project priorities — do not rely on a summary of it.\n\n- Evaluate design decisions (new APIs, abstractions, dependencies) against the goals before implementing.\n- When goals conflict for a given change (e.g. bundle size vs. performance), resolve the trade-off using the priorities expressed in GOALS.md, and note the reasoning (in a PR, under its GOALS impact section).\n- If a requested change works against the goals, say so and propose a",
"cost": {
"context_tokens": 158
}
}
Fetch it by URL: GET /api/v1/registry/reactive-data-client-library-goals-rule/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.
