Total Skills
9
Skills published by khrore with real stars/downloads and source-aware metadata.
Total Skills
9
Total Stars
0
Total Downloads
0
Comparison chart based on real stars and downloads signals from source data.
composition-over-inheritance
0
cqs-review
0
design-by-contract
0
dry-principle
0
encapsulation-lens
0
kiss-principle
0
law-of-demeter
0
least-astonishment
0
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.
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.
Apply the KISS principle while generating, refactoring, or reviewing code in mixed-language or config-heavy repos. Use when code, scripts, modules, or configuration feel over-engineered, indirect, or harder to inspect and repair than the requirements justify.
Apply the Law of Demeter while generating, refactoring, or reviewing code in mixed-language or config-heavy repos. Use when code reaches through nested objects, crosses boundaries casually, or couples one layer to internals owned by another.
Apply the principle of least astonishment while generating, refactoring, or reviewing APIs, CLI flags, and configuration in mixed-language repos so behavior matches names, syntax, defaults, and local conventions, with attention to surprising defaults, hidden context, nonstandard semantics, and cross-layer drift.
Use SOLID while generating, refactoring, or reviewing code for structure, extensibility, and coupling in mixed-language or config-heavy repos. Map class to module or component, interface to API, schema, or contract, and dependency to library, tool, service, or path. Check SRP, OCP, LSP, ISP, and DIP, and flag god modules, fat interfaces, central switch trees, special-case adapters, hardcoded environment coupling, and abstractions without real variation.