ode-scheme-evaluation-max

What problem does it solve?

It helps you objectively evaluate whether an Android code solution or design approach is sound, especially for hybrid Jetpack Compose + View projects, reducing the risk of architecture drift, hidden state-sync bugs, and performance issues.

Core Features & Use Cases

• Architecture & logic assessment: Reviews module boundaries, dependency direction, and implementation correctness, including the required deep checks for data-source consistency and user-operation real-world effects.
• Feasibility, difficulty, and debuggability scoring: Assesses technical feasibility, migration complexity (View to Compose), and how hard the solution will be to diagnose in production.
• Compose/View hybrid & state synchronization specialization: Validates interoperability APIs, lifecycle alignment, focus/gesture behavior, and whether all UI stays consistent when shared configuration changes.

Use case examples:

• You are proposing a new Compose navigation/data flow while legacy View screens still exist, and you need an evaluation of compatibility and maintainability.
• A UI selection/configuration seems to “not take effect” reliably across multiple screens, and you need a structured diagnosis of state sync and data-source issues.

Quick Start

Ask the skill to evaluate a specific Android code/design idea by providing the relevant context, the current implementation approach, and what user action or data flow you expect to work.