agentleFS
Sign inStart free
martincjarvismartincjarvis/development-skills/skills/component-boundary-ownership/SKILL.md

component-boundary-ownership

Skill4 starsChanged 10 months agoMITView on GitHub

Use when user decides repository organization, where functionality should live, or reviews component boundaries. Determines cross-component ownership and placement (macro), delegates intra-component file layout to scoped-colocation (micro).

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ensure clear ownership and minimal coupling when organizing repositories.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Component Boundary Ownership

Overview

Determine macro-level repository organisation and component boundaries based on deployment independence, team ownership, coupling analysis, and reuse patterns. Delegates micro-level concerns (intra-component file layout) to scoped-colocation skill.

Ensure clear ownership and minimal coupling when organizing repositories. Determines macro placement (which component owns what), delegates micro placement (file layout within components) to scoped-colocation.

REQUIRED: superpowers:brainstorming, superpowers:verification-before-completion

When to Use

  • User decides repository organization or restructures codebase
  • User asks where functionality should live (component placement decisions)
  • User reviews or questions existing component boundaries
  • New functionality spans multiple existing components
  • Team ownership changes require boundary realignment
  • Deployment independence needs evaluation for splitting/merging components

Core Workflow

  1. Identify candidate boundaries based on deployment independence, team ownership, coupling analysis, and reuse patterns
  2. Evaluate organization pattern: Monorepo (workspaces), Polyrepo (separate repos), Modular Monolith (internal boundaries)
  3. Decide placement aligned to ownership, deployment boundaries, and documentation grouping
  4. Document boundaries in docs/architecture/component-boundaries.md with ownership matrix
  5. Delegate micro concerns to scoped-colocation for intra-component file placement

Boundary Decision Criteria

CriterionExtract Boundary When
DeploymentComponents deploy independently
OwnershipDifferent teams own different parts
CouplingHigh internal cohesion, low external coupling
ReuseCode shared by 3+ components

Well-Known Locations

Files with required positions: README.md (root), package.json (component root), .github/ (repo root), .gitignore (root).

See Boundary Patterns for detailed guidance.

Rationalizations Table

ExcuseReality
"Can reorganize later"Boundaries harder to add later. Establish early.
"Current structure works"Missing boundaries couple components, slow changes.
"Just need it working"Placement decision takes 5 minutes. Wrong placement creates debt.

Red Flags - STOP

  • "Can reorganize later" / "Just put it in /src"
  • "Current structure is fine" / "Split when we need to"

All mean: Apply skill to evaluate boundaries properly.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free