Design Coaching

Coach design judgment on Android/Kotlin/Compose code — evaluate the shape by reasoning from design principles in tension, not by matching a catalog of bad forms, and teach the author to see the forks themselves. Use when reviewing code (often the user's own) to help them design better, or when weighing a design fork — inheritance vs composition, what to expose at a boundary, a value class vs a raw primitive, a data class vs a sealed hierarchy for state, where to validate input — when you ask "is this the right shape" or "where could this be misused", or for a design pass before committing. Coaches the author toward better judgment, not just fixes; to write review comments…