oo-design

To brainstorm an object-oriented design, you describe your domain and the system proposes a structured OO plan with named tradeoffs, often contrasting with functional or hybrid alternatives. It routes your request by intent to produce a design doc without writing code.

Common OO architecture pitfalls include anemic domains, bad aggregate boundaries, inheritance misuse, and value object issues. A design critique identifies these failure surfaces, ranks them by severity, and proposes fixes based on SOLID and domain-driven design principles.

You should consider hybrid or functional alternatives when your proposed OO design exhibits structural tradeoffs where immutable data flows or pure functions solve the problem more cleanly than object hierarchies. The critique surfaces these alternatives honestly.

To critique a proposed OO architecture, you submit your design and the system analyzes it for inheritance misuse, aggregate boundary errors, value object issues, and SOLID violations. It produces a severity-ranked critique with targeted fixes and recommendations.

Yes, you can review proposed designs that mix OO with functional programming tradeoffs. The system evaluates hybrid architectures, applying an OO lineage lens to assess the design and recommend when a functional or hybrid approach is better.

This object-oriented design guidance produces design documents and severity-ranked critiques without writing code. It focuses on routing your intent, selecting patterns, modeling aggregates, and surfacing architectural tradeoffs rather than generating implementation.