compose-reuse-checker

Detect Jetpack Compose UI theme and shared component misuse in Kotlin files.

2|Updated May 12, 2026
One-click install
npx skills add https://github.com/youfengknight/Android-Code-Skills --skill compose-reuse-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compose-reuse-checker
Source: https://github.com/youfengknight/Android-Code-Skills/tree/main/other/compose-reuse-checker
Command: npx skills add https://github.com/youfengknight/Android-Code-Skills --skill compose-reuse-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly detect when a Jetpack Compose screen hardcodes UI styles or bypasses your shared theme/components, which leads to inconsistent design and lower maintainability.

Core Features & Use Cases

  • Theme compliance checking: Verifies whether the screen uses LegadoTheme and required page-level color functions instead of hardcoded colors.
  • Reusable component usage audit: Flags missing usage of project components such as GlassCard/TextCard, AppModalBottomSheet, TopFloatingStickyItem, and CheckboxItem.
  • MaterialTheme consistency review: Ensures proper use of MaterialTheme.colorScheme and MaterialTheme.typography for standard components.
  • Use Case: Before refactoring a Compose screen, run this to confirm it already follows the project’s reuse and theming conventions to avoid redundant work.

Quick Start

Use compose-reuse-checker on the target Compose .kt file (the one containing @Composable functions) to get a report of incorrect theme usage, missing shared components, and actionable migration suggestions.

Frequently Asked Questions about compose-reuse-checker

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

FAQPage Schema
How do I check Jetpack Compose screens for hardcoded colors and theme misuse?

To check Jetpack Compose screens for hardcoded colors and theme misuse, analyze the file's imports and usages to verify it wraps content with LegadoTheme and uses page-level color functions instead of hardcoded values.

How do I enforce reusable component usage in a Kotlin Android codebase?

Enforce reusable component usage in a Kotlin Android codebase by auditing the Composable code to flag missing project components like GlassCard, TextCard, AppModalBottomSheet, TopFloatingStickyItem, and CheckboxItem during refactoring.

What is Material3 theme compliance for Jetpack Compose shared components?

Material3 theme compliance for Jetpack Compose shared components requires using MaterialTheme.colorScheme and MaterialTheme.typography instead of default styles to maintain consistency across the centralized design system.

Can I run a shared widget library audit before refactoring a Compose screen?

Yes, you can run a shared widget library audit before refactoring a Compose screen to confirm it already follows project reuse and theming conventions, helping you avoid redundant work and ensuring design consistency.

What are the limitations of automated Compose UI reuse checking?

Automated Compose UI reuse checking is limited to static analysis of imports and function usages within the target .kt file, meaning it applies specifically to codebases using a centralized design system and shared widget library.