一键导入
android-accessibility
Expert checklist and prompts for auditing and fixing Android accessibility issues, especially in Jetpack Compose.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Expert checklist and prompts for auditing and fixing Android accessibility issues, especially in Jetpack Compose.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Expert guidance on setting up and maintaining a modern Android application architecture using Clean Architecture and Hilt. Use this when asked about project structure, module setup, or dependency injection.
Authoritative rules and patterns for production-quality Kotlin Coroutines onto Android. Covers structured concurrency, lifecycle integration, and reactive streams.
Guidance on implementing the Data Layer using Repository pattern, Room (Local), and Retrofit (Remote) with offline-first synchronization.
Production-ready scripts for Android app testing, building, and automation. Provides semantic UI navigation, build automation, log monitoring, and emulator lifecycle management. Optimized for AI agents with minimal token output.
Expert guidance on setting up scalable Gradle build logic using Convention Plugins and Version Catalogs.
Expert guidance on setting up and using Retrofit for type-safe HTTP networking in Android. Covers service definitions, coroutines, OkHttp configuration, and Hilt integration.
| name | android-accessibility |
| description | Expert checklist and prompts for auditing and fixing Android accessibility issues, especially in Jetpack Compose. |
Analyze the provided component or screen for the following accessibility aspects.
Image and Icon composables have a meaningful contentDescription?contentDescription = null.MinTouchTargetSize or wrap in Box with appropriate padding if the visual icon is smaller.Modifier.semantics(mergeDescendants = true) for complex items (like a row with text and icon) so they are announced as a single item.stateDescription to describe custom states (e.g., "Selected", "Checked") if standard semantics aren't enough.Modifier.semantics { heading() } to allow screen reader users to jump between sections.