software-engineering-library
Route software engineering design and discovered code-risk tasks to on-demand book references. Use for architecture review, layer boundary change, dependency boundary, module interface shape, domain modeling, bounded context, refactoring, code smell, legacy code, low test coverage, old file, characterization test, external API calls, queues, retries, transactions, event ordering, data layer, storage design, consistency, schema evolution, timeout, circuit breaker, bulkhead, DRY at the knowledge level, orthogonality, tracer bullet, broken windows, design by contract, and a forbidden-patterns blocklist review in .py, .cs, .ts, .tsx, .js, .ps1, .sql, and service design docs. Do NOT use for reinventing-the-wheel or build-vs-buy, use programming-advisor. Do NOT use for single-file maintainability scoring, use code-qualities-assessment. Do NOT use for CVA design, use cva-analysis.
- License
- MIT
Pinned to revision 6e62f3d0a901, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/software-engineering-library/SKILL.md
- skills/software-engineering-library/references/clean-architecture.md
- skills/software-engineering-library/references/data-intensive-applications.md
- skills/software-engineering-library/references/domain-driven-design.md
- skills/software-engineering-library/references/enterprise-patterns.md
- skills/software-engineering-library/references/forbidden-patterns.md
- skills/software-engineering-library/references/philosophy-of-software-design.md
- skills/software-engineering-library/references/pragmatic-programmer.md
- skills/software-engineering-library/references/refactoring.md
- skills/software-engineering-library/references/release-it.md
- skills/software-engineering-library/references/working-with-legacy-code.md
Every link opens the file at its source, pinned to the revision this page describes.