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.
Imported from Team-Gamism/lcg-server (.agents/skills/nextjs-package-boundaries/SKILL.md). Install upstream with npx skills add Team-Gamism/lcg-server --skill nextjs-package-boundaries. Copyright stays with the author.
Next.js Package Boundaries Guide
Expose package APIs through narrow barrel files; keep server-only APIs in index.server.ts and a dedicated export subpath.
Do not export server-only modules from a client-safe barrel.
Use transpilePackages only for source-consumed workspace packages that need Next.js to preserve RSC directives.
Prebuilt UI packages should publish JavaScript, CSS, and declarations; do not transpile them again in each app.
Keep package configuration, lint configuration, and Tailwind configuration out of the application runtime bundle.
Use each app's own public/, environment files, deployment configuration, and route boundary.
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": "team-gamism-lcg-server-nextjs-package-boundaries",
"kind": "skill",
"name": "nextjs-package-boundaries",
"description": "Use when structuring a Next.js workspace package, especially when separating server-only modules, source-consumed packages, and prebuilt UI packages.",
"publisher": "Team-Gamism",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Use when structuring a Next.js workspace package, especially when separating server-only modules, source-consumed packages, and prebuilt UI packages."
],
"primary": false,
"metadata": {
"source": {
"provider": "github",
"repository": "https://github.com/Team-Gamism/lcg-server",
"path": ".agents/skills/nextjs-package-boundaries/SKILL.md",
"ref": "1aee6306db22f60a840e02374987a1917793f5df",
"url": "https://github.com/Team-Gamism/lcg-server/blob/1aee6306db22f60a840e02374987a1917793f5df/.agents/skills/nextjs-package-boundaries/SKILL.md",
"key": "Team-Gamism/lcg-server/.agents/skills/nextjs-package-boundaries/SKILL.md"
}
},
"instructions": "# Next.js Package Boundaries Guide\n\n- Expose package APIs through narrow barrel files; keep server-only APIs in `index.server.ts` and a dedicated export subpath.\n- Do not export `server-only` modules from a client-safe barrel.\n- Use `transpilePackages` only for source-consumed workspace packages that need Next.js to preserve RSC directives.\n- Prebuilt UI packages should publish JavaScript, CSS, and declarations; do not transpile them again in each app.\n- Keep package configuration, lint configuration, and Tailwind configuration out of the application runtime bundle.\n- Use each app's own `publi",
"cost": {
"context_tokens": 167
}
}
Fetch it by URL: GET /api/v1/registry/team-gamism-lcg-server-nextjs-package-boundaries/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.
