compose-screen-splitter

Audit and refactor monolithic Compose Screen files in the NutriSport KMP project.

11|Updated Mar 10, 2026

Search Tags:#architecture #split #refactor #kotlin #compose #screens #kmp

Ready to run

npx skills add https://github.com/satanyakiv/NutriSport --skill compose-screen-splitter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: compose-screen-splitter
Source: https://github.com/satanyakiv/NutriSport/tree/main/.claude/skills/compose-screen-splitter
Command: npx skills add https://github.com/satanyakiv/NutriSport --skill compose-screen-splitter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill audits and refactors monolithic Compose Screen files to keep the NutriSport KMP codebase maintainable, preventing unwieldy screens from slowing development.

Core Features & Use Cases

Detects threshold breaches (lines, @Composable count, nesting, and distinct UI concerns) and proposes project-consistent split points that preserve the Route↔Screen contract.
Operates in audit-only (read-only report) and execute (refactor) modes, including verification of compilation and tests after the split.
Uses a 5-step protocol (audit, classification via the decision tree, proposal, execution, verification) and respects project conventions for per-screen component placement and cross-feature reuse when applicable.

Quick Start

Ask to audit or split a Screen file using the defined trigger phrases.

Frequently Asked Questions about compose-screen-splitter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I split monolithic Compose screens in a Kotlin Multiplatform project?▼

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.

What triggers a Compose screen refactor in a KMP codebase?▼

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.

Can I audit Compose screen complexity before modifying the code?▼

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.

Does the Compose screen splitting process verify compilation and tests?▼

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.

What is the best way to maintain the Route contract when refactoring Compose screens?▼

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.