riley1802/Nixos-config

edit-nixos

Change riley's NixOS flake config at /etc/nixos with clarifying questions, modular modules, validation, safe rebuild, auto-commit, README updates, reference/ sync, lessons.md error logging, and bestpracticesnixos.md. Use when the user invokes @edit-nixos,…

원문 언어: 영어

a-philosophy-of-software-design

Apply A Philosophy of Software Design for deep modules, simple interfaces, and complexity reduction. Use for API design, module design, refactoring shallow abstractions, or when the user mentions Ousterhout or complexity.

원문 언어: 영어

agent-rules-books

Index of programming book rule skills (Clean Code, Refactoring, DDD, Clean Architecture, DDIA, etc.) from ciembor/agent-rules-books. Use when the user asks which book rules to apply, wants coding standards from classic SE books, or references…

원문 언어: 영어

clean-architecture

Apply Clean Architecture for stable boundaries, the dependency rule, and separating business policy from frameworks. Use for architecture reviews, layering, or when the user mentions Clean Architecture or Uncle Bob.

원문 언어: 영어

clean-code

Apply Clean Code principles for readability, naming, small functions, and maintainable code shape. Use for everyday implementation, code review, or when the user mentions clean code or readability.

원문 언어: 영어

code-complete

Apply Code Complete practices for disciplined construction: variables, control flow, defensive programming, and testing. Use for implementation decisions or when the user mentions Code Complete or McConnell.

원문 언어: 영어

designing-data-intensive-applications

Apply DDIA principles for reliability, consistency, replication, partitioning, and data ownership. Use for data systems, events, streams, schema evolution, or when the user mentions DDIA or Kleppmann.

원문 언어: 영어

domain-driven-design-distilled

Apply DDD Distilled for practical subdomains, bounded contexts, and context mapping without excessive ceremony. Use when the user wants lightweight DDD or mentions Vaughn Vernon.

원문 언어: 영어

domain-driven-design

Apply Domain-Driven Design for domain modeling, bounded contexts, ubiquitous language, and tactical patterns. Use for modeling-heavy work or when the user mentions DDD or Evans.

원문 언어: 영어

implementing-domain-driven-design

Apply Implementing DDD for aggregates, domain events, context integration, and application architecture. Use for implementation-focused DDD work or when the user mentions IDDD.

원문 언어: 영어

patterns-of-enterprise-application-architecture

Apply PoEAA patterns for layers, repositories, domain model, and enterprise integration. Use when choosing application patterns or when the user mentions Fowler patterns or PoEAA.

원문 언어: 영어

refactoring-guru

Apply Refactoring.Guru guidance for code smell diagnosis and safe refactoring techniques. Use when diagnosing smells or choosing a refactoring treatment.

원문 언어: 영어

refactoring

Apply Refactoring principles for behavior-preserving structural improvements in small steps. Use for refactoring passes, cleanup, or when the user mentions refactoring or Fowler.

원문 언어: 영어

release-it

Apply Release It! for production reliability: failures, timeouts, retries, circuit breakers, and observability. Use for services, APIs, production fixes, or when the user mentions Release It or Nygard.

원문 언어: 영어

the-pragmatic-programmer

Apply The Pragmatic Programmer for DRY, orthogonality, automation, and pragmatic engineering. Use as general engineering guidance or when the user mentions pragmatic programming.

원문 언어: 영어

working-effectively-with-legacy-code

Apply Working Effectively with Legacy Code for safe changes to poorly tested code via seams and characterization tests. Use for legacy work or when the user mentions Feathers or legacy code.

원문 언어: 영어