New package

Skill eugenelim/agent-ready-repo/packs/monorepo-extras/.apm/skills/new-package

Use this skill when the user wants to scaffold a new package in the monorepo's `packages/` directory. Triggers on "new package", "create a package called...", "add a library for...". Don't use for new top-level directories (those need an RFC) or for new apps (which go in `apps/`, not `packages/`).From its SKILL.md

Install

npx -y skills add eugenelim/agent-ready-repo --skill new-package

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.5 KB, 538 tokens by cl100k_base, as published. Nobody here has run it

Skill: new-package

Scaffold a new package under packages/ with the conventions every package in this monorepo follows.

When to invoke

Confirm:

It belongs in packages/ (shared library), not apps/ (deployable).
Its name is unique within packages/ and reasonably descriptive.
There isn't an existing package that should grow this functionality instead — proliferating tiny packages is its own problem.

If the package's purpose isn't clear in one sentence, ask the user to articulate it before scaffolding.

Procedure

Create the directory structure (two mkdir calls so the snippet works in shells without brace expansion — POSIX sh, Windows PowerShell, dash):
```
mkdir -p packages/<name>/src
mkdir -p packages/<name>/tests
```
Add the standard files:
- package.json (or equivalent) with the project's standard fields
- README.md aimed at human consumers — explains what the package is, how to install it, and gives one realistic usage example
- AGENTS.md aimed at agents — package-specific rules that don't fit in the root AGENTS.md
- src/index.<ext> with a placeholder export
- tests/index.test.<ext> with a passing placeholder test
Wire the package into the workspace config (e.g., pnpm-workspace.yaml, Cargo.toml workspace, go.work — whichever applies).
Run the install command to verify the workspace picks it up.
Run the test command to verify the placeholder test passes.
Update docs/architecture/overview.md to list the new package and what it's for. (If this update would be the only change to overview.md in weeks, that's fine — overview.md is meant to drift slowly.)

What goes in the per-package AGENTS.md

Keep it specific. The root AGENTS.md already covers monorepo-wide things. Per-package AGENTS.md should cover only:

What this package does (one sentence).
Anything unusual about its build, test, or release.
Constraints particular to this package (e.g., "this package targets Node 18; do not use Node 20+ APIs").
Public interface boundaries — what's exported vs. internal.

If you find yourself copying the root AGENTS.md, stop. The agent already has that context.

What ships with it: 1 file

1.2 KB alongside SKILL.md

evals/

eval_queries.json1.2 KB