package-development
Package registration. Use when adding a workspace package, making a private package publishable, renaming a package, or moving its workspace path.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 12
- Forks
- 0
01 前言 Front Matter
- 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.
02 资源文件 3
- 参考文档dependencies.md2.1 KB
- 参考文档publishing.md921 B
- 参考文档registration.md4.3 KB
03 SKILL.md 正文
Treat package work as a registration change, not a directory copy.
Workflow
- 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.
- Create or move only required source, test, TypeScript, and manifest files. When manifest dependencies change, read dependencies.md and classify every entry by role. Continue when pnpm discovers the intended name and manifests reference no absent file.
- Read 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.
- For a published package, read publishing.md and verify its development and packed surfaces.
- 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.
- 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. Continue when focused and root checks pass and the packed surface is intended.
- 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.
04 同仓库更多 Skills
vendored-assets
Vendored assets. Use when importing or updating checked-in third-party or externally generated JavaScript, CSS, registries, schemas, snapshots, or Scalar, Swagger, and MIME artifacts.
test-development
Test development. Use when adding or changing Vitest or Tstyche coverage. Choose Tstyche only for intended compiler behavior such as inference, assignability, rejection, or displayed public types.
performance-analysis
Performance analysis. Use for runtime throughput or latency benchmarks, TypeScript compiler cost, performance regressions, comparison harnesses, or thresholds.
migration-guidance
Use when changing how a v3 public API maps to v4, editing migration annotations, or regenerating migration/v3-to-v4.md.
jsdocs
Public API JSDoc. Use when authoring or reviewing Effect API documentation, refining a module's documentation, or fixing documentation related diagnostics.
effect-development
Effect development guidance. Use when implementing or reviewing code that composes Effect APIs or patterns.