fundamentals/object-relationships

Identify class relationships and lifecycles to guide architectural decisions.

Updated Mar 26, 2026

Search Tags:#aggregation #composition #coupling #dependency #association #class design #object relationships

Ready to run

npx skills add https://github.com/johnnystefan/test-saas-business --skill fundamentals-object-relationships

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fundamentals/object-relationships
Source: https://github.com/johnnystefan/test-saas-business/tree/main/skills/fundamentals/object-relationships
Command: npx skills add https://github.com/johnnystefan/test-saas-business --skill fundamentals-object-relationships

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifying relationships such as dependency, association, aggregation, and composition keeps class diagrams readable and ensures coupling remains intentional rather than accidental, preventing fragile architecture.

Core Features & Use Cases

Relationship taxonomy: Learn the distinguishing signs of dependency versus association so you can categorize any field or parameter usage correctly.
Lifecycle analysis: Evaluate whether a child can outlive its container to choose aggregation over composition, or enforce composition when ownership is strict.
Refactoring nudges: Spot message chains and offer Hide Delegate suggestions to simplify layered interactions and reduce needless coupling.

Quick Start

Evaluate two related classes and determine whether their bond is a dependency, association, aggregation, or composition.

Frequently Asked Questions about fundamentals/object-relationships

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

FAQPage Schema

What is the difference between aggregation and composition in class design?▼

Aggregation in class design implies a weak 'has-a' relationship where a child object can outlive its parent container, whereas composition enforces strict ownership and lifecycle dependency, meaning the child is destroyed when the parent is destroyed.

How do I identify dependency versus association in object relationships?▼

Dependency in object relationships indicates a temporary, weak coupling where one class merely uses another as a parameter or local variable, while association represents a stronger, permanent structural link where one class holds a direct reference to another as a field.

When should I use composition over aggregation for domain models?▼

Use composition over aggregation for domain models when a child component's lifecycle is strictly bound to its parent container, ensuring the child cannot logically exist or operate independently without the parent object maintaining ownership.

How do I reduce accidental coupling during domain model design reviews?▼

Reduce accidental coupling during domain model design reviews by evaluating parent-child ownership rules, spotting complex message chains, and applying Hide Delegate refactoring nudges to simplify layered interactions and distinguish dependency from association.

Does refactoring message chains help clarify object relationships?▼

Refactoring message chains clarifies object relationships by identifying unnecessary intermediary dependencies and offering Hide Delegate suggestions, which reduces needless structural coupling and keeps class diagrams readable and maintainable.