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.development
Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.
development
Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
development
Implements a strict Red-Green-Refactor loop to ensure zero production code is written without a prior failing test. Use when: creating new features, fixing bugs, or expanding test coverage.
testing
Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.