prpm-json-best-practices

A prpm.json manifest requires name, version, description, author, license, format, subtype, and files fields. For single packages, list these at the top level; for multi-package repositories, nest each package's metadata and include a collections field to group related packages together.

Use tags to categorize packages semantically and enable discovery. Set eager activation for packages needed immediately at startup, and lazy activation for optional or on-demand packages to reduce load time and resource overhead.

Yes. Multi-package PRPM repositories support nested package structures with separate metadata for each package and a collections field to organize them logically, making monorepos with multiple Claude skills or Cursor rules straightforward to manage.

Manifest validation checks that all required fields are present and properly typed, file paths resolve correctly, and version strings follow semantic versioning. Validation occurs before registry submission and catches structural errors early.

In single-package manifests, file paths are relative to the repository root. In multi-package structures, paths are scoped to each package's directory within the monorepo, preventing conflicts and clarifying which files belong to each package.