Agent-Skills.md

Agent Skills: Project Vendor Boundary

Generic overlay for app-owned versus vendored dependency boundaries.

UncategorizedID: n-n-code/cpp-agentic-development-frame/project-vendor-boundary

Repository

n-n-code/cpp-agentic-development-frame
n-n-codeLicense: MIT

Install this agent skill to your local

pnpm dlx add-skill https://github.com/n-n-code/cpp-agentic-development-frame/tree/HEAD/.agents/skills/project-vendor-boundary

Skill Files

Browse the full folder contents for project-vendor-boundary.

Download Skill

Loading file tree…

.agents/skills/project-vendor-boundary/SKILL.md

Skill Metadata

Name
project-vendor-boundary
Description
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.

Project Vendor Boundary

Read AGENTS.md first. 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, and install rules aligned with vendor changes
  • avoid unrelated churn inside vendor trees