ciembor/agent-rules-books

# A Philosophy of Software Design Skill

Use this skill when a task involves module design, API design, information hiding, abstraction depth, cognitive load, or refactoring shallow interfaces.

Before making design or code decisions, read and apply [a-philosophy-of-software-design.mini.md](a-philosophy-of-software-design.mini.md). Use [a-philosophy-of-software-design.md](a-philosophy-of-software-design.md) only as a deeper reference when the mini rules are not enough for the current design tradeoff.

# Clean Architecture Skill

Use this skill when a task involves architectural boundaries, dependency direction, use cases, entities, interface adapters, framework isolation, or technology churn.

Before making design or code decisions, read and apply [clean-architecture.mini.md](clean-architecture.mini.md). Use [clean-architecture.md](clean-architecture.md) only as a deeper reference when the mini rules are not enough for the current architectural tradeoff.

# Clean Code Skill

Use this skill when a task involves everyday implementation quality, naming, small functions, readable control flow, responsibilities, comments, errors, or tests.

Before making design or code decisions, read and apply [clean-code.mini.md](clean-code.mini.md). Use [clean-code.md](clean-code.md) only as a deeper reference when the mini rules are not enough for the current code-quality tradeoff.

# Code Complete Skill

Use this skill when a task involves disciplined software construction: routine design, variable use, class design, control flow, defensive programming, coding standards, or implementation testing.

Before making design or code decisions, read and apply [code-complete.mini.md](code-complete.mini.md). Use [code-complete.md](code-complete.md) only as a deeper reference when the mini rules are not enough for the current construction tradeoff.

# Designing Data-Intensive Applications Skill

Use this skill when a task involves data ownership, consistency semantics, event flows, replication, partitioning, transactions, streams, batch processing, fault tolerance, or schema evolution.

Before making design or code decisions, read and apply [designing-data-intensive-applications.mini.md](designing-data-intensive-applications.mini.md). Use [designing-data-intensive-applications.md](designing-data-intensive-applications.md) only as a deeper reference when the mini rules are not enough for the current data-system tradeoff.

# Domain-Driven Design Skill

Use this skill when a task involves strategic domain modeling, ubiquitous language, bounded contexts, context mapping, aggregates, repositories, domain services, or model-driven design.

Before making design or code decisions, read and apply [domain-driven-design.mini.md](domain-driven-design.mini.md). Use [domain-driven-design.md](domain-driven-design.md) only as a deeper reference when the mini rules are not enough for the current domain-modeling tradeoff.

# Domain-Driven Design Distilled Skill

Use this skill when a task needs practical DDD guidance for subdomains, bounded contexts, context mapping, aggregates, domain events, or tactical modeling with restrained ceremony.

Before making design or code decisions, read and apply [domain-driven-design-distilled.mini.md](domain-driven-design-distilled.mini.md). Use [domain-driven-design-distilled.md](domain-driven-design-distilled.md) only as a deeper reference when the mini rules are not enough for the current DDD tradeoff.

# Implementing Domain-Driven Design Skill

Use this skill when a task involves implementing DDD in code: aggregate boundaries, invariants, repositories, domain events, application services, modules, factories, or bounded-context integration.

Before making design or code decisions, read and apply [implementing-domain-driven-design.mini.md](implementing-domain-driven-design.mini.md). Use [implementing-domain-driven-design.md](implementing-domain-driven-design.md) only as a deeper reference when the mini rules are not enough for the current implementation tradeoff.

# Patterns of Enterprise Application Architecture Skill

Use this skill when a task involves enterprise application structure, layering, service layer, transaction script, domain model, data mapper, repository, unit of work, identity map, DTOs, or integration patterns.

Before making design or code decisions, read and apply [patterns-of-enterprise-application-architecture.mini.md](patterns-of-enterprise-application-architecture.mini.md). Use [patterns-of-enterprise-application-architecture.md](patterns-of-enterprise-application-architecture.md) only as a deeper reference when the mini rules are not enough for the current enterprise-pattern tradeoff.

# Refactoring Skill

Use this skill when a task involves behavior-preserving code improvement, code smells, small refactoring steps, test-backed cleanup, or separating refactoring from feature changes.

Before making design or code decisions, read and apply [refactoring.mini.md](refactoring.mini.md). Use [refactoring.md](refactoring.md) only as a deeper reference when the mini rules are not enough for the current refactoring tradeoff.

# Refactoring.Guru Skill

Use this skill when a task involves diagnosing smells, choosing targeted refactoring treatments, preserving behavior, applying a refactoring catalog, or avoiding uncontrolled redesign.

Before making design or code decisions, read and apply [refactoring-guru.mini.md](refactoring-guru.mini.md). Use [refactoring-guru.md](refactoring-guru.md) only as a deeper reference when the mini rules are not enough for the current refactoring tradeoff.

# Release It! Skill

Use this skill when a task involves production reliability, integration failure, timeouts, retries, circuit breakers, bulkheads, backpressure, observability, capacity, deployment, or operational readiness.

Before making design or code decisions, read and apply [release-it.mini.md](release-it.mini.md). Use [release-it.md](release-it.md) only as a deeper reference when the mini rules are not enough for the current production-reliability tradeoff.

# The Pragmatic Programmer Skill

Use this skill when a task involves pragmatic engineering judgment, responsibility, DRY at the knowledge level, orthogonality, automation, prototyping, fast feedback, or adaptable design.

Before making design or code decisions, read and apply [the-pragmatic-programmer.mini.md](the-pragmatic-programmer.mini.md). Use [the-pragmatic-programmer.md](the-pragmatic-programmer.md) only as a deeper reference when the mini rules are not enough for the current engineering tradeoff.

# Working Effectively with Legacy Code Skill

Use this skill when a task involves risky legacy changes, missing tests, characterization tests, seams, dependency breaking, sprout method, wrap method, or incremental risk reduction.

Before making design or code decisions, read and apply [working-effectively-with-legacy-code.mini.md](working-effectively-with-legacy-code.mini.md). Use [working-effectively-with-legacy-code.md](working-effectively-with-legacy-code.md) only as a deeper reference when the mini rules are not enough for the current legacy-code tradeoff.