Skip to content
Skillv1.0.0

nextjs-package-boundaries

Use when structuring a Next.js workspace package, especially when separating server-only modules, source-consumed packages, and prebuilt UI packages.

by themoment-team(0) 0 installs
Free
Sign in to install

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from themoment-team/datagsm-client-v2 (.agents/skills/nextjs-package-boundaries/SKILL.md). Install upstream with npx skills add themoment-team/datagsm-client-v2 --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.

yaml
targets:
  - https://api.opensmartroute.ai/api/v1/registry/themoment-team-datagsm-client-v2-nextjs-package-boundaries/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.

themoment-team-datagsm-client-v2-nextjs-package-boundaries.ocm.jsonjson
{
  "ocm": "1",
  "id": "themoment-team-datagsm-client-v2-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": "themoment-team",
  "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/themoment-team/datagsm-client-v2",
      "path": ".agents/skills/nextjs-package-boundaries/SKILL.md",
      "ref": "53006d5daeb8c835eb0003c41e8b55aa0a654dc7",
      "url": "https://github.com/themoment-team/datagsm-client-v2/blob/53006d5daeb8c835eb0003c41e8b55aa0a654dc7/.agents/skills/nextjs-package-boundaries/SKILL.md",
      "key": "themoment-team/datagsm-client-v2/.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/themoment-team-datagsm-client-v2-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.