Prefer composition for reusable behavior in mixed-language and config-heavy repos. Use when generating, reviewing, or designing modules, helpers, configs, CI steps, or components and deciding whether has-a relationships, delegation, or assembly are cleaner than inheritance or deep hierarchy reuse. Flag inheritance used only for reuse, hierarchy explosion, fragile base classes, and cases where delegation or smaller components would be simpler.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "composition-over-inheritance" with this command: npx skills add khrore/skillsmp-khrore-khrore-composition-over-inheritance
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Apply command-query separation while generating, refactoring, or reviewing callable boundaries in mixed-language and config-heavy repos so operations either mutate state or return information, with explicit plan/apply or validate/fix splits and only documented exceptions for atomicity or concurrency.
Apply Design by Contract while generating, refactoring, or reviewing code in mixed-language or config-heavy repos. Use when boundaries need clearer guarantees, validation, failure behavior, or compatibility rules for adapters and overrides.
Use DRY while generating, refactoring, or reviewing code in mixed-language or config-heavy repos. Keep one authoritative representation for change-prone knowledge such as rules, versions, paths, schemas, option lists, and behavior descriptions. Review for duplicated logic and for drift across docs, tests, CI, and config, but avoid premature abstraction when duplication is harmless and clarity matters more.
Apply encapsulation while generating, refactoring, or reviewing code in mixed-language or config-heavy repos so state stays with the operations that maintain it, internals stay behind stable interfaces, and consumers do not rely on private attributes or incidental defaults.