Install every skill from this repository$ npx skills add ciembor/agent-rules-books
Repository directory
Skills
14 of 14
#Skill8W activityInstalls
1code-completeApply Steve McConnell-inspired construction rules when implementing routines, variables, classes, control flow, defensive code, or tests.92the-pragmatic-programmerApply Hunt and Thomas-inspired pragmatic programming rules when improving engineering judgment, feedback loops, DRY knowledge, orthogonality, automation, or adaptability.93domain-driven-designApply Eric Evans-inspired DDD rules when modeling a complex domain, defining bounded contexts, protecting ubiquitous language, or designing aggregates.84implementing-domain-driven-designApply Vaughn Vernon-inspired implementation DDD rules when building aggregates, domain events, repositories, application services, or context integrations.85a-philosophy-of-software-designApply John Ousterhout-inspired software design rules when reducing complexity, designing module boundaries, or reviewing APIs and abstractions.76clean-architectureApply Robert C. Martin-inspired architecture rules when separating business policy from frameworks, databases, UI, or infrastructure details.77designing-data-intensive-applicationsApply Martin Kleppmann-inspired data-system rules when designing reliability, scalability, consistency, replication, transactions, streams, or schema evolution.78domain-driven-design-distilledApply Vaughn Vernon-inspired lightweight DDD rules when using bounded contexts, subdomains, context maps, and tactical modeling without excess ceremony.79patterns-of-enterprise-application-architectureApply Martin Fowler-inspired enterprise architecture rules when choosing layers, service layers, transaction scripts, domain models, repositories, mappers, or DTOs.710refactoringApply Martin Fowler-inspired refactoring rules when improving existing code structure while preserving observable behavior.711refactoring-guruApply Refactoring.Guru-inspired rules when diagnosing code smells, choosing refactoring techniques, and stopping cleanup before uncontrolled redesign.712release-itApply Michael T. Nygard-inspired production reliability rules when designing failure handling, timeouts, retries, circuit breakers, observability, or deployment behavior.713working-effectively-with-legacy-codeApply Michael Feathers-inspired legacy-code rules when changing hard-to-test code safely with characterization tests, seams, sprout methods, or wrap methods.714clean-codeApply Robert C. Martin-inspired clean code rules when improving readability, naming, function design, responsibilities, or testable everyday code.5