Project vendor boundary

Skill n-n-code/n-n-code-skills/.agents/skills/project-vendor-boundary

Just Another Agent skill repository.

Install

npx -y skills add n-n-code/n-n-code-skills --skill project-vendor-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

4 stars4 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

Overlay for app-owned versus vendored dependency boundaries. Portable across repos that vendor third-party code. Use when work touches vendored dependencies or their integration seam.

SKILL.md

1.3 KB, as published. Nobody here has run it

Project Vendor Boundary

This is a composable overlay, not a standalone workflow. Use alongside the repo's implementation skill when work touches vendored dependencies or their integration boundary.

When to use

The change involves vendored third-party code, the boundary between app-owned and vendored code, or dependency integration (subtrees, vendor directories, copied sources).

Not for

App-owned code that does not touch vendor boundaries (use the implementation skill directly), or release/packaging concerns (use project-release-maintainer).

Rules

prefer app-side integration changes before editing vendored code
treat vendored code as subtree/vendor content, not normal project code
keep notices, provenance, upstream version/source, local patch rationale, and install rules aligned with vendor changes
prefer adapter or wrapper changes in app-owned code before patching vendored sources; patch vendor code only when the seam cannot reasonably absorb the change
avoid unrelated churn inside vendor trees