package-development
/package-development
Package registration. Use when adding a workspace package, making a private package publishable, renaming a package, or moving its workspace path.
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 29.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Package registration. Use when adding a workspace package, making a private package publishable, renaming a package, or moving its workspace path.
Original author description
Package registration. Use when adding a workspace package, making a private package publishable, renaming a package, or moving its workspace path.
How it works
- Workflow
SKILL.md preview
--- name: package-development description: Package registration. Use when adding a workspace package, making a private package publishable, renaming a package, or moving its workspace path. --- Treat package work as a registration change, not a directory copy. ## Workflow 1. Inspect the closest package in the same family. Classify publication status, runtime, test environment, platform support, barrels, and dependency shape. Justify each proposed file by precedent or an explicit repository need. Continue when every proposed file is justified. 2. Create or move only required source, test, TypeScript, and manifest files. When manifest dependencies change, read [dependencies.md](dependencies.md) and classify every entry by role. Continue when pnpm discovers the intended name and manifests reference no absent file. 3. Read [registration.md](registration.md). Classify every registration surface as applicable or not applicable and update every applicable surface. Continue when every surface is classified and old references are explained. 4. For a published package, read [publishing.md](publishing.md) and verify its development and packed surfaces. 5. Run codegen when the package owns generated barrels, then inspect generated sections rather than editing them manually. Continue when generated sections match source modules without manual edits. 6. Run focused package tests and scripts plus applicable root checks. Include public API type tests when applicable. For published packages, build and dry pack the package as described in [publishing.md](publishing.md). Continue when focused and root checks pass and the packed surface is intended. 7. Apply root changeset, generated-file, documentation, and workflow routing. The task is complete when package discovery, registration, generated output, validation, packed output, and changeset routing are all verified or reported as not applicable.
Files in this package (4)
- SKILL.md 2 KB
- dependencies.md 2 KB
- publishing.md 1 KB
- registration.md 4 KB
Versions
The database has no other skills named package-development.
Database snapshot: 13.11.2026 · package version ab1d80d21792 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90define-package
Add or specify a single package inside an existing pnpm/TypeScript workspace. Use when the user says "add a package", "create a new workspace package", "I need a shared/db/api/worker package", "add an SDK package", or asks how to introduce a new deployable or library into the… - 100migrate-internal-package
Move a package from another TryGhost repository into Ghost as an internal-only workspace package while preserving its Git history. Use for package migrations from repositories such as TryGhost/SDK or TryGhost/framework, including the history import PR, exceptional merge-commit… - 95r-package-development
R package development guide covering dependencies, API design, testing, and documentation. Use when developing R packages. - 100convert-internal-package-to-typescript
Convert a legacy internal Ghost workspace package from JavaScript or CommonJS to the repository's TypeScript and ESM golden path while preserving file history and runtime compatibility. Use when modernizing an existing or newly migrated private package, including staged… - 96ds-typescript
Use when changing TypeScript server, database, CLI, or MCP behavior in an existing Node.js package or workspace. - 100r-package-development
R package development with devtools, testthat, and roxygen2. Use when the user is working on an R package, running tests, writing documentation, or building package infrastructure.