Sponsored by

Find leads on Reddit on auto pilot

Agent skills
software-design

Topic: software-design

16 skills in this topic.

brooks-audit Architecture audit drawing on twelve classic engineering books: The Mythical Man-Month, Code Complete, Refactoring, Clean Architecture, The Pragmatic Programmer, Domain-Driven Design, A Philosophy of Software Design, Software Engineering at Google, xUnit Test Patterns, The Art of Unit Testing, Working Effectively with Legacy Code, and How Google Tests Software. Triggers when: user asks to audit architecture, review module structure, check system design, or assess project organization. Also triggers when user mentions: clean architecture / dependency inversion / hexagonal architecture / bounded contexts / module coupling / package structure. Use this skill proactively when project structure or module dependencies are discussed.
hyhmrright/brooks-lint 28
brooks-debt Tech debt assessment drawing on twelve classic engineering books: The Mythical Man-Month, Code Complete, Refactoring, Clean Architecture, The Pragmatic Programmer, Domain-Driven Design, A Philosophy of Software Design, Software Engineering at Google, xUnit Test Patterns, The Art of Unit Testing, Working Effectively with Legacy Code, and How Google Tests Software. Triggers when: user asks about tech debt, where to refactor, health check, or systemic maintainability questions. Also triggers when user asks why the codebase is hard to maintain, why adding developers isn't helping, or why complexity keeps growing. Use this skill proactively when maintainability or refactoring priorities are discussed.
hyhmrright/brooks-lint 28
brooks-review PR code review drawing on twelve classic engineering books: The Mythical Man-Month, Code Complete, Refactoring, Clean Architecture, The Pragmatic Programmer, Domain-Driven Design, A Philosophy of Software Design, Software Engineering at Google, xUnit Test Patterns, The Art of Unit Testing, Working Effectively with Legacy Code, and How Google Tests Software. Triggers when: user asks to review code, check a PR, review a pull request, or shares a diff for feedback. Also triggers when user mentions: Brooks's Law / Mythical Man-Month / conceptual integrity / second system effect / code smells / refactoring / clean architecture / DDD / domain-driven design / SOLID principles / Hyrum's Law / deep modules / tactical programming. Use this skill proactively whenever code, a diff, or a PR is shared for review.
hyhmrright/brooks-lint 28
brooks-test Test quality review drawing on twelve classic engineering books, with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code. Triggers when: user asks about test quality, flaky tests, mock abuse, test debt, legacy code testability, or shares test files for review. Also triggers when user mentions: test smells / characterization tests / test pyramid / test doubles / over-mocking / brittle tests. Use this skill proactively whenever test files are shared for review.
hyhmrright/brooks-lint 28
balanced-coupling The Balanced Coupling model for software design. Use when: designing modular architectures, evaluating coupling between components, reviewing code modularity, deciding whether to split or merge modules/services, assessing integration patterns, classifying coupling as balanced or unbalanced, applying DDD strategic and tactical patterns, reasoning about cohesion vs coupling trade-offs, identifying distributed monolith risks, or explaining why a system is hard to change. Provides the three-dimensional framework (integration strength, distance, volatility) and the balance rule for making coupling decisions.
vladikk/modularity 209
design Designs modular high-level architectures from functional requirements and produces design documents for each module. Use when designing a new system, creating architecture documentation, or producing module-level design specs with integration contracts and test specifications.
vladikk/modularity 209
document Produces modularity review documents in both Markdown and HTML formats. Use when writing the final review output from a modularity analysis.
vladikk/modularity 209
review Analyzes a codebase's modularity imbalances using the Balanced Coupling model and produces a review of design issues. Use when reviewing existing code for coupling problems, assessing architecture quality, identifying distributed monolith risks, or finding areas where changes are unexpectedly expensive.
vladikk/modularity 209
adr Architecture Decision Record skill for documenting significant architectural decisions with context, options, and consequences. Use during the Research phase when choosing between approaches, or whenever the user asks to document an architectural decision.
irahardianto/awesome-agv 129
code-review Structured code review protocol for inspecting code quality against the full rule set. Use when auditing code written by yourself or another agent, during the /audit workflow, or when the user asks for a code review.
irahardianto/awesome-agv 129
debugging-protocol Comprehensive protocol for validating root causes of software issues. Use when you need to systematically debug a complex bug, flaky test, or unknown system behavior by forming hypotheses and validating them with specific tasks.
irahardianto/awesome-agv 129
frontend-design Generates distinctive, production-grade frontend interfaces and artifacts (React, Vue, HTML/CSS). Prioritizes bold aesthetics, unique typography, and motion to avoid generic designs. Use when building websites, landing pages, dashboards, posters, or when the user requests to style, beautify, or create visually striking UI.
irahardianto/awesome-agv 129
guardrails Pre-flight checklist and post-implementation self-review protocol. Use before generating any code (pre-flight) and after writing code but before verification (self-review) to catch issues early.
irahardianto/awesome-agv 129
mobile-design Generates distinctive, production-grade mobile interfaces for Flutter and React Native. Prioritizes platform-native patterns, adaptive layouts, and fluid motion. Use when building mobile apps, screens, widgets, or when the user requests to style or create visually striking mobile UI.
irahardianto/awesome-agv 129
perf-optimization Profile-driven performance optimization protocol. Use when profiling data (CPU, heap, trace) is available or when the user requests performance analysis. Covers methodology, pattern catalog, safety invariants, and when-to-stop heuristics. Language-specific tooling is in languages/*.md.
irahardianto/awesome-agv 129
sequential-thinking Performs dynamic, reflective problem-solving through iterative thought chains. Use for complex planning requiring revision, branching, backtracking, or hypothesis verification. Ideal for multi-step analysis where context maintenance is required or the full scope isn't initially clear.
irahardianto/awesome-agv 129