Monorepo package boundary

Skill jukrap/ai-agent-playbook/skills/architecture/monorepo-package-boundary

Reusable AI agent skills, project templates, and guardrails for safer software maintenance and delivery.

Install

npx -y skills add jukrap/ai-agent-playbook --skill monorepo-package-boundary

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

2 stars2 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.

What its author says it does

Copied from the file, not written here

Use when changing or reviewing monorepo packages, workspace dependencies, package exports, internal libraries, build graphs, generated types, or cross-package release impact.

SKILL.md

1.1 KB, as published. Nobody here has run it

Monorepo Package Boundary

Use this as the primary architecture skill for workspace, package, and internal library boundaries.

Workflow

Identify workspaces, package manager, package ownership, public exports, internal/private modules, build graph, and affected consumers.
Check dependency direction, circular imports, versioning, generated types, release impact, and affected test/build selection.
Keep package boundaries aligned with ownership and runtime contracts rather than folder convenience.
Record affected packages, compatibility shims, required builds/tests, and release or publish constraints.

Reference

Read references/package-ownership-dependency-direction.md for package ownership, imports, exports, and dependency direction.