ousterhout

Evaluate module and API design complexity during design reviews.

4|Updated Jan 29, 2026

Search Tags:#design #architecture #complexity #refactor #software #cognitive-load #information-hiding

Ready to run

npx skills add https://github.com/danmestas/wardrobe --skill ousterhout-danmestas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ousterhout
Source: https://github.com/danmestas/wardrobe/tree/main/skills/ousterhout
Command: npx skills add https://github.com/danmestas/wardrobe --skill ousterhout-danmestas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces cognitive load and architectural complexity by guiding modular design decisions.

Core Features & Use Cases

Principles for deep modules, information hiding, and minimal interfaces to simplify maintenance.
Use Case: apply during design reviews to compare architectural alternatives and select the simplest robust approach.

Quick Start

Analyze a current module and propose concrete refactoring steps that reduce interface complexity.

Frequently Asked Questions about ousterhout

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify and minimize software design complexity in my modules?▼

Software design complexity is minimized by evaluating interface depth and enforcing information hiding during design reviews. This process identifies overly complex modules and guides refactoring decisions to reduce cognitive load.

What is a deep module in software architecture and why does it matter?▼

A deep module in software architecture exposes minimal interface complexity while providing substantial functionality. This design pattern matters because it maximizes information hiding and significantly reduces cognitive load for developers maintaining the system.

How do I reduce cognitive load during an architecture design review?▼

Reduce cognitive load during an architecture design review by applying principles of deep modules and minimal interfaces. Comparing architectural alternatives to select the simplest robust approach directly minimizes complexity and cognitive load.

What is the best way to compare architectural alternatives for refactoring decisions?▼

The best way to compare architectural alternatives for refactoring decisions is to evaluate interface depth and information hiding. Selecting the simplest robust approach during design reviews minimizes complexity and ensures long-term maintainability.

When should I apply information hiding to simplify software maintenance?▼

Apply information hiding to simplify software maintenance when modules expose unnecessary implementation details that increase cognitive load. Use it during refactoring decisions to reduce interface complexity and drive simpler, more maintainable software designs.