Jetpack Compose Styles Integration Skill
Integrate the Jetpack Compose Styles API into an Android project for unified theming and layout migration.
Evidence shows the skill is based on official documentation, no malicious behavior, operations limited to build configs and file creation, low risk. However, publisher identity unverified, no dependency audit or rollback mechanisms, so deducted.
Steps are clear, but no automated tests or execution verification, error feedback on abnormal input insufficient, static review limits reliability score.
Clearly scoped for experimental APIs and custom components, but lacks detailed non-fit boundaries, and reference docs may be unreachable from China, affecting adaptability.
Documentation is well-structured with limitations, prerequisites, and step-by-step guide, but lacks version history, troubleshooting, and clear maintenance responsibility, publisher unverified.
Core task (migration to Styles) steps are plausible, but output direct usability unverified, no comparative benefit evidence.
Relies on official docs, no independently reproducible evidence provided, static review cannot verify execution.
- This skill relies on experimental APIs requiring alpha version upgrades, which may cause instability in production.
- Reference documentation links may be unreachable from mainland China; note network accessibility.
- Publisher identity is unverified; assess before use.
What does this skill do, and when should you use it?
This skill guides developers in migrating a Jetpack Compose project to the new Styles API. It covers dependency upgrades, compiler configuration, setting up component themes, making custom components styleable, and migrating hard-coded layout properties to unified styles. The skill provides a step-by-step workflow including creating ComponentStyles, migrating custom components, and visual regression validation. Note: this skill is experimental, requires a Compose alpha version, supports only custom components and themes, and does not support Material Design component styles.
Reads the project's theme files and component code to analyze design tokens and existing parameters; instructs upgrading compileSdk to 37+ and foundation to 1.12.0-alpha01+ with compiler opt-in flags; creates a ComponentStyles data class and exposes it via the custom theme; for each custom component, removes individual style parameters, adds a style parameter, uses Modifier.styleable, and manages interaction state; after migration, guides building, screenshot testing, and visual comparison.
- Android developers wanting to use unified Style definitions for custom component libraries to reduce duplication.
- Teams migrating existing Compose custom buttons, text fields, and other components to the Styles API for centralized theming.
- Design system maintainers linking design tokens (colors, typography, shapes) to component styles.
- Developers refactoring component signatures to remove redundant parameters without breaking visuals.
What are this skill's strengths and limitations?
- Provides clear step-by-step migration workflow, reducing errors
- Emphasizes visual baseline verification to ensure visual parity
- Supports custom themes and design token integration
- Maintained by Google with reference to official docs
- Experimental API requiring Compose alpha, potentially unstable
- Only supports custom components, not Material Design component styles
- Requires manual dependency and compiler updates, with many prerequisites
- No automated tests provided; manual screenshot comparison needed
How do you install this skill?
This skill is part of the Android skills collection; install via Android CLI: run 'android skills add --skill=styles --project=.' to install into the current project, or 'android skills add --all' for all skills.
How do you use this skill?
In an agent environment, add the skill directory to the agent's skills path and trigger with a prompt like 'Help me migrate my custom button to the Styles API'. The skill guides through steps: upgrade dependencies, configure compiler, create ComponentStyles, migrate components, and validate.