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.
personal-website-v2 - Skill - OpenSmartRoute
Skillv1.0.0
personal-website-v2
Keep comments short and precise, related to the codebase and not user's prompt - Don't test the project yourself, end user will do testing on their end themseleves - Follow existing project structure
Imported from ptchtrns/personal-website-v2 (AGENTS.md). Install upstream with npx skills add ptchtrns/personal-website-v2. Copyright stays with the author.
Keep comments short and precise, related to the codebase and not user's prompt
Don't test the project yourself, end user will do testing on their end
themseleves
Follow existing project structure
Use shadcn components whenever possible, add new components if needed
Do server-side-rendering, minimize client-side JavaScript and fetch()
requests, unless not practical
Use zod for requests validation
If you intend to write descriptions and other text related to UI, follow these
standards:
Dots should not be used for separating info inline. Use commas instead or
adjust the layout.
Em dashes should be used rarely.
Don't write text in UPPER CASE.
Date and time should not be American, a good format is HH:MM:SS for time and
DD.MM.YYYY for date.
If appropriate, suggest user to commit the changes with suggested commit
message. Do not commit yourself - always ask first.
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/ptchtrns-personal-website-v2-personal-website-v2/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": "ptchtrns-personal-website-v2-personal-website-v2",
"kind": "skill",
"name": "personal-website-v2",
"description": "Keep comments short and precise, related to the codebase and not user's prompt - Don't test the project yourself, end user will do testing on their end themseleves - Follow existing project structure - Use shadcn components whenever possible, add new components if needed - Do server-side-rendering, minimize client-side JavaScript and fetch() requests, unless not practical - Use zod for requests validation - If you intend to write descriptions and other text related to UI, follow these standards: - Dots should not be used for separating info inline. Use commas instead or adjust the layout. - Em dashes should be used rarely. - Don't write text in UPPER CASE. - Date and time should not be American, a good format is HH:MM:SS for time and DD.MM.YYYY for date. - If appropriate, suggest user to commit the changes with suggested commit message. Do not commit yourself - always ask first.",
"publisher": "ptchtrns",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Keep comments short and precise, related to the codebase and not user's prompt - Don't test the project yourself, end user will do testing on their end themseleves - Follow existing project structure - Use shadcn components whenever possible, add new components if needed - Do server-side-rendering, minimize client-side JavaScript and fetch() requests, unless not practical - Use zod for requests validation - If you intend to write descriptions and other text related to UI, follow these standards: - Dots should not be used for separating info inline. Use commas instead or adjust the layout. - Em dashes should be used rarely. - Don't write text in UPPER CASE. - Date and time should not be American, a good format is HH:MM:SS for time and DD.MM.YYYY for date. - If appropriate, suggest user to commit the changes with suggested commit message. Do not commit yourself - always ask first."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-agents",
"repository": "https://github.com/ptchtrns/personal-website-v2",
"path": "AGENTS.md",
"ref": "8d2b2ba3b02ac55adbf0ea8b77329f4e79b6a979",
"url": "https://github.com/ptchtrns/personal-website-v2/blob/8d2b2ba3b02ac55adbf0ea8b77329f4e79b6a979/AGENTS.md",
"key": "ptchtrns/personal-website-v2/AGENTS.md"
}
},
"instructions": "- Keep comments short and precise, related to the codebase and not user's prompt\n- Don't test the project yourself, end user will do testing on their end\n themseleves\n- Follow existing project structure\n - Use shadcn components whenever possible, add new components if needed\n - Do server-side-rendering, minimize client-side JavaScript and fetch()\n requests, unless not practical\n - Use zod for requests validation\n- If you intend to write descriptions and other text related to UI, follow these\n standards:\n - Dots should not be used for separating info inline. Use commas instead or\n a",
"cost": {
"context_tokens": 231
}
}
Fetch it by URL: GET /api/v1/registry/ptchtrns-personal-website-v2-personal-website-v2/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.
