skills/android/android-edge-to-edge/SKILL.md
Migrate a Jetpack Compose app to edge-to-edge display and fix system bar inset issues. Use when UI components are obscured by navigation/status bars, fixing IME insets, or enabling edge-to-edge for SDK 35+.
npx skillsauth add hoangnguyen0403/agent-skills-standard android-edge-to-edgeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Structured workflow for migrating a Compose app to edge-to-edge display.
compileSdk to 35.enableEdgeToEdge(), plan to add it.TextField/OutlinedTextField is present, plan IME inset handling.enableEdgeToEdge() before setContent in every Activity.onCreate.android:windowSoftInputMode="adjustResize" in AndroidManifest for Activities with soft keyboard.Choose ONE method per component to avoid double padding:
PaddingValues to content lambda.TopAppBar, NavigationBar, etc.).Modifier.safeDrawingPadding() or windowInsetsPadding.See inset patterns for RIGHT/WRONG code examples.
For Activities with soft keyboard:
adjustResize in manifest (NOT deprecated SOFT_INPUT_ADJUST_RESIZE).imePadding() or fitInside(WindowInsetsRulers.Ime.current) to content container.imePadding BEFORE verticalScroll().See inset patterns for IME-specific RIGHT/WRONG patterns.
contentPadding of LazyColumn/LazyRow, NOT as Modifier.padding() on parent.safeDrawingPadding().Activity calls enableEdgeToEdge().adjustResize set in AndroidManifest for keyboard Activities.contentPadding../gradlew build succeeds.contentWindowInsets = WindowInsets.safeDrawing with imePadding() on the same content — causes double padding when IME opens.contentPadding, not parent Modifier.padding() — parent padding clips scrolling content.SOFT_INPUT_ADJUST_RESIZE: Deprecated. Use manifest adjustResize attribute.testing
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
documentation
Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.
development
Design relational or document schemas from access patterns, cardinality, and lifecycle. Use when modeling entities, choosing embed vs normalize, or shaping schema boundaries before implementation.
data-ai
Diagnose database latency with explain plans, index ownership, and query-shape review. Use when a query is slow, an index is missing, or scans and N+1 patterns appear.