⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
android-design-guidelines
Material Design 3 and Android platform guidelines. Use when building Android apps with Jetpack Compose or XML layouts, implementing Material You, navigation, or accessibility. Triggers on tasks involving Android UI, Compose components, dynamic color, or Material Design compliance.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
Platform Design Skills
Platform design skill pack: 450+ rules for Apple HIG, Material Design 3, and WCAG 2.2 across iOS, iPadOS, macOS, watchOS, visionOS, tvOS, Android, and Web.
Built by scraping the Apple Human Interface Guidelines (a compiled PDF version is included in this repo) and distilling it — along with Material Design 3 and WCAG 2.2 — into succinct but exhaustive skill files. Use them to evaluate, improve, or create your designs.
Available Skills
ios
Apple Human Interface Guidelines for iPhone. 67+ rules covering navigation, layout, accessibility, gestures, and iOS-specific components like tab bars, sheets, and Dynamic Island.
Use when:
- Building SwiftUI or UIKit interfaces for iPhone
- Reviewing iOS app code for HIG compliance
- Choosing between iOS navigation patterns
- Implementing accessibility, Dark Mode, Dynamic Type
ipados
Apple HIG for iPad, covering multitasking, pointer support, sidebar navigation, keyboard shortcuts, and Stage Manager. Extends the iOS skill with iPad-specific patterns.
Use when:
- Building iPad-optimized interfaces
- Implementing Split View, Slide Over, Stage Manager support
- Adding pointer/trackpad and keyboard shortcut support
- Designing responsive layouts for iPad screen sizes
macos
Apple HIG for Mac apps. Covers menu bars, window management, toolbars, keyboard-driven interaction, and the expectations of desktop power users.
Use when:
- Building macOS apps with SwiftUI or AppKit
- Implementing menu bars, toolbars, and sidebars
- Adding keyboard shortcuts and window management
- Designing for Catalyst or native macOS
watchos
Apple HIG for Apple Watch. Covers glanceable interfaces, Digital Crown, complications, Always On display, and wrist-optimized interactions.
Use when:
- Building watchOS apps or complications
- Designing for small screens and short interactions
- Implementing health/fitness features on Watch
visionos
Apple HIG for Apple Vision Pro. Covers spatial UI, eye and hand input, windows, volumes, immersive spaces, and ornaments.
Use when:
- Building visionOS apps with RealityKit or SwiftUI
- Designing for spatial computing and indirect gestures
- Implementing immersive experiences
tvos
Apple HIG for Apple TV. Covers focus-based navigation, Siri Remote, Top Shelf, and living room viewing distances.
Use when:
- Building tvOS apps
- Implementing focus-based navigation with Siri Remote
- Designing for 10-foot viewing experiences
android
Google Material Design 3 guidelines for Android. Covers Material You, dynamic color, navigation patterns, components, and Android-specific patterns.
Use when:
- Building Android apps with Jetpack Compose or XML layouts
- Reviewing Android code for Material Design compliance
- Implementing Material You and dynamic color
- Choosing between Android navigation patterns
web
Web platform best practices covering responsive design, accessibility (WCAG), performance, progressive enhancement, and modern CSS/HTML patterns.
Use when:
- Building web interfaces with any framework
- Auditing sites for accessibility compliance
- Implementing responsive, performant web layouts
- Reviewing web UI code for best practices
Installation
npx skills add ehmo/platform-design-skills
Contributing (Pull Requests)
- Fork the repository and create a feature branch from the default branch.
- Keep PRs focused to one theme (one platform, one major design area, or one format rule set).
- Update affected skill docs in
skills/<platform>/SKILL.mdand keepmetadata.jsonentries aligned when behavior changes. - If adding or changing rule coverage, ensure:
- platform skill descriptions remain accurate,
- source signals in the skill files are still correct,
- and examples still reflect current platform behavior.
- In the PR description include:
- what changed,
- why this matters for AI output quality,
- and a short before/after usage sample.
- Suggested PR title format:
feat: ...,fix: ...,docs: ....
Example PR checklist:
- Scope matches the PR title
- One platform or one rule family per PR
- No broken relative links in touched files
- AGENTS/skill assumptions still stated clearly
- README and skill metadata remain consistent
Usage
Skills activate automatically when agents detect platform-relevant tasks.
Review this SwiftUI view for iOS HIG compliance
Check this Android Compose screen against Material Design
Audit this web page for accessibility
Skill Structure
Each skill contains:
SKILL.md— Agent instructions with frontmatter metadatametadata.json— Version, references, and abstractrules/— Individual rule files with examplesAGENTS.md— Quick context for agent consumption
Sources
Platform-normative sources
- Apple Human Interface Guidelines (2025) — developer.apple.com/design/human-interface-guidelines
- Material Design 3 — m3.material.io
- Web Content Accessibility Guidelines (WCAG) 2.2 — w3.org/WAI/WCAG22/quickref
- MDN Web Docs — developer.mozilla.org
Supporting HCI references
These are secondary references used to sharpen guidance around recognition over recall, visible waiting states, and input effort. They do not override Apple HIG, Material, or WCAG.
- Stuart K. Card, Thomas P. Moran, and Allen Newell, The Psychology of Human-Computer Interaction (1983) — https://archive.org/details/psychologyofhuma0000card
- Allen Newell and Stuart K. Card, Prospects for Psychological Science in Human-Computer Interaction (includes Model Human Processor summary and operating principles) — https://iiif.library.cmu.edu/file/Newell_box00042_fld03533_doc0001/Newell_box00042_fld03533_doc0001.pdf
- Tiffany Jastrzembski and Neil Charness, The Model Human Processor and the Older Adult: Parameter Estimation and Validation Within a Mobile Phone Task (2007 / PMC) — https://pmc.ncbi.nlm.nih.gov/articles/PMC4591021/
- Human Processor Model overview (discovery/reference pointer) — https://en.wikipedia.org/wiki/Human_processor_model
License
MIT
// HOW IT'S BUILT
// FILES
5 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
skills/android/SKILL.md38 KBd52c79c83b49truncatedupstream ↗
Showing the inlined prefix. The rest is in the upstream file.
--- name: android-design-guidelines description: Material Design 3 and Android platform guidelines. Use when building Android apps with Jetpack Compose or XML layouts, implementing Material You, navigation, or accessibility. Triggers on tasks involving Android UI, Compose components, dynamic color, or Material Design compliance. license: MIT metadata: author: platform-design-skills version: "1.0.0" --- # Android Platform Design Guidelines — Material Design 3 ## 1. Material You & Theming [CRITICAL] ### 1.1 Dynamic Color Enable dynamic color derived from the user's wallpaper. Dynamic color is the default on Android 12+ and should be the primary theming strategy. ```kotlin // Compose: Dynamic color theme @Composable fun AppTheme( darkTheme: Boolean = isSystemInDarkTheme(), dynamicColor: Boolean = true, content: @Composable () -> Unit ) { val colorScheme = when { dynamicColor && Build.VERSION.SDK_INT >= Build.VERSION_CODES.S -> { val context = LocalContext.current if (darkTheme) dynamicDarkColorScheme(context) else dynamicLightColorScheme(context) } darkTheme -> darkColorScheme() else -> lightColorScheme() } MaterialTheme( colorScheme = colorScheme, typography = AppTypography, content = content ) } ``` ```xml <!-- XML: Dynamic color in themes.xml --> <style name="Theme.App" parent="Theme.Material3.DayNight.NoActionBar"> <item name="dynamicColorThemeOverlay">@style/ThemeOverlay.Material3.DynamicColors.DayNight</item> </style> ``` **Rules:** - R1.1: Always provide a fallback static color scheme for devices below Android 12. - R1.2: Never hardcode color hex values in components. Always reference color roles from the theme. - R1.3: Test with at least 3 different wallpapers to verify dynamic color harmony. ### 1.2 Color Roles Material 3 defines a structured set of color roles. Use them semantically, not aesthetically. | Role | Usage | On-Role | |------|-------|---------| | `primary` | Key actions, active states, FAB | `onPrimary` | | `primaryContainer` | Less prominent primary elements | `onPrimaryContainer` | | `secondary` | Supporting UI, filter chips | `onSecondary` | | `secondaryContainer` | Navigation bar active indicator | `onSecondaryContainer` | | `tertiary` | Accent, contrast, complementary | `onTertiary` | | `tertiaryContainer` | Input fields, less prominent accents | `onTertiaryContainer` | | `surface` | Backgrounds, cards, sheets | `onSurface` | | `surfaceVariant` | Decorative elements, dividers | `onSurfaceVariant` | | `error` | Error states, destructive actions | `onError` | | `errorContainer` | Error backgrounds | `onErrorContainer` | | `outline` | Borders, dividers | — | | `outlineVariant` | Subtle borders | — | | `inverseSurface` | Snackbar background | `inverseOnSurface` | ```kotlin // Correct: semantic color roles Text( text = "Error message", color = MaterialTheme.colorScheme.error ) Surface(color = MaterialTheme.colorScheme.errorContainer) { Text(text = "Error detail", color = MaterialTheme.colorScheme.onErrorContainer) } // WRONG: hardcoded colors Text(text = "Error", color = Color(0xFFB00020)) // Anti-pattern ``` **Rules:** - R1.4: Every foreground element must use the matching `on` color role for its background (e.g., `onPrimary` text on `primary` background). - R1.5: Use `surface` and its variants for backgrounds. Never use `primary` or `secondary` as large background areas. - R1.6: Use `tertiary` sparingly for accent and complementary contrast only. ### 1.3 Light and Dark Themes Support both light and dark themes. Respect the system setting by default. ```kotlin // Compose: Detect system theme val darkTheme = isSystemInDarkTheme() ``` **Rules:** - R1.7: Always support both light and dark themes. Never ship light-only. - R1.8: Dark theme surfaces use elevation-based tonal mapping, not pure black (#000000). Use `surface` color roles which handle this automatically. - R1.9: Provide a manual theme override in app settings (System / Light / Dark). ### 1.4 Custom Color Seeds When branding requires custom colors, provide a seed color and generate tonal palettes using Material Theme Builder. ```kotlin // Custom color scheme with brand seed private val BrandLightColorScheme = lightColorScheme( primary = Color(0xFF1B6D2F), onPrimary = Color(0xFFFFFFFF), primaryContainer = Color(0xFFA4F6A8), onPrimaryContainer = Color(0xFF002107), // ... generate full palette from seed ) ``` **Rules:** - R1.10: Generate tonal palettes from seed colors using Material Theme Builder. Never manually pick individual tones. - R1.11: When using custom colors, still support dynamic color as the default and use custom colors as fallback. --- ## 2. Navigation [CRITICAL] ### 2.1 Navigation Bar (Bottom) The primary navigation pattern for phones with 3-5 top-level destinations. ```kotlin // Compose: Navigation Bar NavigationBar { items.forEachIndexed { index, item -> NavigationBarItem( icon = { Icon( imageVector = if (selectedItem == index) item.filledIcon else item.outlinedIcon, contentDescription = item.label ) }, label = { Text(item.label) }, selected = selectedItem == index, onClick = { selectedItem = index } ) } } ``` **Rules:** - R2.1: Use Navigation Bar for 3-5 top-level destinations on compact screens. Never use for fewer than 3 or more than 5. - R2.2: Always show labels on navigation bar items. Icon-only navigation bars are not permitted. - R2.3: Use filled icons for the selected state and outlined icons for unselected states. - R2.4: The active indicator uses `secondaryContainer` color. Do not override this. ### 2.2 Navigation Rail For medium and expanded screens (tablets, foldables, desktop). ```kotlin // Compose: Navigation Rail for larger screens NavigationRail( header = { FloatingActionButton( onClick = { /* primary action */ }, containerColor = MaterialTheme.colorScheme.tertiaryContainer ) { Icon(Icons.Default.Add, contentDescription = "Create") } } ) { items.forEachIndexed { index, item -> NavigationRailItem( icon = { Icon(item.icon, contentDescription = item.label) }, label = { Text(item.label) }, selected = selectedItem == index, onClick = { selectedItem = index } ) } } ``` **Rules:** - R2.5: Use Navigation Rail on medium (600-839dp) and expanded (840dp+) window sizes. Pair it with Navigation Bar on compact. - R2.6: Optionally include a FAB in the rail header for the primary action. - R2.7: Labels are optional on the rail but recommended for clarity. ### 2.3 Navigation Drawer For 5+ destinations or complex navigation hierarchies, typically on expanded screens. ```kotlin // Compose: Permanent Navigation Drawer for large screens PermanentNavigationDrawer( drawerContent = { PermanentDrawerSheet { Text("App Name", modifier = Modifier.padding(16.dp), style = MaterialTheme.typography.titleMedium) HorizontalDivider() items.forEach { item -> NavigationDrawerItem( label = { Text(item.label) }, selected = item == selectedItem, onClick = { selectedItem = item }, icon = { Icon(item.icon, contentDescription = null) } ) } } } ) { Scaffold { /* page content */ } } ``` **Rules:** - R2.8: Use modal drawer on compact screens, permanent drawer on expanded screens. - R2.9: Group drawer items into sections with dividers and section headers. ### 2.4 Predictive Back Gesture Android 13+ supports predictive back with an animation preview. ```kotlin // Compose: Predictive back with BackHandlerskills/android/AGENTS.md1.6 KB54071f60f06cupstream ↗
# Android Design Skill Material Design 3 guidelines and Android platform conventions for Jetpack Compose and XML layouts. ## Structure - `SKILL.md` — Full guideline rules with code examples - `rules/_sections.md` — Indexed section breakdown for quick lookup - `metadata.json` — Version and reference metadata ## Usage Apply these guidelines when: - Building or reviewing Android UI code - Implementing Material You / dynamic color - Designing navigation, layout, or component architecture - Auditing accessibility or platform compliance ## Priority Rules marked **CRITICAL** must never be violated. Rules marked **HIGH** should be followed unless there is a documented reason. Rules marked **MEDIUM** are recommended best practices. ## Never Do - Never hardcode color hex values — always use `MaterialTheme.colorScheme` color roles - Never use `dp` for text sizes — use `sp` so user font scaling applies - Never override `onBackPressed()` — use `BackHandler` (Compose) or `OnBackInvokedCallback` (View-based) for predictive back - Never place touch targets below 48x48dp — accessibility violation - Never request permissions at app launch — request in context with a rationale - Never use pure black (#000000) for dark theme backgrounds — use Material surface roles - Never put icon-only items in the navigation bar — labels are required - Never use a dialog for non-critical information — prefer Snackbar or Bottom Sheet - Never use more than one FAB on a screen — one FAB for the single primary action - Never show full-width content on tablet layouts — use list-detail or max-width containersskills/android/metadata.json614 Ba1b2c9df695fupstream ↗
{ "version": "1.0.0", "organization": "Platform Design Skills", "date": "February 2026", "abstract": "Material Design 3 and Android platform guidelines. 106 rules across 10 categories covering Material You, dynamic color, navigation patterns, Jetpack Compose components, accessibility, adaptive layouts, and Android-specific interactions. Each rule includes Compose and XML examples.", "references": [ "https://m3.material.io", "https://developer.android.com/design", "https://developer.android.com/develop/ui/compose", "https://developer.android.com/guide/topics/ui/accessibility" ] }skills/android/rules/_sections.md9.0 KB2177e7f7aa4aupstream ↗
# Android Design Guidelines — Section Index Quick reference for locating rules by category and ID. ## Section Map | # | Section | Priority | Rules | Topics | |---|---------|----------|-------|--------| | 1 | Material You & Theming | CRITICAL | R1.1–R1.11 | Dynamic color, color roles, light/dark themes, custom seeds, tonal palettes | | 2 | Navigation | CRITICAL | R2.1–R2.14 | Navigation bar, navigation rail, navigation drawer, predictive back, up vs back | | 3 | Layout & Responsive | HIGH | R3.1–R3.10 | Window size classes, Material grid, edge-to-edge, insets, foldable support | | 4 | Typography | HIGH | R4.1–R4.5 | Type scale, sp units, font scaling, line height, custom fonts | | 5 | Components | HIGH | R5.1–R5.19 | FAB, top app bar, bottom sheets, dialogs, snackbars, chips, cards, waiting states | | 6 | Accessibility | CRITICAL | R6.1–R6.13 | TalkBack, contentDescription, touch targets, contrast, focus order, custom canvas views | | 7 | Gestures & Input | MEDIUM | R7.1–R7.7 | System gestures, pull to refresh, swipe to dismiss, long press, ripple | | 8 | Notifications | MEDIUM | R8.1–R8.9 | Channels, importance, messaging style, expandable, foreground service | | 9 | Permissions & Privacy | HIGH | R9.1–R9.8 | Runtime permissions, rationale, photo picker, approximate location | | 10 | System Integration | MEDIUM | R10.1–R10.10 | Widgets (Glance), app shortcuts, deep links, share sheet | ## Rule Index ### 1. Material You & Theming [CRITICAL] - **R1.1** — Provide fallback static color scheme for devices below Android 12 - **R1.2** — Never hardcode color hex values; use theme color roles - **R1.3** — Test with at least 3 wallpapers for dynamic color harmony - **R1.4** — Foreground elements must use matching `on` color role - **R1.5** — Use `surface` variants for backgrounds, not `primary`/`secondary` - **R1.6** — Use `tertiary` sparingly for accent only - **R1.7** — Always support both light and dark themes - **R1.8** — Dark theme uses tonal mapping, not pure black - **R1.9** — Provide manual theme override (System/Light/Dark) - **R1.10** — Generate tonal palettes from seed via Material Theme Builder - **R1.11** — Support dynamic color as default; custom colors as fallback ### 2. Navigation [CRITICAL] - **R2.1** — Navigation Bar for 3-5 destinations on compact screens - **R2.2** — Always show labels on navigation bar items - **R2.3** — Filled icons for selected, outlined for unselected - **R2.4** — Active indicator uses `secondaryContainer` - **R2.5** — Navigation Rail on medium (600dp+) and expanded screens - **R2.6** — Optionally include FAB in rail header - **R2.7** — Rail labels optional but recommended - **R2.8** — Modal drawer on compact, permanent drawer on expanded - **R2.9** — Group drawer items with dividers and section headers - **R2.10** — Opt in to predictive back; use `BackHandler` (Compose) or `OnBackInvokedCallback` (View-based) - **R2.11** — System back != Up button; they may navigate differently - **R2.12** — No "are you sure?" on back unless unsaved user input - **R2.13** — Do not suppress the system predictive back preview animation; interpolate custom transitions using `BackEventCompat.progress` and respect `BackEventCompat.swipeEdge` - **R2.14** — Prefer recognition over recall; keep destinations labeled and visible state preserved ### 3. Layout & Responsive [HIGH] - **R3.1** — Use `WindowSizeClass` for responsive decisions - **R3.2** — Never use fixed pixel breakpoints - **R3.3** — Support all three width size classes - **R3.4** — Max content width ~840dp on expanded screens - **R3.5** — Consistent horizontal margins per grid spec - **R3.6** — Call `enableEdgeToEdge()` before `setContent` - **R3.7** — Use `WindowInsets` to pad content from system bars - **R3.8** — Scrollable content scrolls behind transparent system bars - **R3.9** — Detect fold/hinge; avoid content across fold - **R3.10** — Use `ListDetailPaneScaffold` for foldable-aware layouts ### 4. Typography [HIGH] - **R4.1** — Use `sp` units for all text sizes - **R4.2** — Minimum 12sp body text, 11sp labels - **R4.3** — Reference `MaterialTheme.typography` roles, not hardcoded sizes - **R4.4** — Test at 200% font scale; no clipping - **R4.5** — Line height 1.2-1.5x font size ### 5. Components [HIGH] - **R5.1** — At most one FAB per screen - **R5.2** — FAB at bottom-end, above Navigation Bar - **R5.3** — FAB uses `primaryContainer` by default - **R5.4** — Prefer `ExtendedFloatingActionButton` with label - **R5.5** — Small top app bar for most screens; medium/large for prominent titles - **R5.6** — Connect scroll behavior to top app bar - **R5.7** — Limit action icons to 2-3; overflow the rest - **R5.8** — Modal bottom sheets for supplementary; standard for persistent - **R5.9** — Bottom sheets must have visible drag handle - **R5.10** — Sheet content must be scrollable if it overflows - **R5.11** — Dialogs for critical decisions only - **R5.12** — Confirm button is text button; dismiss on left - **R5.13** — Dialog titles are concise questions or statements - **R5.14** — Snackbars for brief non-critical feedback - **R5.15** — Snackbars above Navigation Bar, below FAB - **R5.16** — Include undo action when operation is reversible - **R5.17** — Correct chip type for use case (Filter/Assist/Input/Suggestion) - **R5.18** — Chips in horizontal scroll or flow layout, not stacked vertically - **R5.19** — Expose waiting states immediately; acknowledge long-running work with visible progress ### 6. Accessibility [CRITICAL] - **R6.1** — Every interactive element needs `contentDescription` - **R6.2** — Describe action/meaning, not visual appearance - **R6.3** — `mergeDescendants` for grouped related elements - **R6.4** — Provide `customActions` for swipe/long-press actions - **R6.5** — Minimum 48x48dp touch targets - **R6.6** — Do not reduce touch targets to save space - **R6.7** — Text contrast >= 4.5:1 normal, >= 3:1 large - **R6.8** — Never use color alone to convey information - **R6.9** — Support bold text and high contrast settings - **R6.10** — Logical focus order (top-to-bottom, start-to-end) - **R6.11** — Move focus to logical target after navigation/dialog dismissal - **R6.12** — Full operability via TalkBack, Switch Access, keyboard - **R6.13** — Custom canvas views must use ExploreByTouchHelper for a virtual accessibility tree ### 7. Gestures & Input [MEDIUM] - **R7.1** — No interactive elements in system gesture zones - **R7.2** — Use `WindowInsets.systemGestures` to detect conflict zones - **R7.3** — Swipe-to-dismiss must be undoable or confirmed - **R7.4** — Non-gesture alternatives for all gesture actions - **R7.5** — Material ripple on all tappable elements - **R7.6** — Long press for context menus; never the only access path - **R7.7** — Haptic feedback on long press ### 8. Notifications [MEDIUM] - **R8.1** — Separate channels for each notification type - **R8.2** — Choose importance levels conservatively - **R8.3** — All notifications must have a tap action - **R8.4** — Notification icons need `contentDescription` - **R8.5** — `MessagingStyle` for conversations - **R8.6** — Direct reply actions on message notifications - **R8.7** — "Mark as read" action on message notifications - **R8.8** — Use expandable styles for rich content - **R8.9** — Foreground service notifications describe operation + stop action ### 9. Permissions & Privacy [HIGH] - **R9.1** — Request permissions in context, not at launch - **R9.2** — Show rationale before requesting - **R9.3** — Graceful degradation on denial - **R9.4** — Never request unnecessary permissions - **R9.5** — Use Photo Picker instead of `READ_MEDIA_IMAGES` - **R9.6** — Prefer `ACCESS_COARSE_LOCATION` unless precise is essential - **R9.7** — One-time permissions for camera/mic in non-recording contexts - **R9.8** — Privacy indicator when camera/mic actively in use ### 10. System Integration [MEDIUM] - **R10.1** — Glance API for widgets with dynamic color - **R10.2** — Widgets must work immediately after placement - **R10.3** — Multiple widget sizes where practical - **R10.4** — Rounded corners matching system widget shape - **R10.5** — 2-4 static shortcuts; support dynamic shortcuts - **R10.6** — Shortcut icons: simple silhouettes on circular background - **R10.7** — Test shortcuts via long-press and Settings - **R10.8** — Android App Links for public content URLs - **R10.9** — Share sheet with rich previews - **R10.10** — Handle incoming share intents with content type filtering ## Cross-References | Topic | Primary Section | Also See | |-------|----------------|----------| | Dark theme | 1.3 | 6.3 (contrast) | | Touch targets | 6.2 | 7.1 (gesture zones) | | System bars | 3.3 | 7.1 (gesture insets) | | FAB placement | 5.1 | 2.2 (rail header), 5.15 (snackbar) | | Font scaling | 4.1 | R4.4 (200% scale test), R6.9 (bold text) | | Permissions | 9.1 | 9.5 (photo picker) | | Navigation sizing | 2.5 (table) | 3.1 (window size classes) | | Color roles | 1.2 | R2.4 (nav indicator active color), R5.3 (FAB color) |README.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/ehmo-platform-design-skills-skills-android.md