aposd-reviewing-module-design

Evaluate module design quality using a 40-item APOSD checklist.

351|31|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/ryanthedev/code-foundations --skill aposd-reviewing-module-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aposd-reviewing-module-design
Source: https://github.com/ryanthedev/code-foundations/tree/main/skills/aposd-reviewing-module-design
Command: npx skills add https://github.com/ryanthedev/code-foundations --skill aposd-reviewing-module-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluate module design quality using APOSD principles to surface structural issues.

Core Features & Use Cases

  • 40-item APOSD checklist to detect complexity symptoms such as change amplification, cognitive load, and unknown unknowns.
  • Identify information hiding problems, pass-through methods, and structural anti-patterns.
  • Produce a categorized design review (Critical/Moderate/Observations/Positive) for actionable remediation.
  • Use during code reviews, interface assessments, PR reviews, or architectural evaluations.

Quick Start

Start by applying the aposd-reviewing-module-design checklist to a target module, e.g., run the 40-item checklist on a codebase during a review.

Frequently Asked Questions about aposd-reviewing-module-design

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

FAQPage Schema
How do I review module design to identify structural anti-patterns?

Identify structural anti-patterns during a module design review by applying a 40-item APOSD checklist to detect information hiding problems and pass-through methods. This surfaces complexity symptoms and categorizes findings for actionable remediation.

What is APOSD and how does it help with code reviews?

APOSD is a set of software engineering principles used to evaluate module design quality during code reviews. It helps identify complexity symptoms like change amplification, cognitive load, and unknown unknowns to surface structural issues.

Does this APOSD checklist work for PR reviews and interface assessments?

Yes, the APOSD checklist is applicable during PR reviews, interface assessments, and architectural evaluations across software projects. It evaluates module design quality to surface structural issues and anti-patterns for actionable remediation.

How do I categorize complexity symptoms found during an architecture review?

Categorize complexity symptoms found during an architecture review into Critical, Moderate, Observations, or Positive findings. This APOSD-driven approach produces a categorized design review to prioritize actionable remediation.

What is the best way to detect pass-through methods and information hiding problems?

The best way to detect pass-through methods and information hiding problems is applying a 40-item APOSD checklist during a module design review. This identifies structural anti-patterns and surfaces complexity symptoms for actionable remediation.