[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D5ABYRS59CE3SVC8DHC35F":3,"skill-same:01M7D5ABYRS59CE3SVC8DHC35F":172},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7D5ABYRS59CE3SVC8DHC35F","material-design-3-ui",null,"Design, redesign, review, or implement user interfaces using Google Material Design 3 (M3), Material You, and optional Material 3 Expressive principles. Use for UI\u002FUX screens, app flows, design systems, component selection, theming, responsive\u002Fadaptive layouts, accessibility audits, Figma-ready specifications, or developer handoff where Material Design 3 is required.","Darshan8610\u002FDynamic-Island","Darshan8610","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F280662176?v=4","01M7D3NS7B63B86XTVEHZWQRM2","01M7D3NS8HT3SPCDXKS1VFAB0X",0,"MIT","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: Design, redesign, review, or implement user interfaces using Google Material Design 3 (M3), Material You, and optional Material 3 Expressive principles. Use for UI\u002FUX screens, app flows, design systems, component selection, theming, responsive\u002Fadaptive layouts, accessibility audits, Figma-ready specifications, or developer handoff where Material Design 3 is required.\nmetadata:\n  updated: 2026-10-01\n  version: 1.1.1\nname: material-design-3-ui\n---\n\n# Material Design 3 UI\u002FUX\n\n## Purpose\n\nCreate interfaces that **behave like Material Design 3**, not interfaces that merely look rounded or “Google-like.”\n\nTreat M3 as a system:\n\n**user goal → information architecture → hierarchy → adaptive layout → semantic tokens → components → states → interaction → motion → accessibility → visual expression**\n\nM3 Expressive is optional. Use it to strengthen hierarchy, usability, recognition, and emotional clarity; never use it as permission to make every element loud.\n\n## Source of truth\n\n1.  Prefer current official Material 3 guidance at `https:\u002F\u002Fm3.material.io\u002F`.\n2.  For Android implementation details, prefer `https:\u002F\u002Fdeveloper.android.com\u002F`.\n3.  Treat design guidance separately from implementation-library\u002FAPI status.\n4.  Verify current official guidance before asserting exact dimensions, dependency versions, experimental API names, or recently changed behavior.\n5.  Do not silently mix Material 2 rules into Material 3.\n6.  Pixel and Google-app screenshots are examples, not the specification.\n\n## Core rules\n\n### MUST\n\n- Start from the user’s task, content, hierarchy, and platform before styling.\n- Use semantic design tokens instead of scattered one-off values.\n- Choose components by purpose and behavior, not visual resemblance.\n- Prefer established M3\u002Fplatform components when they solve the interaction.\n- Define important states: default, pressed, focus, hover where applicable, selected, disabled, loading, error, empty, and success where relevant.\n- Design for the available window rather than a guessed device category.\n- Preserve accessible contrast, target size, focus, semantics, scaling, and non-color state communication.\n- Respect system bars, safe areas, cutouts, keyboards\u002FIME, foldable hinges, and edge-to-edge behavior where applicable.\n- Keep primary actions distinguishable from secondary and destructive actions.\n- Make custom components inherit the token, state, motion, and accessibility logic of the system.\n- Explain deliberate departures from M3 when product requirements justify them.\n\n### MUST NOT\n\n- Do not “Materialize” a screen by only adding large radii, pastel colors, shadows, or Material Symbols.\n- Do not hardcode raw colors throughout screens when semantic roles can be used.\n- Do not use color alone to communicate meaning or state.\n- Do not wrap every section or list row in a card.\n- Do not maximize corner radius on every component.\n- Do not use FABs for minor, destructive, or ambiguous actions.\n- Do not use chips as generic buttons or primary navigation.\n- Do not use tabs for unrelated top-level destinations.\n- Do not make all components equally expressive.\n- Do not invent a new control when an established M3\u002Fplatform control already solves the interaction.\n- Do not sacrifice accessibility to preserve a visual composition.\n- Do not stretch a compact\u002Fmobile layout unchanged across wide windows.\n\n## Progressive-disclosure references\n\nLoad only the references needed for the current task. Do not read every reference by default.\n\n| Need                                                    | Read                                  |\n|---------------------------------------------------------|---------------------------------------|\n| Color roles, surfaces, dark theme, dynamic color        | `references\u002Fcolor-system.md`          |\n| Type hierarchy, scaling, expressive typography          | `references\u002Ftypography.md`            |\n| Shape, cards, containment, elevation                    | `references\u002Fshape-and-elevation.md`   |\n| Spacing, alignment, readable widths, safe areas         | `references\u002Fspacing-and-layout.md`    |\n| Buttons, FAB, cards, chips, selection, inputs, feedback | `references\u002Fcomponent-selection.md`   |\n| Navigation bar\u002Frail\u002Fdrawer, tabs, app bars              | `references\u002Fnavigation.md`            |\n| Forms, validation, settings, text input                 | `references\u002Fforms-and-input.md`       |\n| Snackbar, dialog, sheet, loading, empty\u002Ferror states    | `references\u002Ffeedback-and-overlays.md` |\n| Responsive, tablet, foldable, desktop, multi-pane       | `references\u002Fadaptive-design.md`       |\n| Accessibility audit or any final UI review              | `references\u002Faccessibility.md`         |\n| Transitions, feedback animation, shape morphing         | `references\u002Fmotion.md`                |\n| Material 3 Expressive                                   | `references\u002Fm3-expressive.md`         |\n| Final audit \u002F suspicious “Material-looking” UI          | `references\u002Fanti-patterns.md`         |\n\nFor a broad end-to-end design, load the references incrementally as decisions require them. Always include the accessibility reference before final approval.\n\n## Workflow\n\nFollow this order unless the task explicitly scopes one stage.\n\n### 1. Understand the product\n\nIdentify the platform, primary user goal and action, top-level destinations, content hierarchy, data density, input methods, brand constraints, required states and edge cases, target window sizes, and whether M3 Expressive is appropriate.\n\nIf missing information does not block the work, make a conservative M3-aligned assumption and state it. Ask only when the missing information materially changes architecture or interaction.\n\n### 2. Establish information architecture\n\nBefore styling:\n\n- Group related information and identify the primary task per screen.\n- Separate navigation from actions and distinguish destructive actions.\n- Remove duplicated controls and define progressive disclosure.\n- Avoid showing information merely because space is available.\n\n### 3. Choose adaptive structure\n\nRead `references\u002Fadaptive-design.md` and `references\u002Fnavigation.md` when multiple window sizes or navigation forms matter.\n\nPrefer canonical patterns such as list-detail, supporting pane, feed, and adaptive navigation when they fit the content.\n\nWider space must improve context or productivity rather than merely stretch content.\n\n### 4. Build the theme semantically\n\nRead the relevant color, typography, shape\u002Felevation, and spacing references.\n\nUse the hierarchy:\n\n**reference\u002Fsystem tokens → semantic\u002Fsystem roles → component tokens**\n\nScreens should depend on semantic roles rather than scattered literal values.\n\n### 5. Select components\n\nRead `references\u002Fcomponent-selection.md` plus specialized navigation\u002Fform\u002Ffeedback references as needed.\n\nFor each important control, determine its semantic purpose, emphasis, immediate or transactional behavior, interaction states, accessibility behavior, and adaptive behavior.\n\n### 6. Define states and feedback\n\nCover relevant loading, empty, error, success, disabled, selected, pressed, focus, hover, and busy\u002Fsubmitting states.\n\nError states must provide a recovery path.\n\n### 7. Apply accessibility\n\nRead `references\u002Faccessibility.md`.\n\nAccessibility is a release requirement. Do not defer it to visual polish.\n\n### 8. Add motion\n\nRead `references\u002Fmotion.md` only when motion is part of the task.\n\nMotion must explain state, hierarchy, spatial relationship, or response. Do not animate for spectacle.\n\n### 9. Apply M3 Expressive if appropriate\n\nRead `references\u002Fm3-expressive.md`.\n\nUse a few deliberate expressive moments. Routine reading, forms, settings, and dense productivity surfaces should remain calm unless stronger expression improves usability.\n\n### 10. Audit before approval\n\nRead `references\u002Fanti-patterns.md` and run the self-audit below.\n\n## Self-audit\n\nBefore delivering a design, score each applicable category `0`, `1`, or `2`.\n\n- `0` = incorrect \u002F missing\n- `1` = partially correct \u002F needs refinement\n- `2` = ready\n\n| Category              | Check                                                        |\n|-----------------------|--------------------------------------------------------------|\n| Task clarity          | Primary user goal and action are obvious                     |\n| Information hierarchy | Grouping and emphasis are coherent                           |\n| Component semantics   | Controls match their actual behavior                         |\n| Token discipline      | Semantic roles are used consistently                         |\n| Adaptive behavior     | Layout improves across relevant windows                      |\n| States & feedback     | Important states and recovery are covered                    |\n| Accessibility         | Targets, contrast, semantics, focus, scaling, reduced motion |\n| Expressive restraint  | Expression improves hierarchy without creating noise         |\n\nA design with any `0` in **component semantics**, **states & feedback**, or **accessibility** is not ready for approval.\n\nDo not inflate scores to satisfy the user. State the concrete issue and correction.\n\n## Handoff contract\n\nWhen asked to design, redesign, audit, or hand off a UI, provide enough detail for another designer or developer to reproduce the decisions.\n\nUnless the user requests another format, include as applicable:\n\n1.  **Design intent** — user goal and hierarchy.\n2.  **Layout** — regions, panes, navigation, adaptive behavior.\n3.  **Theme roles** — semantic colors, typography, shape, elevation.\n4.  **Component map** — exact M3 component type\u002Fvariant for important controls.\n5.  **States** — interaction, loading, empty, error, success, disabled.\n6.  **Accessibility** — target size, contrast, names, focus, keyboard, scaling.\n7.  **Motion** — only meaningful transitions\u002Fstate changes.\n8.  **Implementation notes** — platform-specific caveats and experimental\u002Funsupported APIs.\n9.  **Self-audit** — include when the user asks for a review, audit, or production-readiness check.\n\nWhen creating actual code or an artifact, apply these decisions instead of stopping at a description.\n\n## Semantic handoff example\n\nPrefer:\n\n``` text\nScreen background: surface\nPrimary text: onSurface\nSecondary text: onSurfaceVariant\nPrimary CTA: filled button \u002F primary + onPrimary\nSecondary CTA: outlined button\nSection container: surfaceContainer\nSubtle separator: outlineVariant\nError container: errorContainer + onErrorContainer\n```\n\nAvoid handoff based on arbitrary literals unless they come from the project’s token system.\n\n## Platform implementation notes\n\n### Android \u002F Jetpack Compose\n\n- Prefer `androidx.compose.material3` for new M3 work.\n- Prefer stable APIs for production unless alpha\u002Fexperimental dependencies are explicitly accepted.\n- Do not assume every M3 Expressive API is stable.\n- Use Material theme roles rather than raw colors.\n- Follow current Android adaptive guidance for resizable and large-window experiences.\n- Treat edge-to-edge and system insets as layout concerns.\n- For Wear OS, use Wear Material 3 rather than mixing mobile components.\n\nDo not hardcode library version numbers into generated implementation unless they are verified against current official release notes.\n\n### Web \u002F other platforms\n\nMaterial 3 guidance can inform the design even when an official implementation library does not expose every component.\n\n- reproduce semantics and token relationships, not Android-specific quirks,\n- preserve native platform accessibility and input conventions,\n- mark custom implementations clearly,\n- do not claim official platform availability without verification.\n\n## Final principle\n\n**Material Design 3 is a semantic, adaptive, accessible design system.**\n\nA successful M3 interface should remain coherent when brand colors change, the window resizes, dark theme turns on, text scales up, keyboard replaces touch, or expressive styling is reduced.\n\nIf the design only works because every surface is rounded and colorful, it is not a robust Material 3 design.\n","# Material Design 3 UI\u002FUX\n\n## Purpose\n\nCreate interfaces that **behave like Material Design 3**, not interfaces that merely look rounded or “Google-like.”\n\nTreat M3 as a system:\n\n**user goal → information architecture → hierarchy → adaptive layout → semantic tokens → components → states → interaction → motion → accessibility → visual expression**\n\nM3 Expressive is optional. Use it to strengthen hierarchy, usability, recognition, and emotional clarity; never use it as permission to make every element loud.\n\n## Source of truth\n\n1.  Prefer current official Material 3 guidance at `https:\u002F\u002Fm3.material.io\u002F`.\n2.  For Android implementation details, prefer `https:\u002F\u002Fdeveloper.android.com\u002F`.\n3.  Treat design guidance separately from implementation-library\u002FAPI status.\n4.  Verify current official guidance before asserting exact dimensions, dependency versions, experimental API names, or recently changed behavior.\n5.  Do not silently mix Material 2 rules into Material 3.\n6.  Pixel and Google-app screenshots are examples, not the specification.\n\n## Core rules\n\n### MUST\n\n- Start from the user’s task, content, hierarchy, and platform before styling.\n- Use semantic design tokens instead of scattered one-off values.\n- Choose components by purpose and behavior, not visual resemblance.\n- Prefer established M3\u002Fplatform components when they solve the interaction.\n- Define important states: default, pressed, focus, hover where applicable, selected, disabled, loading, error, empty, and success where relevant.\n- Design for the available window rather than a guessed device category.\n- Preserve accessible contrast, target size, focus, semantics, scaling, and non-color state communication.\n- Respect system bars, safe areas, cutouts, keyboards\u002FIME, foldable hinges, and edge-to-edge behavior where applicable.\n- Keep primary actions distinguishable from secondary and destructive actions.\n- Make custom components inherit the token, state, motion, and accessibility logic of the system.\n- Explain deliberate departures from M3 when product requirements justify them.\n\n### MUST NOT\n\n- Do not “Materialize” a screen by only adding large radii, pastel colors, shadows, or Material Symbols.\n- Do not hardcode raw colors throughout screens when semantic roles can be used.\n- Do not use color alone to communicate meaning or state.\n- Do not wrap every section or list row in a card.\n- Do not maximize corner radius on every component.\n- Do not use FABs for minor, destructive, or ambiguous actions.\n- Do not use chips as generic buttons or primary navigation.\n- Do not use tabs for unrelated top-level destinations.\n- Do not make all components equally expressive.\n- Do not invent a new control when an established M3\u002Fplatform control already solves the interaction.\n- Do not sacrifice accessibility to preserve a visual composition.\n- Do not stretch a compact\u002Fmobile layout unchanged across wide windows.\n\n## Progressive-disclosure references\n\nLoad only the references needed for the current task. Do not read every reference by default.\n\n| Need                                                    | Read                                  |\n|---------------------------------------------------------|---------------------------------------|\n| Color roles, surfaces, dark theme, dynamic color        | `references\u002Fcolor-system.md`          |\n| Type hierarchy, scaling, expressive typography          | `references\u002Ftypography.md`            |\n| Shape, cards, containment, elevation                    | `references\u002Fshape-and-elevation.md`   |\n| Spacing, alignment, readable widths, safe areas         | `references\u002Fspacing-and-layout.md`    |\n| Buttons, FAB, cards, chips, selection, inputs, feedback | `references\u002Fcomponent-selection.md`   |\n| Navigation bar\u002Frail\u002Fdrawer, tabs, app bars              | `references\u002Fnavigation.md`            |\n| Forms, validation, settings, text input                 | `references\u002Fforms-and-input.md`       |\n| Snackbar, dialog, sheet, loading, empty\u002Ferror states    | `references\u002Ffeedback-and-overlays.md` |\n| Responsive, tablet, foldable, desktop, multi-pane       | `references\u002Fadaptive-design.md`       |\n| Accessibility audit or any final UI review              | `references\u002Faccessibility.md`         |\n| Transitions, feedback animation, shape morphing         | `references\u002Fmotion.md`                |\n| Material 3 Expressive                                   | `references\u002Fm3-expressive.md`         |\n| Final audit \u002F suspicious “Material-looking” UI          | `references\u002Fanti-patterns.md`         |\n\nFor a broad end-to-end design, load the references incrementally as decisions require them. Always include the accessibility reference before final approval.\n\n## Workflow\n\nFollow this order unless the task explicitly scopes one stage.\n\n### 1. Understand the product\n\nIdentify the platform, primary user goal and action, top-level destinations, content hierarchy, data density, input methods, brand constraints, required states and edge cases, target window sizes, and whether M3 Expressive is appropriate.\n\nIf missing information does not block the work, make a conservative M3-aligned assumption and state it. Ask only when the missing information materially changes architecture or interaction.\n\n### 2. Establish information architecture\n\nBefore styling:\n\n- Group related information and identify the primary task per screen.\n- Separate navigation from actions and distinguish destructive actions.\n- Remove duplicated controls and define progressive disclosure.\n- Avoid showing information merely because space is available.\n\n### 3. Choose adaptive structure\n\nRead `references\u002Fadaptive-design.md` and `references\u002Fnavigation.md` when multiple window sizes or navigation forms matter.\n\nPrefer canonical patterns such as list-detail, supporting pane, feed, and adaptive navigation when they fit the content.\n\nWider space must improve context or productivity rather than merely stretch content.\n\n### 4. Build the theme semantically\n\nRead the relevant color, typography, shape\u002Felevation, and spacing references.\n\nUse the hierarchy:\n\n**reference\u002Fsystem tokens → semantic\u002Fsystem roles → component tokens**\n\nScreens should depend on semantic roles rather than scattered literal values.\n\n### 5. Select components\n\nRead `references\u002Fcomponent-selection.md` plus specialized navigation\u002Fform\u002Ffeedback references as needed.\n\nFor each important control, determine its semantic purpose, emphasis, immediate or transactional behavior, interaction states, accessibility behavior, and adaptive behavior.\n\n### 6. Define states and feedback\n\nCover relevant loading, empty, error, success, disabled, selected, pressed, focus, hover, and busy\u002Fsubmitting states.\n\nError states must provide a recovery path.\n\n### 7. Apply accessibility\n\nRead `references\u002Faccessibility.md`.\n\nAccessibility is a release requirement. Do not defer it to visual polish.\n\n### 8. Add motion\n\nRead `references\u002Fmotion.md` only when motion is part of the task.\n\nMotion must explain state, hierarchy, spatial relationship, or response. Do not animate for spectacle.\n\n### 9. Apply M3 Expressive if appropriate\n\nRead `references\u002Fm3-expressive.md`.\n\nUse a few deliberate expressive moments. Routine reading, forms, settings, and dense productivity surfaces should remain calm unless stronger expression improves usability.\n\n### 10. Audit before approval\n\nRead `references\u002Fanti-patterns.md` and run the self-audit below.\n\n## Self-audit\n\nBefore delivering a design, score each applicable category `0`, `1`, or `2`.\n\n- `0` = incorrect \u002F missing\n- `1` = partially correct \u002F needs refinement\n- `2` = ready\n\n| Category              | Check                                                        |\n|-----------------------|--------------------------------------------------------------|\n| Task clarity          | Primary user goal and action are obvious                     |\n| Information hierarchy | Grouping and emphasis are coherent                           |\n| Component semantics   | Controls match their actual behavior                         |\n| Token discipline      | Semantic roles are used consistently                         |\n| Adaptive behavior     | Layout improves across relevant windows                      |\n| States & feedback     | Important states and recovery are covered                    |\n| Accessibility         | Targets, contrast, semantics, focus, scaling, reduced motion |\n| Expressive restraint  | Expression improves hierarchy without creating noise         |\n\nA design with any `0` in **component semantics**, **states & feedback**, or **accessibility** is not ready for approval.\n\nDo not inflate scores to satisfy the user. State the concrete issue and correction.\n\n## Handoff contract\n\nWhen asked to design, redesign, audit, or hand off a UI, provide enough detail for another designer or developer to reproduce the decisions.\n\nUnless the user requests another format, include as applicable:\n\n1.  **Design intent** — user goal and hierarchy.\n2.  **Layout** — regions, panes, navigation, adaptive behavior.\n3.  **Theme roles** — semantic colors, typography, shape, elevation.\n4.  **Component map** — exact M3 component type\u002Fvariant for important controls.\n5.  **States** — interaction, loading, empty, error, success, disabled.\n6.  **Accessibility** — target size, contrast, names, focus, keyboard, scaling.\n7.  **Motion** — only meaningful transitions\u002Fstate changes.\n8.  **Implementation notes** — platform-specific caveats and experimental\u002Funsupported APIs.\n9.  **Self-audit** — include when the user asks for a review, audit, or production-readiness check.\n\nWhen creating actual code or an artifact, apply these decisions instead of stopping at a description.\n\n## Semantic handoff example\n\nPrefer:\n\n``` text\nScreen background: surface\nPrimary text: onSurface\nSecondary text: onSurfaceVariant\nPrimary CTA: filled button \u002F primary + onPrimary\nSecondary CTA: outlined button\nSection container: surfaceContainer\nSubtle separator: outlineVariant\nError container: errorContainer + onErrorContainer\n```\n\nAvoid handoff based on arbitrary literals unless they come from the project’s token system.\n\n## Platform implementation notes\n\n### Android \u002F Jetpack Compose\n\n- Prefer `androidx.compose.material3` for new M3 work.\n- Prefer stable APIs for production unless alpha\u002Fexperimental dependencies are explicitly accepted.\n- Do not assume every M3 Expressive API is stable.\n- Use Material theme roles rather than raw colors.\n- Follow current Android adaptive guidance for resizable and large-window experiences.\n- Treat edge-to-edge and system insets as layout concerns.\n- For Wear OS, use Wear Material 3 rather than mixing mobile components.\n\nDo not hardcode library version numbers into generated implementation unless they are verified against current official release notes.\n\n### Web \u002F other platforms\n\nMaterial 3 guidance can inform the design even when an official implementation library does not expose every component.\n\n- reproduce semantics and token relationships, not Android-specific quirks,\n- preserve native platform accessibility and input conventions,\n- mark custom implementations clearly,\n- do not claim official platform availability without verification.\n\n## Final principle\n\n**Material Design 3 is a semantic, adaptive, accessible design system.**\n\nA successful M3 interface should remain coherent when brand colors change, the window resizes, dark theme turns on, text scales up, keyboard replaces touch, or expressive styling is reduced.\n\nIf the design only works because every surface is rounded and colorful, it is not a robust Material 3 design.\n",{"name":5,"metadata":24,"description":7},{"updated":25,"version":26},1790812800000,"1.1.1","main","a22dccb577b5d59b83ac12e9e784b16d919df95d","used skills\u002F18-skydashnet-material-design-3-ui-skill",1,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island","https:\u002F\u002Fgithub.com\u002FDarshan8610","2026-10-31 11:29:16",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Darshan8610\u002FDynamic-Island --skill material-design-3-ui",{"tool":40,"command":41},"bunx","bunx skills add Darshan8610\u002FDynamic-Island --skill material-design-3-ui",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Darshan8610\u002FDynamic-Island --skill material-design-3-ui","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002FSKILL.md",true,[48,54,58,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,140,144,148,152,156,160,164,168],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"CHANGELOG.md","REFERENCE","参考文档",1999,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002FCHANGELOG.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"CONTRIBUTING.md",4863,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002FCONTRIBUTING.md",{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"install.ps1","SCRIPT","脚本",9661,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Finstall.ps1",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"install.sh",8879,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Finstall.sh",{"path":69,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":15},"LICENSE","许可证",1104,{"path":73,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":74,"sourceHtmlUrl":75},"README.md",22843,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002FREADME.md",{"path":77,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Faccessibility.md",2199,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Freferences\u002Faccessibility.md",{"path":81,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fadaptive-design.md",1996,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Freferences\u002Fadaptive-design.md",{"path":85,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fanti-patterns.md",2215,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Freferences\u002Fanti-patterns.md",{"path":89,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fcolor-system.md",2817,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Freferences\u002Fcolor-system.md",{"path":93,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fcomponent-selection.md",4527,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Freferences\u002Fcomponent-selection.md",{"path":97,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Ffeedback-and-overlays.md",1891,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Freferences\u002Ffeedback-and-overlays.md",{"path":101,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fforms-and-input.md",2108,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Freferences\u002Fforms-and-input.md",{"path":105,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fm3-expressive.md",1738,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Freferences\u002Fm3-expressive.md",{"path":109,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fmotion.md",1371,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Freferences\u002Fmotion.md",{"path":113,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":114,"sourceHtmlUrl":115},"references\u002Fnavigation.md",1961,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Freferences\u002Fnavigation.md",{"path":117,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":118,"sourceHtmlUrl":119},"references\u002Fshape-and-elevation.md",1812,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Freferences\u002Fshape-and-elevation.md",{"path":121,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":122,"sourceHtmlUrl":123},"references\u002Fspacing-and-layout.md",1579,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Freferences\u002Fspacing-and-layout.md",{"path":125,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":126,"sourceHtmlUrl":127},"references\u002Ftypography.md",2049,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Freferences\u002Ftypography.md",{"path":129,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":130,"sourceHtmlUrl":131},"skill-files.txt",388,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Fskill-files.txt",{"path":133,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":134,"sourceHtmlUrl":135},"tests\u002Fcases\u002F01-settings-screen.md",875,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Ftests\u002Fcases\u002F01-settings-screen.md",{"path":137,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":138,"sourceHtmlUrl":139},"tests\u002Fcases\u002F02-dashboard.md",813,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Ftests\u002Fcases\u002F02-dashboard.md",{"path":141,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":142,"sourceHtmlUrl":143},"tests\u002Fcases\u002F03-navigation.md",801,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Ftests\u002Fcases\u002F03-navigation.md",{"path":145,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":146,"sourceHtmlUrl":147},"tests\u002Fcases\u002F04-form-validation.md",720,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Ftests\u002Fcases\u002F04-form-validation.md",{"path":149,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":150,"sourceHtmlUrl":151},"tests\u002Fcases\u002F05-m3-expressive.md",818,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Ftests\u002Fcases\u002F05-m3-expressive.md",{"path":153,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":154,"sourceHtmlUrl":155},"tests\u002Fcases\u002F06-audit-fake-material.md",695,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Ftests\u002Fcases\u002F06-audit-fake-material.md",{"path":157,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":158,"sourceHtmlUrl":159},"tests\u002FREADME.md",1120,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Ftests\u002FREADME.md",{"path":161,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":162,"sourceHtmlUrl":163},"tests\u002Fvalidate_skill.py",3807,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Ftests\u002Fvalidate_skill.py",{"path":165,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":166,"sourceHtmlUrl":167},"uninstall.ps1",877,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Funinstall.ps1",{"path":169,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":170,"sourceHtmlUrl":171},"uninstall.sh",679,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002Funinstall.sh",[173,182,190,198,205,212],{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":177,"licenseFileUrl":178,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":19},"01M7D6EQ4V97KQAAJDX03NH1PK","security-review","Security code review for vulnerabilities. Use when asked to \"security review\", \"find vulnerabilities\", \"check for security issues\", \"audit security\", \"OWASP review\", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.","CC-BY-SA-4.0","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F25-getsentry-skills\u002Fskills\u002Fsecurity-review\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F25-getsentry-skills\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":186,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":189,"publishedAt":19},"01M7D6EFH7JA3N91H85BMF90X5","security-model","Define, review, or update SECURITY_MODEL.md files that tell security review tools a repository's threat model, trust boundaries, invariants, reportable finding classes, and exclusions. Use when asked to \"write a security model\", \"threat model this repo for scanners\", \"define security review scope\", \"what counts as a vulnerability here\", \"update SECURITY_MODEL.md\", \"why did the scanner flag or miss this\", or to check whether existing security guidance still matches the code. Not for running a security review or editing the SECURITY.md disclosure policy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F25-getsentry-skills\u002Fskills\u002Fsecurity-model\u002FSKILL.md",[],[],{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":194,"sourceHtmlUrl":195,"categories":196,"keywords":197,"publishedAt":19},"01M7D69FRBB22BSGEJBFH71JA4","mobile-harness","Portable Android and iOS device-control harness for agents. Use when an agent needs to control or automate Android\u002FiOS devices — tap, swipe, screenshot, app control — locally (ADB\u002FPortal\u002FSimulator) or on Mobilerun cloud devices.","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F23-droidrun-mobile-harness\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F23-droidrun-mobile-harness\u002FSKILL.md",[],[],{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":204,"publishedAt":19},"01M7D5Z37XC1K629HJP6DMA2CF","compose-agent","Helps AI coding assistants write modern Jetpack Compose: correct state, side effects, performance-aware modifiers, Navigation 3, Paging 3 in Compose, coroutines on lifecycle, animations, UI tests, focus\u002Fkeyboard navigation, Compose Multiplatform boundaries, idiomatic Kotlin, and well-shaped composable APIs. Targets the mistakes LLMs actually make in Compose code. Use when reading, writing, or reviewing Compose projects.","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F20-hamen-compose_skill\u002Fskills\u002Fcompose-agent\u002FSKILL.md",[],[],{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":209,"categories":210,"keywords":211,"publishedAt":19},"01M7D5A2RS4MAX9H0CGT60NQ1B","web-design-guidelines","Web platform design and accessibility guidelines. Use when building web interfaces, auditing accessibility, implementing responsive layouts, or reviewing web UI code. Triggers on tasks involving HTML, CSS, web components, WCAG compliance, responsive design, or web performance.","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F17-ehmo-platform-design-skills\u002Fskills\u002Fweb\u002FSKILL.md",[],[],{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":216,"categories":217,"keywords":218,"publishedAt":19},"01M7D59YEAB0TPVFWVPMCHYY15","watchos-design-guidelines","Apple Human Interface Guidelines for Apple Watch. Use when building watchOS apps, complications, or workout features. Triggers on tasks involving Watch UI, Digital Crown, glanceable interfaces, or wrist-based interactions.","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F17-ehmo-platform-design-skills\u002Fskills\u002Fwatchos\u002FSKILL.md",[],[]]