Ariel Rodriguez

ps-composition-over-coordination tools

Build complexity by composing simple units, not orchestrating flows. Use when reviewing large functions or god objects.

ps-error-handling-design ai

Design systems with explicit error handling. Avoid throwing exceptions for domain errors. Use Result/Either types to...

ps-explicit-boundaries-adapters development

Isolates frameworks and external systems behind adapters. Use when reviewing code with tight framework coupling or...

ps-explicit-ownership-lifecycle development

Every resource must have clear ownership and lifetime. Use when reviewing resource management, subscriptions, or...

ps-explicit-state-invariants development

Ensures state is intentionally designed with explicit invariants. Use when reviewing stateful code, designing data...

ps-functional-core-imperative-shell data

Separate pure computation from side effects. Core business logic is pure functions, shell handles IO. Use when...

ps-illegal-states-unrepresentable development

System design should prevent misuse by construction. Use when reviewing defensive code with runtime checks.

ps-local-reasoning development

Ensures code is understandable locally without global context. Use when reviewing code with hidden dependencies or...

ps-minimize-mutation development

Mutation must be controlled and localized. Use when reviewing code with scattered mutations or shared mutable state.

ps-naming-as-design ai

Names must encode intent and constraints, not implementation. Use when reviewing vague or generic names.

ps-policy-mechanism-separation development

Business rules must be separated from execution mechanisms. Use when reviewing code with hardcoded rules in loops or...

ps-single-direction-data-flow development

Enforces unidirectional data flow with clear ownership. Use when reviewing data flows, debugging race conditions, or...