software-engineering-library

Software Engineering Library

This skill routes software engineering design work to deeper book-derived references without loading them on every turn.

For the everyday default, none loads on every turn and code-quality and unified-software-engineering load on code files; open a reference here only when the task needs that specific book's depth (start with one, add a second only when it changes a decision).

Triggers

• architecture review
• domain modeling bounded context
• refactoring code smells legacy code low test coverage old file characterization tests
• external API calls queues retries timeouts circuit breaker bulkhead
• transactions event ordering data consistency schema evolution module interface shape

When Each Reference Applies

• Use references/clean-architecture.md when dependency direction, layer ownership, or boundary placement drives the decision.
• Use references/philosophy-of-software-design.md when module depth, interface shape, or complexity hiding drives the decision.
• Use references/domain-driven-design.md when the work models a domain, splits bounded contexts, or translates across contexts.
• Use references/enterprise-patterns.md when persistence, repositories, unit-of-work, transactions, or application service orchestration are central.
• Use references/refactoring.md when changing internal structure, addressing code smells, or preserving behavior while improving shape.
• Use references/working-with-legacy-code.md when the code is hard to test, poorly covered, or needs seams and characterization tests before change.
• Use references/data-intensive-applications.md when state, storage, schema evolution, consistency, ordering, or delivery semantics are central.
• Use references/release-it.md when production resilience, timeouts, circuit breakers, bulkheads, retries, and operational failure modes are central.
• Use references/pragmatic-programmer.md when DRY at the knowledge level, orthogonality, tracer-bullet delivery, automation, feedback loops, broken windows, or design by contract drive the decision.
• Use references/forbidden-patterns.md when reviewing a diff or generating code against the design, architecture, data-and-production, or change-and-legacy blocklist.