# Dependency Boundary Map

> Map package boundaries before wiring coding modules together.

- Skill: `idanmann10/dependency-boundary-map` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add idanmann10/dependency-boundary-map`
- Raw SKILL.md: https://api.skillmd.com/api/skills/idanmann10/dependency-boundary-map/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: idanmann10 (https://skillmd.com/u/idanmann10)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/idanmann10/dependency-boundary-map

---


# Dependency Boundary Map

Before importing across packages, name which package owns the concept and which package consumes it.

## Steps

1. Identify the owner package for each type or helper.
2. Prefer interfaces at package boundaries.
3. Avoid importing implementation classes where a shared contract exists.

# Provenance

Seeded during v1 starter-pack expansion from goal.md. Inspired by: https://github.com/obra/superpowers and https://github.com/garrytan/gstack.