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.

SKILL.md

≈42 tokens for metadata: the name and description. ≈441 when used: this file. ≈1.9k more on demand in 3 files.

Description uses 2.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈168 characters, or 2.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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 and classify every entry by role. Continue when pnpm discovers the intended name and manifests reference no absent file.
  3. 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.
  4. For a published package, read 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. 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.

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