android-coil-compose
Use Coil in Jetpack Compose with AsyncImage, painter variants, sizing, and accessible image loading patterns.
Works with
--- name: android-coil-compose description: Use Coil in Jetpack Compose with AsyncImage, painter variants, sizing, and accessible image loading patterns. license: MIT --- # Android Coil Compose ## When To Use - Use this skill when the request is about: coil compose image loading, asyncimage android compose, rememberasyncimagepainter android. - Primary outcome: Use Coil in Jetpack Compose with `AsyncImage`, painter variants, sizing, and accessible image loading patterns. - Reach for this skill when the work is specifically about image loading, placeholders, error states, sizing, or list performance in Compose. - Read `references/patterns.md` for the `AsyncImage` vs painter vs subcomposition decision guide. - Read `references/scenarios.md` for list-performance and screenshot-stable validation paths. - Handoff skills when the scope expands: - `android-compose-foundations` - `android-compose-performance` ## Workflow 1. Identify whether the UI needs a simple image surface, low-level painter access, or custom slot-based loading states. 2. Prefer `AsyncImage` first, then drop down to painter APIs only when the component truly needs them. 3. Constrain size, placeholders, and content description so the image behavior is both performant and accessible; for painter APIs, supply an explicit size resolver when needed. 4. Check list rendering, state churn, and visual fallbacks before considering the implementation done, and confirm that remote data or decoder modules are actually present when the source type needs them. 5. Hand off general Compose layout or broader performance issues to the neighboring skills after the image pipeline is stable. ## Guardrails - Prefer `AsyncImage` for most Compose surfaces. - Keep image requests sized to the rendered UI surface when possible. - Provide meaningful accessibility behavior: descriptive `contentDescription` for informative images, `null` for decorative ones. - Avoid subcomposition-heavy image patterns in scroll-heavy lists unless the UX truly needs them. - If you need painter state directly, remember that `rememberAsyncImagePainter` does not infer on-screen size by itself. ## Anti-Patterns - Loading full-size remote assets into tiny list items. - Using `SubcomposeAsyncImage` everywhere when a simple placeholder is enough. - Treating image loading failures as silent no-ops with no error fallback. - Forgetting accessibility semantics on actionable or informative images. ## Review Focus - API choice: `AsyncImage`, `rememberAsyncImagePainter`, or `SubcomposeAsyncImage`. - Correct sizing and request construction for the rendered surface. - Remote-loading prerequisites such as the right Coil network modules. - Stable placeholders and error states for lists, tests, and screenshots. ## Examples ### Happy path - Scenario: Build the Compose fixture and verify a stable `AsyncImage` surface renders in the task board. - Command: `bash skills/android-coil-compose/scripts/run_examples.sh` ### Edge case - Scenario: Review a list cell where placeholders, sizing, and lazy-list performance all matter. - Command: `cd examples/orbittasks-compose && ./gradlew :app:testDebugUnitTest` ### Failure recovery - Scenario: Re-check the image surface after a placeholder or error-state change using screenshot-friendly validation. - Command: `cd examples/orbittasks-compose && ./gradlew verifyRoborazziDebug` ## Done Checklist - `AsyncImage` is the default unless a lower-level painter API is justified. - Sizing, placeholders, and error states are explicit. - Accessibility behavior is intentional. - List and screenshot behavior has been validated on the Compose fixture. ## Official References - [https://coil-kt.github.io/coil/compose/](https://coil-kt.github.io/coil/compose/) - [https://coil-kt.github.io/coil/image_requests/](https://coil-kt.github.io/coil/image_requests/) - [https://coil-kt.github.io/coil/network/](https://coil-kt.github.io/coil/network/) - [https://developer.android.com/develop/ui/compose/graphics/images/loading](https://developer.android.com/develop/ui/compose/graphics/images/loading) - [https://developer.android.com/develop/ui/compose/accessibility](https://developer.android.com/develop/ui/compose/accessibility)
More Accessibility skills
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Also covers Tailwind projects and the STORYBOARD.md / SCRIPT.md plan formats. Read before writing composition HTML.
ui-ux-pro-max
nextlevelbuilder/ui-ux-pro-max-skill
UI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation. Searchable local data: 79 searchable styles (50 active), 192 product palettes and reasoning profiles, 74 font pairings, 119 UX guidelines, 105 icons, 17 GSAP presets, 25 chart types, and 22 stacks.

