[{"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",1554,"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",468,"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-11 02:22:54",{"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,104,129,161,182,196],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":50},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[87,88,89,90,91,92,93,94,95,30,96,32,36,97,98,99,100,101,102,103],"search","deja search","error","ready","never","memory","re","decide","fix","debugging","done","reviewer","io","change","cli","merge","past",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":50},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[111,112,113,114,92,115,116,117,118,119,120,121,122,99,123,124,125,126,127,128],"reflect","deja reflect","brew","remember","project rules","project","session","end","reflection","Rules","decisions","review","with","record","github","next","https","node",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":144,"publishedAt":50},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[135,138,141],{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":139,"categoryName":140,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":142,"categoryName":143,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[131,145,146,147,148,149,116,150,93,151,152,153,154,32,155,156,157,158,159,160],"Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","URL","image","mcp server","schedule","api","publish",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":50},"01M71569ZM2X3H5RBFK8PVKMK2","review-study","Review a QuestionPunk survey before launch for wording, answer choices, branching, and missing settings. Use for check my survey or review this draft before publishing.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fquestionpunk\u002Fcodex-plugin\u002Fskills\u002Freview-study\u002FSKILL.md",[],[168,169,122,170,171,172,173,174,175,176,177,178,179,180,181],"study","review study","for","answer","missing","survey","publishing","use","check","draft","settings","launch","my","branching",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":50},"01M71567GV0C35YQBY0DPGR86B","manage-study","Find QuestionPunk studies, check status, publish an explicitly requested draft, or retrieve its participant link. Use for find my survey, publish this study, or how many people responded.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fquestionpunk\u002Fcodex-plugin\u002Fskills\u002Fmanage-study\u002FSKILL.md",[],[189,168,190,170,173,175,191,176,177,160,192,193,194,195,180],"manage study","manage","people","how","find","link","status",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"publishedAt":50},"01M71565A8TCA01AZQZRGRYMFZ","create-study","Create a saved QuestionPunk survey draft from a research brief or edit specified questions. Use for requests such as make a customer feedback survey or shorten my onboarding study.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fquestionpunk\u002Fcodex-plugin\u002Fskills\u002Fcreate-study\u002FSKILL.md",[],[203,168,204,205,206,207,170,208,173,209,175,210,211,177,212,213,214,215,216,180],"create study","create","brief","as","feedback","customer feedback","research brief","shorten","saved","research","requests","customer","questions","edit"]