compose-screen-splitter

You can split monolithic Compose screens by auditing files for threshold breaches in lines, composable count, nesting, or distinct UI concerns, then applying a 5-step protocol to classify, propose, execute, and verify the refactored splits while preserving the Route contract.

A Compose screen refactor triggers when a Screen file exceeds defined thresholds for total lines, @Composable count, nesting depth, or contains multiple distinct UI concerns that make the monolithic file unmanageable.

Yes, you can run an audit-only mode that generates a read-only report evaluating Compose screen complexity and threshold breaches without executing any refactoring changes to the actual codebase.

Yes, the execute mode runs a verification step after splitting the Compose screen to ensure the refactored modules compile correctly and existing tests pass according to project conventions.

The best way to maintain the Route contract during a Compose screen refactor is to use a decision tree that proposes project-consistent split points for per-screen components and cross-feature reuse without breaking navigation.