android-image
/android-image
Integrate image loading in Kotlin Android projects with Coil AppImage or Glide ImageView helpers. Use for Compose, XML ViewBinding, Coil, Glide, placeholders or image Recipe status. Preserve the image library already used by the project.
- Author
- smallmarker ↗
- Repository
- android-stack-skills ↗
- Licence
- MIT
- Last repository change
- 06.11.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 06.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Integrate image loading in Kotlin Android projects with Coil AppImage or Glide ImageView helpers. Use for Compose, XML ViewBinding, Coil, Glide, placeholders or image Recipe status. Preserve the image library already used by the project.
Original author description
Integrate image loading in Kotlin Android projects with Coil AppImage or Glide ImageView helpers. Use for Compose, XML ViewBinding, Coil, Glide, placeholders or image Recipe status. Preserve the image library already used by the project.
How it works
- CLI readiness
SKILL.md preview
--- name: android-image description: Integrate image loading in Kotlin Android projects with Coil AppImage or Glide ImageView helpers. Use for Compose, XML ViewBinding, Coil, Glide, placeholders or image Recipe status. Preserve the image library already used by the project. license: MIT --- ## CLI readiness Before any Android operation, read [cli-requirements.json](cli-requirements.json) and [cli-setup.md](cli-setup.md). Check the trusted executable with `android-stack capabilities --json` and compare the protocol, capabilities and Recipe versions. Stop and ask for approval before preparing a missing or incompatible CLI. Use the same checked executable for the workflow. Requires android-stack, Python 3.11+, JDK 17 and an Android SDK for builds. 1. Run `android-stack inspect --project <path> --json` and `android-stack status --project <path>`. Select the target module explicitly with `--module` if needed. Read the selected module's `image_libraries`, `compose`, `view_binding` and `xml_layouts`. Confirm ambiguous results in Gradle declarations and source imports. For status-only requests, report without writing. 2. Preserve an existing Coil or Glide library and its version. If both are present, inspect the specific screen and ask which integration to extend if still ambiguous. If the requested library conflicts with the existing one, report the conflict and stop automatic installation. An explicit library choice is not authorization to migrate, remove or add a competing library. 3. For a module without an image library, honor an explicit supported choice. Otherwise use `coil-standard` for Compose screens and `glide-standard` for XML Views. For mixed UI choose based on the target screen. `coil-standard` requires Compose. `glide-standard` targets ImageView and can run in Compose via AndroidView. For XML-only + Coil, report that the existing Coil Recipe cannot generate a Views integration and preserve any existing Coil code. 4. Run `android-stack plan --project <path> --recipe <recipe>`. Review version and file conflicts before `android-stack install --project <path> --recipe <recipe>`. Require INTERNET permission and preserve Application and screen code. Do not bypass a conflict by rewriting dependencies or overwriting source. A repeated install should report already-installed. 5. Read the generated `app/android-stack/image/Usage.md` in the selected module. For Coil, initialize AppImages in Application.onCreate only if appropriate for the existing loader. For Glide, call loadGlide on an ImageView on the main thread and clear requests on disposal or recycling as documented. Match placeholders, size and accessibility to the screen. 6. Run `android-stack verify --project <path>` with the same module. Report the build and test outcomes. On a failed build, preserve diagnostics. If a write is interrupted, inspect the journal and use `android-stack recover` only after confirming no live installer owns the lock.
Files in this package (3)
- SKILL.md 3 KB
- cli-requirements.json 1 KB
- cli-setup.md 4 KB
Versions
The database has no other skills named android-image.
Database snapshot: 13.11.2026 · package version 84b89c69595f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100android-project
Create a Kotlin Android Compose or XML ViewBinding MVVM project with Retrofit, Coil or Glide, and Timber using Android Stack Skills. Use for new Android apps, Lightweight scaffolding, or a Standard project with Hilt. Does not migrate an existing application's architecture. - 100coil-compose
Expert guidance on using Coil for image loading in Jetpack Compose. Use this when asked about loading images from URLs, handling image states, or optimizing image performance in Compose. - 95coil-compose
Use when loading images in Compose or Compose Multiplatform with Coil 3 — AsyncImage vs SubcomposeAsyncImage vs rememberAsyncImagePainter, ImageRequest configuration, placeholder/error states, performance in lists, and KMP setup with LocalPlatformContext. - 95android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices. - 90kotlin-android
Build and upgrade native Android applications with Kotlin, Compose/View UI and lifecycle-aware work. Use when implementing Android screens, navigation, permissions or background jobs; coordinate Kotlin, Gradle, AGP and SDK compatibility. - 100android-kotlin-jetpack-compose-ui
Use this skill when building modern native Android user interfaces declaratively using Kotlin, Compose modifiers, and state hoisting.