One-click install
npx skills add https://github.com/gustavofsantos/dot-files --skill bounded-contexts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bounded-contexts
Source: https://github.com/gustavofsantos/dot-files/tree/main/skills/bounded-contexts
Command: npx skills add https://github.com/gustavofsantos/dot-files --skill bounded-contexts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Boundaries between system parts often become blurred, leading to tight coupling and ripple effects when changes occur. This skill guides you to reason about where responsibilities live, how modules should communicate, and when a contract should separate concerns to keep changes local.

Core Features & Use Cases

  • Clear boundaries: identify where a module's responsibilities end and another's begin to reduce unwanted dependencies.
  • Contract-driven interactions: design minimal interfaces that enable collaboration without exposing internals.
  • Change-locality guidance: evaluate how changes in one area impact others and enforce ownership of contracts.

Quick Start

Identify two interacting modules, define a minimal contract between them, and assign responsibility for the contract.

Frequently Asked Questions about bounded-contexts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define clear module boundaries to reduce tight coupling in system architecture?

Define clear module boundaries by identifying where a module's responsibilities end and another's begin, then design minimal contracts between contexts to reduce unwanted dependencies and keep changes local. This promotes high-cohesion, low-coupling architectures.

What is the best way to design minimal contracts for loose coupling between interacting modules?

Design minimal contracts for loose coupling by defining interfaces that enable collaboration without exposing module internals, assigning explicit ownership of the contract to enforce stable interaction rules.

How do I evaluate change locality when modifying components across bounded contexts?

Evaluate change locality by mapping how a modification in one bounded context impacts another, enforcing contract ownership so that ripple effects are contained and changes remain local to the owning context.

When do I need to separate concerns with a contract during system design reviews?

Separate concerns with a contract during design reviews when two interacting modules require explicit interaction rules, ensuring high cohesion and preventing cross-cutting coupling from blurring system boundaries.

Does this approach to dependency management work for modular design without external frameworks?

Yes, this dependency management approach works for modular design without external frameworks, as it relies on defining stable interfaces and explicit ownership rules to enforce boundaries rather than requiring specific platform dependencies.

Why does cross-cutting coupling cause ripple effects across system architecture modules?

Cross-cutting coupling causes ripple effects because blurred boundaries allow changes in one module to propagate unchecked to others, making it necessary to enforce minimal contracts and explicit ownership to isolate modifications.