Index of every page on this site: llms.txt
All skills
pingdotgg avatar

/package-development

@b5453de
by Ping.ggpingdotgg/t3code67k stars
11,639
Run it yourself

Package registration. Use when adding a workspace package, making a private package publishable, renaming a package, or moving its workspace path.

  • 4 files
  • 9.2 KB
  • Updated 2 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/pingdotgg/t3code/package-development

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

dependencies.md

≈542 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Package Dependencies

Inspect the closest package with the same publication and integration shape. Classify every manifest entry by the role it serves:

Role Use when
dependencies Published runtime code requires the package to receive its own installed copy.
peerDependencies Consumers provide a compatible shared package or the public contract integrates with their copy.
devDependencies Only repository build, test, type test, benchmark, or code generation needs the package.
optionalDependencies A runtime feature handles absence and installation failure must not block the base package.
Optional peer via peerDependenciesMeta A consumer-provided integration is genuinely optional. Keep its version in peerDependencies.

Use workspace:^ for workspace packages unless neighboring packages establish a different policy. When local build or tests need an installed peer, add the peer to devDependencies at the repository's tested version while keeping the peer range based on supported consumer versions.

Derive external versions from current consumers with the same integration shape. Add only direct requirements; do not copy a neighboring manifest entry that the new package's runtime, declarations, build, or tests do not use.

After editing manifests, run root pnpm install. Inspect warnings and the package's pnpm-lock.yaml importer for intended specifiers and resolutions. If a dependency has an install or native build, classify it under pnpm-workspace.yaml#allowBuilds using current repository policy.

This branch is complete when every entry has one justified role, workspace and peer ranges follow repository policy, the lockfile importer agrees with the manifest, and install/build policy is explicit.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at b5453de. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago

README badge

README badge for pingdotgg/t3code/package-development