Software Design Philosophy
Skill Verified ActiveManage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", "strategic vs tactical", "deep module", "information leakage", or "pass-through method". Also trigger when reviewing interface designs for simplicity, evaluating whether an abstraction is pulling its weight, or choosing between general-purpose and special-purpose approaches. Covers deep vs shallow modules, red flags for complexity, and comments as design documentation. For code quality, see clean-code. For boundaries, see clean-architecture.
Manage software complexity through deep modules, information hiding, and strategic programming by applying core design principles.
Features
- Manages software complexity through deep modules
- Explains information hiding and identifies leakage
- Differentiates strategic vs. tactical programming
- Provides a framework for evaluating module depth
- Offers guidance on comments as design documentation
Use Cases
- Use when the user mentions 'module design', 'API too complex', or 'complexity budget'
- Use when reviewing interface designs for simplicity or evaluating abstraction depth
- Trigger when choosing between general-purpose and special-purpose approaches
- Apply when refactoring code or advising on architecture decisions
Non-Goals
- Providing specific code implementations for every language
- Covering low-level code quality details (see clean-code skill)
- Detailed guidance on architectural patterns (see clean-architecture skill)
Installation
First, add the marketplace
/plugin marketplace add wondelai/skills/plugin install skills@wondelai-skillsQuality Score
VerifiedSimilar Extensions
V3 Ddd Architecture
100Domain-Driven Design architecture for claude-flow v3. Implements modular, bounded context architecture with clean separation of concerns and microkernel pattern.
Pathfinder
100Map a codebase into feature-grouped flowcharts, identify duplicated concerns across features, and propose a unified architecture. Use when asked to "find the ideal path," unify duplicated systems, or audit architecture before a refactor. Emits a proposed unified flowchart plus per-system /make-plan prompts.
Understand
100Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships
Cloud Architect
100Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost optimization, disaster recovery, landing zones, security architecture, serverless design.
API Design Patterns
100Comprehensive API design patterns covering REST, GraphQL, gRPC, versioning, authentication, and modern API best practices
Angular Developer
100Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.