edge-to-edge
Skill1k starsChanged 4 days agoApache-2.0View on GitHub
Use this skill to migrate your Jetpack Compose app to add adaptive edge-to-edge
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 3 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 33
Add enableEdgeToEdge before setContent in onCreate in each Activity that does not already call enableEdgeToEdge.
- Very specific: line 34
Add android:windowSoftInputMode="adjustResize" in the AndroidManifest.xml for all Activities that use a soft keyboard.
- Very specific: line 41
PREFERRED: When available, use Scaffolds and pass PaddingValues to the content lambda.
- Distinctive: line 58
PREFERRED: When available, use the automatic inset handling or padding modifiers in material components.
- Very specific: line 99
When you need an element (e.g.
- Very specific: line 298
If the Activity uses enableEdgeToEdge from WindowCompat, you MUST set isAppearanceLightNavigationBars and isAppearanceLightStatusBars to …
- Very specific: line 302
DO NOT do this if the Activities use enableEdgeToEdge from ComponentActivity because it handles the icon colors automatically.
- Very specific: line 332
If any screen uses a Scaffold or a NavigationSuiteScaffold with a bottom bar (e.g., BottomAppBar, NavigationBar), set …
- Distinctive: line 342
Create a translucent composable covering the system bar so that the icons are still legible.
- Distinctive: line 396
If both the following conditions are true, then the Dialog is full screen and must be made edge-to-edge:
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Prerequisites
- Project MUST use Android Jetpack Compose.
- Project MUST target SDK 35 or later. If the SDK is lower than 35, increase the SDK to 35.
Step 1: plan
- Locate and analyze all Activity classes to detect which have existing edge-to-edge support. For every Activity without edge-to-edge, plan to make each Activity edge-to-edge.
- In each Activity, Locate and analyze all lists and FAB components to detect which have existing edge-to-edge support. For every component without edge-to-edge support, plan to make each of these components edge-to-edge.
- In each Activity, scan for
TextField,OutlinedTextField, orBasicTextField. If found, then you MUST verify the IME doesn't hide the input field by following the IME section of this skill.
Step 2: add edge-to-edge support
- Add
enableEdgeToEdgebeforesetContentinonCreatein each Activity that does not already callenableEdgeToEdge. - Add
android:windowSoftInputMode="adjustResize"in the AndroidManifest.xml for all Activities that use a soft keyboard.
Step 3: apply insets
The app MUST apply system insets, or align content to rulers, so critical UI remains tappable. Choose only one method to avoid double padding:
- PREFERRED: When available, use
Scaffolds and passPaddingValuesto the content lambda.
Scaffold { innerPadding -> // innerPadding accounts for system bars and any Scaffold components LazyColumn( modifier = Modifier .fillMaxSize() .consumeWindowInsets(innerPadding), contentPadding = innerPadding ) { /* Content */ } }<br />PREFERRED: When available, use the automatic inset handling or padding modifiers in material components.
- Material 3 Components manages safe areas for its own components, including:
TopAppBarSmallTopAppBarCenterAlignedTopAppBarMediumTopAppBarLargeTopAppBarBottomAppBarModalDrawerSheetDismissibleDrawerSheetPermanentDrawerSheetModalBottomSheetNavigationBarNavigationRail
- For Material 2 Components, use the
windowInsetsparameter to apply insets manually forBottomAppBar,TopAppBarandBottomNavigation. DO NOT apply padding to the parent container; instead, pass insets directly to the App Bar component. Applying padding to the parent container prevents the App Bar background from drawing into the system bar area. For example, forTopAppBar, choose only one of the following options:- PREFERRED:
TopAppBar(windowInsets = AppBarDefaults.topAppBarWindowInsets) TopAppBar(windowInsets = WindowInsets.systemBars.exclude(WindowInsets.navigationBars))TopAppBar(windowInsets = WindowInsets.systemBars.add(WindowInsets.captionBar))
- PREFERRED:
- Material 3 Components manages safe areas for its own components, including:
For components outside a Scaffold, use padding modifiers, such as
Modifier.safeDrawingPadding()orModifier.windowInsetsPadding(WindowInsets.safeDrawing).Box( modifier = Modifier .fillMaxSize() .safeDrawingPadding() ) { Button( onClick = {}, modifier = Modifier.align(Alignment.BottomCenter) ) { Text("Login") } }<br />- For deeply nested components with excessive padding, use
WindowInsetsRulers(e.g.Modifier.fitInside(WindowInsetsRulers.SafeDrawing.current)). See the IME section for a code sample. - When you need an element (e.g. a custom header or decorative scrim) to
equal the dimensions of a system bar, use inset size modifiers (e.g.
Modifier.windowInsetsTopHeight(WindowInsets.systemBars)). See the Lists section for a code sample.
- PREFERRED: When available, use
Adaptive Scaffolds
NavigationSuiteScaffoldmanages safe areas for its own components, like theNavigationRailorNavigationBar. However, the adaptive scaffolds (e.g.NavigationSuiteScaffold,ListDetailPaneScaffold) don't propagate PaddingValues to their inner contents. You MUST apply insets to individual screens or components (e.g., listcontentPaddingor FAB padding) as described in Step 3 . DO NOT applysafeDrawingPaddingor similar modifiers to theNavigationSuiteScaffoldparent. This clips and prevents an edge-to-edge screen.
IME
- For each Activity with a soft keyboard, check that
android:windowSoftInputMode="adjustResize"is set in the AndroidManifest.xml. DO NOT useSOFT_INPUT_ADJUST_RESIZEbecause it is deprecated. Then, maintain focus on the input field. Choose one:- PREFERRED: Add
Modifier.fitInside(WindowInsetsRulers.Ime.current)to the content container. This is preferred overimePadding()because it reduces jank and extra padding caused by forgetting to consume insets upstream in the hierarchy.
- PREFERRED: Add
- Add
imePaddingto the content container. The padding modifier MUST be placed beforeModifier.verticalScroll(). Do NOT useModifier.imePadding()if the parent already accounts for the IME withcontentWindowInsets(e.g.contentWindowInsets = WindowInsets.safeDrawing). Doing so will cause double padding.
- Add
IMEs with Scaffolds code patterns
RIGHT
RIGHT because contentWindowInsets contains IME insets, which are passed to the
content lambda as innerPadding.
// RIGHT
Scaffold(contentWindowInsets = WindowInsets.safeDrawing) { innerPadding ->
Column(
modifier = Modifier
.padding(innerPadding)
.consumeWindowInsets(innerPadding)
.verticalScroll(rememberScrollState())
) { /* Content */ }
}<br />RIGHT because fitInside fits the content to the IME insets regardless of
contentWindowInsets.
// RIGHT
Scaffold() { innerPadding ->
Column(
modifier = Modifier
.padding(innerPadding)
.consumeWindowInsets(innerPadding)
.fitInside(WindowInsetsRulers.Ime.current)
.verticalScroll(rememberScrollState())
) { /* Content */ }
}<br />RIGHT because the default contentWindowInsets does not contain IME insets, and
imePadding() applies IME insets:
// RIGHT
Scaffold() { innerPadding ->
Column(
modifier = Modifier
.padding(innerPadding)
.consumeWindowInsets(innerPadding)
.imePadding()
.verticalScroll(rememberScrollState())
) { /* Content */ }
}<br />WRONG
WRONG because there will be excess padding when the IME opens. IME insets are
applied twice, once with innerPadding, which contains IME insets from the passed
contentWindowInsets values, and once with imePadding:
// WRONG
Scaffold(contentWindowInsets = WindowInsets.safeDrawing) { innerPadding ->
Column(
modifier = Modifier
.padding(innerPadding)
.imePadding()
.verticalScroll(rememberScrollState())
) { /* Content */ }
}<br />WRONG because the IME will cover up the content. Scaffold's default
contentWindowInsets does NOT contain IME insets.
// WRONG
Scaffold() { innerPadding ->
Column(
modifier = Modifier
.padding(innerPadding)
.verticalScroll(rememberScrollState())
) { /* Content */ }
}<br />IMEs without Scaffolds code patterns
RIGHT
The following code samples WILL NOT cause excessive padding.
// RIGHT
Box(
// Insets consumed
modifier = Modifier.safeDrawingPadding() // or imePadding(), safeContentPadding(), safeGesturesPadding()
) {
Column(
modifier = Modifier.imePadding()
) { /* Content */ }
}<br />// RIGHT
Box(
// Insets consumed
modifier = Modifier.windowInsetsPadding(WindowInsets.safeDrawing) // or WindowInsets.ime, WindowInsets.safeContent, WindowInsets.safeGestures
) {
Column(
modifier = Modifier.imePadding()
) { /* Content */ }
}<br />// RIGHT
Box(
// Insets not consumed, but irrelevant due to fitInside
modifier = Modifier.padding(WindowInsets.safeDrawing.asPaddingValues()) // or WindowInsets.ime.asPaddingValues(), WindowInsets.safeContent.asPaddingValues(), WindowInsets.safeGestures.asPaddingValues()
) {
Column(
modifier = Modifier
.fillMaxSize()
.fitInside(WindowInsetsRulers.Ime.current)
) { /* Content */ }
}<br />WRONG
The following code sample WILL cause excessive padding because IME insets are applied twice:
// WRONG
Box(
// Insets not consumed
modifier = Modifier.padding(WindowInsets.safeDrawing.asPaddingValues()) // or WindowInsets.ime.asPaddingValues(), WindowInsets.safeContent.asPaddingValues(), WindowInsets.safeGestures.asPaddingValues()
) {
Column(
modifier = Modifier.imePadding()
) { /* Content */ }
}<br />Navigation Bar Contrast & System Bar Icons
If the Activity uses
enableEdgeToEdgefromWindowCompat, you MUST setisAppearanceLightNavigationBarsandisAppearanceLightStatusBarsto the inverse of the device theme for apps that support light and dark theme so the system bar icons are legible. It's recommended to do this in your theme file. DO NOT do this if the Activities useenableEdgeToEdgefromComponentActivitybecause it handles the icon colors automatically.// Only use if calling `enableEdgeToEdge` from `WindowCompat`. // Apply to your theme file. @Composable fun MyTheme( darkTheme: Boolean = isSystemInDarkTheme(), content: @Composable () -> Unit ) { val view = LocalView.current if (!view.isInEditMode) { SideEffect { val window = (view.context as? Activity)?.window ?: return@SideEffect val controller = WindowCompat.getInsetsController(window, view) // Dark icons for Light Mode (!darkTheme), Light icons for Dark Mode controller.isAppearanceLightStatusBars = !darkTheme controller.isAppearanceLightNavigationBars = !darkTheme } } MaterialTheme(content = content) }<br />- If any screen uses a
Scaffoldor aNavigationSuiteScaffoldwith a bottom bar (e.g.,BottomAppBar,NavigationBar), setwindow.isNavigationBarContrastEnforced = falsein the corresponding Activity for SDK 29+. This prevents the system from adding a translucent background to the navigation bar, verifying your bottom bar colors extend to the bottom of the screen.
Lists
- Apply inset padding (like
Scaffold'sinnerPadding) to thecontentPaddingparameter of scrollable components (e.g.LazyColumn,LazyRow). DO NOT apply it as aModifier.padding()to the list's parent container, as this clips the content and prevents it from scrolling behind the system bars. - Create a translucent composable covering the system bar so that the icons are still legible.
class SystemBarProtectionSnippets : ComponentActivity() {
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
// enableEdgeToEdge sets window.isNavigationBarContrastEnforced = true
// which is used to add a translucent scrim to three-button navigation
enableEdgeToEdge()
setContent {
MyTheme {
// Main content
MyContent()
// After drawing main content, draw status bar protection
StatusBarProtection()
}
}
}
}
@Composable
private fun StatusBarProtection(
color: Color = MaterialTheme.colorScheme.surfaceContainer,
) {
Spacer(
modifier = Modifier
.fillMaxWidth()
.height(
with(LocalDensity.current) {
(WindowInsets.statusBars.getTop(this) * 1.2f).toDp()
}
)
.background(
brush = Brush.verticalGradient(
colors = listOf(
color.copy(alpha = 1f),
color.copy(alpha = 0.8f),
Color.Transparent
)
)
)
)
}<br />Dialogs
If both the following conditions are true, then the Dialog is full screen and must be made edge-to-edge:
- The
DialogPropertiescontainsusePlatformDefaultWidth = false. - The Dialog calls
Modifier.fillMaxSize().
To make a full screen Dialog edge-to-edge, set decorFitsSystemWindows = false
in the DialogProperties.
Dialog(
onDismissRequest = { /* Handle dismiss */ },
properties = DialogProperties(
// 1. Allows the dialog to span the full width of the screen
usePlatformDefaultWidth = false,
// 2. Allows the dialog to draw behind status and navigation bars
decorFitsSystemWindows = false
)
) { /* Content */ }<br />Checklist
- [ ] Does every
ActivitycallenableEdgeToEdge()? - [ ] Is
adjustResizeset in theAndroidManifest.xml? - [ ] Does every
TextField,OutlinedTextField, orBasicTextFieldhave a parent withimePadding(),fitInside,Modifier.safeDrawingPadding(),Modifier.safeContentPadding(),Modifier.safeGesturesPadding(), orcontentWindowInsetsset toWindowInsets.safeDrawingorWindowInsets.ime? - [] Does the first and last list item draw away from the system bars by passing insets to
contentPadding? - [] Do FABs draw above the navigation bars by either being inside a Scaffold or by applying
Modifier.safeDrawingPadding()? - [] Does the project build? Run
./gradlew buildto be sure.
Other versions5 projects use a version of this.
Word for word · 4
- rosuH/EasyWatermark★ 1.9k100% same
- gug007/lpm★ 149100% same
- deonmenezes/mobile-app-skill★ 4100% same
- MKS-01/appscreenmap★ 2100% same
Edited · 1
- kid1412621/SummaryExpressive★ 21798% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use play-policy-insights.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
deonmenezesSkillplay-policy-insights
Automated auditor designed to verify Android applications against Google Play Policy domains. It cross-references static code analysis with Play Store declarations to generate deterministic compliance reports, identifying undeclared data collection, architectural risks, and missing disclosures across Permissions and APIs Hygiene, User Account and Identity, and Data Safety and Privacy domains.
Also in 3 projects that use this
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adaptiveSkill
- android-profilerSkill
- anr-audit-and-fixSkill
- glance-appwidget-updates-and-memorySkill
- glance-canonical-layoutsSkill
- jetpack-compose-performanceSkill
- litert-lmSkill
- litert-runtimeSkill
- ml-kit-genai-prompt-apiSkill
- navigation-3Skill
- navigation-eventSkill
- r8-analyzerSkill
- testing-setupSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

