Review module boundaries, APIs, and abstractions using John Ousterhout-inspired design rules. Use it to reduce software complexity, decide which implementation details to hide, and reconsider interfaces that leave too much work to their callers.
Apply John Ousterhout-inspired software design rules when reducing complexity, designing module boundaries, or reviewing APIs and abstractions.
Review the instructions the agent will receive before you install.
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. Use a-philosophy-of-software-design.md only as a deeper reference when the mini rules are not enough for the current design tradeoff.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Helps separate business rules from frameworks, databases, user interfaces, and infrastructure. Uses Robert C. Martin-inspired architecture rules to guide decisions about responsibilities, dependency direction, and boundaries when technologies change.
Review everyday code for readability and testability using rules inspired by Robert C. Martin. Examine names, small functions, control flow, responsibilities, comments, error handling, and tests to guide practical improvements to implementation quality.
Apply construction rules inspired by Steve McConnell when designing routines, variables, classes, and control flow. The skill guides implementation decisions, defensive programming to handle unexpected conditions, coding standards, and implementation testing.
Guide data system design with Martin Kleppmann-inspired rules. Review reliability, growth, data consistency, replication, transactions, and schema changes, including decisions about data ownership and how events, streams, and batch jobs move and process information.
Model complex business domains using domain-driven design, an approach that organizes software around business concepts. Inspired by Eric Evans, this skill guides shared terminology, model boundaries, aggregates, and the relationships between different contexts.
Apply domain-driven design, an approach to modeling software around business concepts, without excessive ceremony. Inspired by Vaughn Vernon, this skill guides domain boundaries, relationships between models, aggregates, and events representing business occurrences.