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.
rules - Skill - OpenSmartRoute
Skillv1.0.0
rules
Rules for Code Contributions ## General Guidelines 1. **Code Quality**: Ensure that your code is clean, well-documented, and follows the project's coding standards. 2. **Testing**: Dont need test 3. T
Instruction file imported from rizkypsr/smeshub-ai (.github/instructions/rules.instructions.md). Copyright stays with the author.
Rules for Code Contributions
General Guidelines
Code Quality: Ensure that your code is clean, well-documented, and follows the project's coding standards.
Testing: Dont need test
TypeScript: Use TypeScript for type safety and better developer experience. Ensure that types are correctly defined and used throughout the codebase.
Linting: Use ESLint and Prettier to maintain code style consistency. Run the linter before committing your changes.
Commit Messages: Write clear and descriptive commit messages that explain the changes made.
Prefer functional components and hooks over class components in React.
Dependencies: Only add dependencies that are necessary for the project. Avoid bloating the project with unnecessary libraries.
Code Reviews: Be open to feedback and willing to make changes based on code review comments.
Use shadcn UI components for ui components.
Use Next.js 15.3+ and App Router for routing.
Use Next.js Server Components for initial data fetch.
Use Client Components with useEffect or SWR for dynamic data.
Use error.js and loading.js in App Router.
Provide fallback UI for Suspense.
ui must be responsive and work on mobile devices and tablet.
using drizzle ORM for database interactions (postgress).
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.
{
"ocm": "1",
"id": "rizkypsr-smeshub-ai-rules-instructions",
"kind": "skill",
"name": "rules",
"description": "Rules for Code Contributions ## General Guidelines 1. **Code Quality**: Ensure that your code is clean, well-documented, and follows the project's coding standards. 2. **Testing**: Dont need test 3. TypeScript: Use TypeScript for type safety and better developer experience. Ensure that types are correctly defined and used throughout the codebase. 4. **Linting**: Use ESLint and Prettier to maintain code style consistency. Run the linter before committing your changes. 4. **Commit Messages**: Write clear and descriptive commit messages that explain the changes made. 5. Prefer functional components and hooks over class components in React. 6. **Dependencies**: Only add dependencies that are necessary for the project. Avoid bloating the project with unnecessary libraries. 7. **Code Reviews**: Be open to feedback and willing to make changes based on code review comments. 8. Use shadcn UI components for ui components. 9. Use Next.js 15.3+ and App Router for routing. 10. Use Next.js Server Components for initial dat",
"publisher": "rizkypsr",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding",
"math"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Rules for Code Contributions ## General Guidelines 1. **Code Quality**: Ensure that your code is clean, well-documented, and follows the project's coding standards. 2. **Testing**: Dont need test 3. TypeScript: Use TypeScript for type safety and better developer experience. Ensure that types are correctly defined and used throughout the codebase. 4. **Linting**: Use ESLint and Prettier to maintain code style consistency. Run the linter before committing your changes. 4. **Commit Messages**: Write clear and descriptive commit messages that explain the changes made. 5. Prefer functional components and hooks over class components in React. 6. **Dependencies**: Only add dependencies that are necessary for the project. Avoid bloating the project with unnecessary libraries. 7. **Code Reviews**: Be open to feedback and willing to make changes based on code review comments. 8. Use shadcn UI components for ui components. 9. Use Next.js 15.3+ and App Router for routing. 10. Use Next.js Server Components for initial dat"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/rizkypsr/smeshub-ai",
"path": ".github/instructions/rules.instructions.md",
"ref": "e6580bf4aa98b80c023b6610fb47aa2300e5005a",
"url": "https://github.com/rizkypsr/smeshub-ai/blob/e6580bf4aa98b80c023b6610fb47aa2300e5005a/.github/instructions/rules.instructions.md",
"key": "rizkypsr/smeshub-ai/.github/instructions/rules.instructions.md"
},
"applies_to": "**"
},
"instructions": "# Rules for Code Contributions\n## General Guidelines\n1. **Code Quality**: Ensure that your code is clean, well-documented, and follows the project's coding standards.\n2. **Testing**: Dont need test\n3. TypeScript: Use TypeScript for type safety and better developer experience. Ensure that types are correctly defined and used throughout the codebase.\n4. **Linting**: Use ESLint and Prettier to maintain code style consistency. Run the linter before committing your changes.\n4. **Commit Messages**: Write clear and descriptive commit messages that explain the changes made.\n5. Prefer functional compon",
"cost": {
"context_tokens": 327
}
}
Fetch it by URL: GET /api/v1/registry/rizkypsr-smeshub-ai-rules-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.
