bchapuis

software-specification

bchapuis1/13/2026

This skill should be used when the user asks to "write specifications", "specify an abstraction", "create contract tests", "property-based testing", "design by contract", "specification tests", or dis...

principles

bchapuis1/13/2026

Core software design principles from 'A Philosophy of Software Design'. Use when asking about decomposition, deep modules, information hiding, complexity management, or John Ousterhout's design princi...

comments

bchapuis1/13/2026

Reviews code comments for quality. Use when reviewing documentation or evaluating if code is self-documenting.

complexity

bchapuis1/13/2026

Analyzes code for complexity issues. Use when code feels hard to understand, reviewing maintainability, or planning refactoring.

software-requirement

bchapuis1/13/2026

This skill should be used when the user asks to "write requirements", "define requirements", "create user stories", "formalize use cases", "functional requirements", "non-functional requirements", or...