Skip to content
TrustedSkillsbeta
Back to all skills

Material 3 To Material 2 Theme Adapter

Checked
rodydavis·vlatest·frontend

This skill seamlessly converts Material 3 themes into Material 2, streamlining design transitions and saving development time.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add rodydavis/skills --skill material-3-to-material-2-theme-adapter -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

rodydavis

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned rodydavis/skills at 804913dcbe.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
804913dcbe
Manifest
skills/snippets_m3-to-m2-css-adapter/SKILL.md
Scanned
1 file, 27 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The material-3-to-material-2-theme-adapter allows AI agents to dynamically switch between Material Design 3 and Material Design 2 visual themes. It ensures consistent styling when applications need to support legacy Material 2 components alongside modern Material 3 interfaces. This utility resolves conflicts that arise when mixing design systems within a single project.

When to use it

  • Migrating an existing app from Material 2 to Material 3 while keeping older components functional.
  • Creating hybrid UIs where specific sections require the stricter guidelines of Material Design 2.
  • Testing how AI-generated layouts adapt when the underlying theme version changes.
  • Maintaining backward compatibility during a gradual design system overhaul.

Key capabilities

  • Seamless integration between Material 3 and Material 2 component libraries.
  • Dynamic theme switching without breaking existing UI structures.
  • Resolution of visual inconsistencies caused by mixed design tokens.
  • Support for both light and dark mode configurations across versions.

Example prompts

  • "Apply the material-3-to-material-2-theme-adapter to my dashboard so legacy charts match the new color scheme."
  • "Switch the sidebar navigation to Material 2 style while keeping the main content area in Material 3."
  • "Fix the broken button styles after I updated the project theme to Material 3 using this adapter."

Tips & gotchas

Ensure your base application supports both design versions before installing, as some custom CSS may override the adapter's defaults. Monitor for specific component conflicts if you are mixing third-party libraries that enforce strict versioning rules.