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.
main - Skill - OpenSmartRoute
Skillv1.0.0
main
always use @lucide/svelte for icons - use shadcn-svelte (use shadcn mcp) - use svelte-mcp for more context about svelte - use context7-mcp for more context about things you dont fully understand - aft
Instruction file imported from msu-projects/capstone-preview-2 (.github/instructions/main.instructions.md). Copyright stays with the author.
always use @lucide/svelte for icons
use shadcn-svelte (use shadcn mcp)
use svelte-mcp for more context about svelte
use context7-mcp for more context about things you dont fully understand
after you edit, make sure to run pnpm check and fix the errors.
imagine you are a senior developer with lots of experience. always keep in mind to have minimal redundancies and utilized good design patterns and clean code.
make sure to keep all views mobile responsive and work well on mobile, tablet, and desktop screen sizes.
make sure to keep all views light and dark mode friendly, based on the user's system settings.
reference the docs/project-process-overview.md for more details about the project
reference the .github/frontend-designer-skill.md if you are designing the frontend.
note that docs/project-process-overview.md is the single source of truth of the project, the project must always be consistent with what the docs/project-process-overview.md described.
the truth heirarchy:
docs/project-process-overview.md > types > project files
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/msu-projects-capstone-preview-2-main-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": "msu-projects-capstone-preview-2-main-instructions",
"kind": "skill",
"name": "main",
"description": "always use @lucide/svelte for icons - use shadcn-svelte (use shadcn mcp) - use svelte-mcp for more context about svelte - use context7-mcp for more context about things you dont fully understand - after you edit, make sure to run pnpm check and fix the errors. - imagine you are a senior developer with lots of experience. always keep in mind to have minimal redundancies and utilized good design patterns and clean code. - make sure to keep all views mobile responsive and work well on mobile, tablet, and desktop screen sizes. - make sure to keep all views light and dark mode friendly, based on the user's system settings. - reference the docs/project-process-overview.md for more details about the project - reference the .github/frontend-designer-skill.md if you are designing the frontend. - note that docs/project-process-overview.md is the single source of truth of the project, the project must always be consistent with what the docs/project-process-overview.md described. - the truth heirarchy: docs/project-proce",
"publisher": "msu-projects",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding",
"creative"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"always use @lucide/svelte for icons - use shadcn-svelte (use shadcn mcp) - use svelte-mcp for more context about svelte - use context7-mcp for more context about things you dont fully understand - after you edit, make sure to run pnpm check and fix the errors. - imagine you are a senior developer with lots of experience. always keep in mind to have minimal redundancies and utilized good design patterns and clean code. - make sure to keep all views mobile responsive and work well on mobile, tablet, and desktop screen sizes. - make sure to keep all views light and dark mode friendly, based on the user's system settings. - reference the docs/project-process-overview.md for more details about the project - reference the .github/frontend-designer-skill.md if you are designing the frontend. - note that docs/project-process-overview.md is the single source of truth of the project, the project must always be consistent with what the docs/project-process-overview.md described. - the truth heirarchy: docs/project-proce"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/msu-projects/capstone-preview-2",
"path": ".github/instructions/main.instructions.md",
"ref": "3aa505d8377a216abe467110ab19abd405e1ed16",
"url": "https://github.com/msu-projects/capstone-preview-2/blob/3aa505d8377a216abe467110ab19abd405e1ed16/.github/instructions/main.instructions.md",
"key": "msu-projects/capstone-preview-2/.github/instructions/main.instructions.md"
},
"applies_to": "**"
},
"instructions": "- always use @lucide/svelte for icons\n- use shadcn-svelte (use shadcn mcp)\n- use svelte-mcp for more context about svelte\n- use context7-mcp for more context about things you dont fully understand\n- after you edit, make sure to run pnpm check and fix the errors.\n- imagine you are a senior developer with lots of experience. always keep in mind to have minimal redundancies and utilized good design patterns and clean code.\n- make sure to keep all views mobile responsive and work well on mobile, tablet, and desktop screen sizes.\n- make sure to keep all views light and dark mode friendly, based on ",
"cost": {
"context_tokens": 266
}
}
Fetch it by URL: GET /api/v1/registry/msu-projects-capstone-preview-2-main-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.
