[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MGC70XMST1NWK7TYMBZ7ZX":3,"skill-same:01M6MGC70XMST1NWK7TYMBZ7ZX":79},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6MGC70XMST1NWK7TYMBZ7ZX","android-design",null,"Use when the user asks for an Android app, Compose UI, Material 3, Material You, Material 3 Expressive, Pixel-style app, foldable\u002Fadaptive layout, Play Store deliverable, React Native Android, Flutter Android, Compose Multiplatform, or any Android deliverable. Builds Android apps across system-like Compose, branded Compose, React Native, Flutter, and Compose Multiplatform while preserving UX decisions, state coverage, adaptive navigation, Material motion, accessibility, and product-specific visual direction. ALWAYS ask which track first. SKIP when the target is only iOS, Windows, or web-in-browser.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ff0d010c\u002Fstark\u002Fskills\u002Fandroid-design\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"android","design","android design","when","track","which","ux decisions","you","native","direction","apps","app","material 3","across","pixel","only","react native","coverage","ask","browser","react","2026-11-10 10:12:30",false,"---\nname: android-design\ndescription: Use when the user asks for an Android app, Compose UI, Material 3, Material You, Material 3 Expressive, Pixel-style app, foldable\u002Fadaptive layout, Play Store deliverable, React Native Android, Flutter Android, Compose Multiplatform, or any Android deliverable. Builds Android apps across system-like Compose, branded Compose, React Native, Flutter, and Compose Multiplatform while preserving UX decisions, state coverage, adaptive navigation, Material motion, accessibility, and product-specific visual direction. ALWAYS ask which track first. SKIP when the target is only iOS, Windows, or web-in-browser.\n---\n\n# android-design — pick the track first\n\nAndroid has multiple stacks with different visual ceilings. **Ask the user which one before any code.**\n\n## What This Skill Can Do\n\n- Choose the right Android track: strict Compose\u002FMaterial, branded Compose, React Native, Flutter, or Compose Multiplatform.\n- Design mobile task flows, onboarding, forms, settings, dashboards, media\u002Fproduct surfaces, foldables, tablets, and adaptive layouts.\n- Preserve UX briefs, state coverage, navigation hierarchy, gesture\u002Fback behavior, loading\u002Ferror\u002Fpermission states, and accessibility.\n- Apply Material 3 Expressive, dynamic color, edge-to-edge, predictive back, motion schemes, shape, typography, and responsive window-size classes.\n- Add branded originality through content surfaces, composition, typography, and state treatment without breaking Android idioms.\n\n## Step 0 (MANDATORY) — Ask the user which track\n\n> Which track for this app?\n>\n> **1. System-like native (Jetpack Compose + Material 3 Expressive strict)** — feels like Pixel Launcher, Google Calendar, Settings. Best for: utilities, system tools, productivity. Spring physics, shape morphing, wavy progress, dynamic color (Material You). Examples: Read You, Androidify sample, Files by Google.\n>\n> **2. Branded native (Compose + custom Material theme)** — native chrome (M3E motion, predictive back, edge-to-edge) but bespoke content surface (custom typography, hero atmospheres, magazine layouts). Visual ceiling: high. Examples: Fitbit redesign, Google Calendar's editorial moments, Niantic apps.\n>\n> **3. React Native (New Architecture + Fabric + Hermes)** — real Android views, decent native feel, JavaScript codebase, cross-platform with iOS. Material themable but won't get spring physics or shape morphing without manual work. Examples: Discord mobile, Coinbase, Microsoft Office.\n>\n> **4. Flutter** — Skia-painted custom rendering. Cross-platform single codebase. Lags Material updates (no M3 Expressive parity, no real dynamic color). Visual ceiling: high if you ship your own design language; weak if mimicking Material. Examples: Google Pay, BMW My BMW, Toyota.\n>\n> **5. Compose Multiplatform (1.8+)** — same Compose code, runs Android + iOS + Desktop + Web (Wasm experimental). Native on Android, Material-look on iOS (you must Cupertino-skin or accept). Best for: Kotlin shop wanting cross-platform from one codebase.\n>\n> Which? Or describe priorities (Play Store launch, cross-platform reach, brand vs Material fit) and I'll pick.\n\nIf brief gives strong signal (e.g. \"Pixel-style camera\" → 1; \"cross-platform with React team\" → 3; \"Kotlin shop, ship to all platforms\" → 5), state your pick + reasoning in one sentence. If ambiguous, ask.\n\n## Step 0b — Once picked, route\n\n| Track | Reference docs | Default stack |\n|---|---|---|\n| 1. System-like Compose | `..\u002F..\u002Freferences\u002Fmaterial3-expressive.md` | Compose BOM 2026.06.00 + Material3 1.4 + adaptive layouts strict |\n| 2. Branded Compose | Same as 1 | Same as 1 + custom display font + hero atmospheres + bespoke surfaces |\n| 3. React Native | `..\u002F..\u002Freferences\u002Fweb-fonts.md` + cross-platform docs | RN 0.86 New Architecture + Expo Router |\n| 4. Flutter | None for native fidelity | Flutter 3+ stable |\n| 5. Compose Multiplatform | `..\u002F..\u002Freferences\u002Fmaterial3-expressive.md` | Current stable CMP + shared Compose |\n\nFor tracks 3 and 4: web\u002Fcross-platform anti-slop rules apply. Read web references.\n\nState the chosen aesthetic direction and track in one sentence at top of response.\n\n## Step 0c — UI decision brief\n\nBefore code, read:\n\n- `..\u002F..\u002Freferences\u002Fui-patterns\u002Fsurface-taxonomy.md`\n- `..\u002F..\u002Freferences\u002Fui-patterns\u002Fui-decision-brief.md`\n- `..\u002F..\u002Freferences\u002Fui-patterns\u002Fvisual-hierarchy.md`\n- `..\u002F..\u002Freferences\u002Fui-patterns\u002Fmotion-budget.md`\n\nWrite the UI decision brief and adapt it to the chosen Android track. Compact screens need thumb-reachable primary actions, sheets, edge-to-edge, and adaptive navigation; tablets\u002Ffoldables need list-detail or supporting panes; operational tools should stay dense and scannable while preserving Material 3 Expressive motion, dynamic color, and predictive back.\n\n## Step 1 — Material 3 Expressive default (only if track 1 or 2)\n\nLaunched at I\u002FO 2025. Default for Pixel 10 \u002F Android 16 QPR1. Generated UI must adopt:\n\n- **Spring physics on every motion** — `MotionScheme.expressive()`. Never `FastOutSlowIn` on M3E surfaces.\n- **Shape morphing** — 35 new shapes (squircle, pill, cookie, clover). Use `MaterialShapes.Cookie4Sided`, `Pill`, etc. Buttons\u002Fchips\u002Floaders morph between states.\n- **Emphasized typography** — bigger, heavier headlines. Use `MaterialTheme.typography.displayLarge` with intent.\n- **New components**:\n  - `FloatingToolbar` (pill-shaped, drifts with content)\n  - `ButtonGroup` \u002F `SplitButton`\n  - `FloatingActionButtonMenu`\n  - `ContainedLoadingIndicator` (cycles through M3E shapes)\n  - **Wavy progress** — `LinearWavyProgressIndicator`, `CircularWavyProgressIndicator` with variable amplitude\n  - Large\u002FSmall\u002FXL button sizes\n- **Tonal elevation** — surface tone shifts, never `Modifier.shadow()` for elevation\n- **Dynamic color (Material You)** — `dynamicColorScheme()` from wallpaper on Android 12+\n\nRead `..\u002F..\u002Freferences\u002Fmaterial3-expressive.md` for the M3E adoption checklist.\n\n## Step 2 — Compose currency (BOM 2026.04.01)\n\n```kotlin\nimplementation(platform(\"androidx.compose:compose-bom:2026.04.01\"))\nimplementation(\"androidx.compose.material3:material3:1.4.0\")\n\u002F\u002F or for shape-morphing chips:\nimplementation(\"androidx.compose.material3:material3:1.5.0-alpha18\")\n```\n\nUse:\n- `currentWindowAdaptiveInfo()` + `NavigationSuiteScaffold` (auto-swaps Bar\u002FRail\u002FDrawer by WindowSizeClass)\n- `ListDetailPaneScaffold`, `SupportingPaneScaffold`, `NavigableListDetailPaneScaffold`\n- `SharedTransitionLayout { ... }` for shared element transitions (stable)\n- `PredictiveBackHandler` \u002F `BackHandler` — **mandatory** on Android 16, default ON Android 15+\n- `LookaheadAnimationVisualDebugging` for inspecting bounds during dev\n\n## Step 3 — Edge-to-edge is mandatory\n\nAndroid 16 (API 36) deprecated `windowOptOutEdgeToEdgeEnforcement`. Every screen:\n- Wraps in `Scaffold` with content padding from insets\n- Uses `WindowInsets.systemBars`, `.statusBars`, `.navigationBars`\n- Predictive back must be wired\n- Status bar color cannot be set opaque — banned on Android 16\n\n## Step 4 — Adaptive layouts\n\n- **Compact** (phone portrait) → `NavigationBar` (3–5 items)\n- **Medium** (foldable inner \u002F tablet portrait) → `NavigationRail`\n- **Expanded** (tablet landscape \u002F desktop) → `NavigationDrawer` (modal or permanent) + `ListDetailPaneScaffold`\n- **Foldables**: handle tabletop \u002F book postures via `WindowInfoTracker`\n\n## Step 5 — Typography & icons\n\n- **Default body**: Roboto Flex (variable). Headlines: per-app brand expression — but stay within M3E weight\u002Fsize scale.\n- **Material Symbols** (variable axes: weight, fill, grade, optical size) — never FontAwesome\u002FLucide.\n- Get Material Symbols from https:\u002F\u002Ffonts.google.com\u002Ficons\n\n## Step 6 — Anti-slop ban list (Android-specific)\n\n- iOS-style top nav bars \u002F chevron-back headers\n- Hamburger drawer when `NavigationBar` (3–5 items) or `NavigationRail` fits\n- Hard `Modifier.shadow(elevation = 8.dp)` — use `tonalElevation` on `Surface` instead\n- Custom back stacks ignoring system back \u002F predictive animation\n- Opaque colored status bars — banned on Android 16\n- Bottom sheets without drag handle \u002F non-draggable\n- Static easing curves on M3E surfaces — `MotionScheme.expressive()` only\n- SF Symbols \u002F Material Symbols-Outlined-only (use variable axes)\n- Inter \u002F SF Pro on Android — Roboto Flex \u002F Google Sans \u002F Material default\n- Centered FAB layouts where docked FAB pattern is canonical\n- Standard Material 3 baseline 2023 — must be M3 Expressive\n- Web-style desktop dashboards squeezed into mobile Compose\n- Decorative motion that hides progress, state, or navigation changes\n\n## Step 7 — Reference apps that nail M3 Expressive\n\n- **Pixel Launcher \u002F Android 16 System UI** — shape morph + springs\n- **Google Calendar** — floating toolbar + tonal surfaces\n- **Fitbit (2025 redesign)** — `ContainedLoadingIndicator` cycling shapes; floating toolbar\n- **Pixel Camera 10.1** — wavy progress in capture\n- **Google Docs\u002FSheets\u002FSlides homepages** — M3E typography\n- **Chrome (M3E redesign)** — adaptive nav\n- **Read You** (community RSS, OSS) — canonical M3 + dynamic color\n- **Androidify** sample app — official Compose M3E reference\n\n## Step 8 — Architecture defaults\n\n- **MVVM** with `ViewModel` + `StateFlow` + `collectAsStateWithLifecycle()`\n- **Hilt** for DI\n- **Navigation Compose 3** with type-safe routes\n- **Coil 3** for image loading (replaces Glide for Compose-first apps)\n- **Ktor** or **Retrofit + KotlinX Serialization** for networking\n- **Room** for local persistence\n\n## Step 9 — Tokens & assets\n\n- M3 token spec: https:\u002F\u002Fm3.material.io\u002Ffoundations\u002Fdesign-tokens\u002Fhow-to-use-tokens\n- Theme Builder (web): https:\u002F\u002Fm3.material.io\u002Ftheme-builder\n- Theme Builder Figma plugin: https:\u002F\u002Fwww.figma.com\u002Fcommunity\u002Fplugin\u002F1034969338659738588\n- M3 Figma kit: https:\u002F\u002Fwww.figma.com\u002Fcommunity\u002Ffile\u002F1035203688168086460\n- Material Symbols: https:\u002F\u002Ffonts.google.com\u002Ficons\n- M3E component catalog: https:\u002F\u002Fgithub.com\u002Fmeticha\u002Fmaterial-3-expressive-catalog\n\nToken JSON: see `..\u002F..\u002Fassets\u002Ftokens\u002Fmaterial3-expressive.json`\n","# android-design — pick the track first\n\nAndroid has multiple stacks with different visual ceilings. **Ask the user which one before any code.**\n\n## What This Skill Can Do\n\n- Choose the right Android track: strict Compose\u002FMaterial, branded Compose, React Native, Flutter, or Compose Multiplatform.\n- Design mobile task flows, onboarding, forms, settings, dashboards, media\u002Fproduct surfaces, foldables, tablets, and adaptive layouts.\n- Preserve UX briefs, state coverage, navigation hierarchy, gesture\u002Fback behavior, loading\u002Ferror\u002Fpermission states, and accessibility.\n- Apply Material 3 Expressive, dynamic color, edge-to-edge, predictive back, motion schemes, shape, typography, and responsive window-size classes.\n- Add branded originality through content surfaces, composition, typography, and state treatment without breaking Android idioms.\n\n## Step 0 (MANDATORY) — Ask the user which track\n\n> Which track for this app?\n>\n> **1. System-like native (Jetpack Compose + Material 3 Expressive strict)** — feels like Pixel Launcher, Google Calendar, Settings. Best for: utilities, system tools, productivity. Spring physics, shape morphing, wavy progress, dynamic color (Material You). Examples: Read You, Androidify sample, Files by Google.\n>\n> **2. Branded native (Compose + custom Material theme)** — native chrome (M3E motion, predictive back, edge-to-edge) but bespoke content surface (custom typography, hero atmospheres, magazine layouts). Visual ceiling: high. Examples: Fitbit redesign, Google Calendar's editorial moments, Niantic apps.\n>\n> **3. React Native (New Architecture + Fabric + Hermes)** — real Android views, decent native feel, JavaScript codebase, cross-platform with iOS. Material themable but won't get spring physics or shape morphing without manual work. Examples: Discord mobile, Coinbase, Microsoft Office.\n>\n> **4. Flutter** — Skia-painted custom rendering. Cross-platform single codebase. Lags Material updates (no M3 Expressive parity, no real dynamic color). Visual ceiling: high if you ship your own design language; weak if mimicking Material. Examples: Google Pay, BMW My BMW, Toyota.\n>\n> **5. Compose Multiplatform (1.8+)** — same Compose code, runs Android + iOS + Desktop + Web (Wasm experimental). Native on Android, Material-look on iOS (you must Cupertino-skin or accept). Best for: Kotlin shop wanting cross-platform from one codebase.\n>\n> Which? Or describe priorities (Play Store launch, cross-platform reach, brand vs Material fit) and I'll pick.\n\nIf brief gives strong signal (e.g. \"Pixel-style camera\" → 1; \"cross-platform with React team\" → 3; \"Kotlin shop, ship to all platforms\" → 5), state your pick + reasoning in one sentence. If ambiguous, ask.\n\n## Step 0b — Once picked, route\n\n| Track | Reference docs | Default stack |\n|---|---|---|\n| 1. System-like Compose | `..\u002F..\u002Freferences\u002Fmaterial3-expressive.md` | Compose BOM 2026.06.00 + Material3 1.4 + adaptive layouts strict |\n| 2. Branded Compose | Same as 1 | Same as 1 + custom display font + hero atmospheres + bespoke surfaces |\n| 3. React Native | `..\u002F..\u002Freferences\u002Fweb-fonts.md` + cross-platform docs | RN 0.86 New Architecture + Expo Router |\n| 4. Flutter | None for native fidelity | Flutter 3+ stable |\n| 5. Compose Multiplatform | `..\u002F..\u002Freferences\u002Fmaterial3-expressive.md` | Current stable CMP + shared Compose |\n\nFor tracks 3 and 4: web\u002Fcross-platform anti-slop rules apply. Read web references.\n\nState the chosen aesthetic direction and track in one sentence at top of response.\n\n## Step 0c — UI decision brief\n\nBefore code, read:\n\n- `..\u002F..\u002Freferences\u002Fui-patterns\u002Fsurface-taxonomy.md`\n- `..\u002F..\u002Freferences\u002Fui-patterns\u002Fui-decision-brief.md`\n- `..\u002F..\u002Freferences\u002Fui-patterns\u002Fvisual-hierarchy.md`\n- `..\u002F..\u002Freferences\u002Fui-patterns\u002Fmotion-budget.md`\n\nWrite the UI decision brief and adapt it to the chosen Android track. Compact screens need thumb-reachable primary actions, sheets, edge-to-edge, and adaptive navigation; tablets\u002Ffoldables need list-detail or supporting panes; operational tools should stay dense and scannable while preserving Material 3 Expressive motion, dynamic color, and predictive back.\n\n## Step 1 — Material 3 Expressive default (only if track 1 or 2)\n\nLaunched at I\u002FO 2025. Default for Pixel 10 \u002F Android 16 QPR1. Generated UI must adopt:\n\n- **Spring physics on every motion** — `MotionScheme.expressive()`. Never `FastOutSlowIn` on M3E surfaces.\n- **Shape morphing** — 35 new shapes (squircle, pill, cookie, clover). Use `MaterialShapes.Cookie4Sided`, `Pill`, etc. Buttons\u002Fchips\u002Floaders morph between states.\n- **Emphasized typography** — bigger, heavier headlines. Use `MaterialTheme.typography.displayLarge` with intent.\n- **New components**:\n  - `FloatingToolbar` (pill-shaped, drifts with content)\n  - `ButtonGroup` \u002F `SplitButton`\n  - `FloatingActionButtonMenu`\n  - `ContainedLoadingIndicator` (cycles through M3E shapes)\n  - **Wavy progress** — `LinearWavyProgressIndicator`, `CircularWavyProgressIndicator` with variable amplitude\n  - Large\u002FSmall\u002FXL button sizes\n- **Tonal elevation** — surface tone shifts, never `Modifier.shadow()` for elevation\n- **Dynamic color (Material You)** — `dynamicColorScheme()` from wallpaper on Android 12+\n\nRead `..\u002F..\u002Freferences\u002Fmaterial3-expressive.md` for the M3E adoption checklist.\n\n## Step 2 — Compose currency (BOM 2026.04.01)\n\n```kotlin\nimplementation(platform(\"androidx.compose:compose-bom:2026.04.01\"))\nimplementation(\"androidx.compose.material3:material3:1.4.0\")\n\u002F\u002F or for shape-morphing chips:\nimplementation(\"androidx.compose.material3:material3:1.5.0-alpha18\")\n```\n\nUse:\n- `currentWindowAdaptiveInfo()` + `NavigationSuiteScaffold` (auto-swaps Bar\u002FRail\u002FDrawer by WindowSizeClass)\n- `ListDetailPaneScaffold`, `SupportingPaneScaffold`, `NavigableListDetailPaneScaffold`\n- `SharedTransitionLayout { ... }` for shared element transitions (stable)\n- `PredictiveBackHandler` \u002F `BackHandler` — **mandatory** on Android 16, default ON Android 15+\n- `LookaheadAnimationVisualDebugging` for inspecting bounds during dev\n\n## Step 3 — Edge-to-edge is mandatory\n\nAndroid 16 (API 36) deprecated `windowOptOutEdgeToEdgeEnforcement`. Every screen:\n- Wraps in `Scaffold` with content padding from insets\n- Uses `WindowInsets.systemBars`, `.statusBars`, `.navigationBars`\n- Predictive back must be wired\n- Status bar color cannot be set opaque — banned on Android 16\n\n## Step 4 — Adaptive layouts\n\n- **Compact** (phone portrait) → `NavigationBar` (3–5 items)\n- **Medium** (foldable inner \u002F tablet portrait) → `NavigationRail`\n- **Expanded** (tablet landscape \u002F desktop) → `NavigationDrawer` (modal or permanent) + `ListDetailPaneScaffold`\n- **Foldables**: handle tabletop \u002F book postures via `WindowInfoTracker`\n\n## Step 5 — Typography & icons\n\n- **Default body**: Roboto Flex (variable). Headlines: per-app brand expression — but stay within M3E weight\u002Fsize scale.\n- **Material Symbols** (variable axes: weight, fill, grade, optical size) — never FontAwesome\u002FLucide.\n- Get Material Symbols from https:\u002F\u002Ffonts.google.com\u002Ficons\n\n## Step 6 — Anti-slop ban list (Android-specific)\n\n- iOS-style top nav bars \u002F chevron-back headers\n- Hamburger drawer when `NavigationBar` (3–5 items) or `NavigationRail` fits\n- Hard `Modifier.shadow(elevation = 8.dp)` — use `tonalElevation` on `Surface` instead\n- Custom back stacks ignoring system back \u002F predictive animation\n- Opaque colored status bars — banned on Android 16\n- Bottom sheets without drag handle \u002F non-draggable\n- Static easing curves on M3E surfaces — `MotionScheme.expressive()` only\n- SF Symbols \u002F Material Symbols-Outlined-only (use variable axes)\n- Inter \u002F SF Pro on Android — Roboto Flex \u002F Google Sans \u002F Material default\n- Centered FAB layouts where docked FAB pattern is canonical\n- Standard Material 3 baseline 2023 — must be M3 Expressive\n- Web-style desktop dashboards squeezed into mobile Compose\n- Decorative motion that hides progress, state, or navigation changes\n\n## Step 7 — Reference apps that nail M3 Expressive\n\n- **Pixel Launcher \u002F Android 16 System UI** — shape morph + springs\n- **Google Calendar** — floating toolbar + tonal surfaces\n- **Fitbit (2025 redesign)** — `ContainedLoadingIndicator` cycling shapes; floating toolbar\n- **Pixel Camera 10.1** — wavy progress in capture\n- **Google Docs\u002FSheets\u002FSlides homepages** — M3E typography\n- **Chrome (M3E redesign)** — adaptive nav\n- **Read You** (community RSS, OSS) — canonical M3 + dynamic color\n- **Androidify** sample app — official Compose M3E reference\n\n## Step 8 — Architecture defaults\n\n- **MVVM** with `ViewModel` + `StateFlow` + `collectAsStateWithLifecycle()`\n- **Hilt** for DI\n- **Navigation Compose 3** with type-safe routes\n- **Coil 3** for image loading (replaces Glide for Compose-first apps)\n- **Ktor** or **Retrofit + KotlinX Serialization** for networking\n- **Room** for local persistence\n\n## Step 9 — Tokens & assets\n\n- M3 token spec: https:\u002F\u002Fm3.material.io\u002Ffoundations\u002Fdesign-tokens\u002Fhow-to-use-tokens\n- Theme Builder (web): https:\u002F\u002Fm3.material.io\u002Ftheme-builder\n- Theme Builder Figma plugin: https:\u002F\u002Fwww.figma.com\u002Fcommunity\u002Fplugin\u002F1034969338659738588\n- M3 Figma kit: https:\u002F\u002Fwww.figma.com\u002Fcommunity\u002Ffile\u002F1035203688168086460\n- Material Symbols: https:\u002F\u002Ffonts.google.com\u002Ficons\n- M3E component catalog: https:\u002F\u002Fgithub.com\u002Fmeticha\u002Fmaterial-3-expressive-catalog\n\nToken JSON: see `..\u002F..\u002Fassets\u002Ftokens\u002Fmaterial3-expressive.json`\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Ff0d010c\u002Fstark\u002Fskills\u002Fandroid-design",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill android-design",{"tool":71,"command":72},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill android-design",{"tool":74,"command":75},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill android-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ff0d010c\u002Fstark\u002Fskills\u002Fandroid-design\u002FSKILL.md",true,[],[80,90,98,106,114,122],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":89},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":89},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":89},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":89},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":89},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":89},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]