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.
bridge-map - Skill - OpenSmartRoute
Skillv1.0.0
bridge-map
Use when writing cross-stack features, checking APIs, or implementing new routes to ensure logic routing matches the established bridges map.
Instruction file imported from Code8Soumya/NITR (.github/instructions/bridge-map.instructions.md). Copyright stays with the author.
Logic Bridges Enforcement
You are working in the NITR HUB project, which utilizes a background watcher to map all connections between the UI, State, APIs, Lambdas, and Database.
Before you make any changes that span across modules or the full stack, you MUST refer to project_docs/logic_bridges.md.
This ensures you:
Do not hallucinate API endpoints or Zustand store action names.
Read the existing flows before creating duplicate endpoints.
Consistently match frontend paths with backend handlers.
When modifying a route or database fetch:
Always open project_docs/logic_bridges.md using the exact layout mapped.
Verify if a method/route already handles your specific need.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/code8soumya-nitr-bridge-map-instructions/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "code8soumya-nitr-bridge-map-instructions",
"kind": "skill",
"name": "bridge-map",
"description": "Use when writing cross-stack features, checking APIs, or implementing new routes to ensure logic routing matches the established bridges map.",
"publisher": "Code8Soumya",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Use when writing cross-stack features, checking APIs, or implementing new routes to ensure logic routing matches the established bridges map."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/Code8Soumya/NITR",
"path": ".github/instructions/bridge-map.instructions.md",
"ref": "f4c838d98b3f8d743c4518569895f93b8a570146",
"url": "https://github.com/Code8Soumya/NITR/blob/f4c838d98b3f8d743c4518569895f93b8a570146/.github/instructions/bridge-map.instructions.md",
"key": "Code8Soumya/NITR/.github/instructions/bridge-map.instructions.md"
},
"applies_to": "**/*.{ts,tsx,js,json}"
},
"instructions": "# Logic Bridges Enforcement\n\nYou are working in the NITR HUB project, which utilizes a background watcher to map all connections between the UI, State, APIs, Lambdas, and Database.\n\nBefore you make any changes that span across modules or the full stack, you MUST refer to `project_docs/logic_bridges.md`.\n\nThis ensures you:\n1. Do not hallucinate API endpoints or Zustand store action names.\n2. Read the existing flows before creating duplicate endpoints.\n3. Consistently match frontend paths with backend handlers.\n\nWhen modifying a route or database fetch:\n1. Always open `project_docs/logic_bridges",
"cost": {
"context_tokens": 174
}
}
Fetch it by URL: GET /api/v1/registry/code8soumya-nitr-bridge-map-instructions/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.
