Material Design 3 UI/UX Guide
skydashnet/material-design-3-ui-skill
Guides designing, reviewing or implementing interfaces that follow Google's Material Design 3 system: semantic tokens, component states, adaptive layout and accessibility.
A skill your agent uses when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up.
Install Explorer Interface Brief
$ npx skills add mohitagw15856/pm-claude-skills --skill explorer-interface-brief -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills explorer-interface-brief --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/explorer-interface-brief .claude/skills/explorer-interface-brief && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "explorer-interface-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/explorer-interface-brief into .claude/skills/explorer-interface-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explorer-interface-brief", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/explorer-interface-briefType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill explorer-interface-brief -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills explorer-interface-brief --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/explorer-interface-brief .agents/skills/explorer-interface-brief && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "explorer-interface-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/explorer-interface-brief into .agents/skills/explorer-interface-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explorer-interface-brief", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill explorer-interface-brief -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills explorer-interface-brief --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/explorer-interface-brief .cursor/skills/explorer-interface-brief && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "explorer-interface-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/explorer-interface-brief into .cursor/skills/explorer-interface-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explorer-interface-brief", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/explorer-interface-brief--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill explorer-interface-brief -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills explorer-interface-brief --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/explorer-interface-brief .gemini/skills/explorer-interface-brief && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "explorer-interface-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/explorer-interface-brief into .gemini/skills/explorer-interface-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explorer-interface-brief", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills explorer-interface-briefInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill explorer-interface-brief -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/explorer-interface-brief .github/skills/explorer-interface-brief && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "explorer-interface-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/explorer-interface-brief into .github/skills/explorer-interface-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explorer-interface-brief", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill explorer-interface-brief -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills explorer-interface-brief --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/explorer-interface-brief .opencode/skills/explorer-interface-brief && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "explorer-interface-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/explorer-interface-brief into .opencode/skills/explorer-interface-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explorer-interface-brief", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
explorer-interface-brief- GitHub stars
- 1.4k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 567 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up.
- Works in 3 steps: Design brief → Image-model prompt for the interface mock → Handover notes
- Asked to design the interface for an interactive 3D explorer
- SKILL.md covers Required Inputs, Output Structure, Quality Checks and Anti-Patterns, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Explorer Interface Brief is an agent skill from mohitagw15856/pm-claude-skills. Use when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up. Produces, from a topic, the UI design brief (audience, layout, panels, interactions, label style, colour palette, accessibility) and an image-model prompt for the interface mock. First step of explorer-pipeline.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering Theming and dark mode, UI design and 3D graphics and WebGL. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to design the interface for an interactive 3D explorer
- Plan a UI for exploring a 3D model of a topic
- Write an image-model prompt for a 3D learning app mock-up
Example prompts
- “/explorer-interface-brief”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Explorer Interface Brief loads about 1.2k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 567 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 567 words, ~1,188 tokens.
Download SKILL.mdSave it as
.claude/skills/explorer-interface-brief/SKILL.md (or your agent's skills folder).- name
- explorer-interface-brief
- description
- Use when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up. Produces, from a topic, the UI design brief (audience, layout, panels, interactions, label style, colour palette, accessibility) and an image-model prompt for the interface mock. First step of explorer-pipeline.
- version
- 1.0.0
Explorer Interface Brief
A 3D explorer (a heart, a jet engine, a cell, a volcano) succeeds or fails on its interface: where the model sits, how labels read against it, how a learner moves between free exploration and testing themselves. This skill turns a topic into a design brief a builder can follow and an image-model prompt that produces a convincing mock of the screen before any 3D work starts.
Required Inputs
Ask for these if not provided:
- Topic and the specific object or system to explore
- Audience: age or level (for example 14-year-old students, first-year medical students, museum visitors)
- Learning goal: what the learner should be able to name, explain or do afterwards
- Devices: classroom laptops, phones, a museum touch screen
- Brand or colour constraints, if any
Output Structure
1. Design brief
- Purpose: one sentence: who explores what, to learn what
- Audience notes: reading level, prior knowledge, device and setting
- Learning outcomes: three to five, each starting with a verb (name, locate, explain)
- Layout: the model stage, a side panel (or bottom sheet on phones) with the selected part's label, description and source, a parts list, and a toolbar (exploded view, quiz mode, reset). Give proportions for desktop and phone.
- Interactions: rotate, zoom, select (click, tap and keyboard via the parts list), exploded view, quiz mode, reset. State the response to each.
- Label style: font, size (at least 16 px body), casing, how labels attach to parts (side panel rather than floating text over geometry), and what a "source" line looks like
- Colour palette: background, panel, ink, accent and highlight as hex values, each pair checked for at least 4.5:1 contrast for text; a dark-mode variant
- Accessibility: keyboard path to every part, visible focus, reduced motion respected, no information carried by colour alone
- Content rules: every label carries a named source; the model is described as illustrative
2. Image-model prompt for the interface mock
A single prompt in this structure, ready for an image model:
UI mock-up, [device] screen, [width]x[height] aspect, of an interactive 3D explorer for [topic].
Left: [model description] on a [background colour] stage, three-quarter view, soft studio light.
Right: a [panel colour] side panel with a title "[part name]", two lines of body text, a small
"Source: [source]" line, and a list of [n] part names. Top of panel: three pill buttons
"Exploded view", "Quiz mode", "Reset". Flat design, [palette as colour names], generous spacing,
light sans-serif typography, no device frame, no watermark, legible placeholder text.Plus a negative prompt (cluttered UI, tiny text, neon colours, photorealistic hands, watermarks) and two variants: one for phone in portrait, one for dark mode.
Show full SKILL.md (216 more words)Show less
3. Handover notes
What the next steps need from this brief: the parts list it implies (for model-prompt-pack) and the palette and layout values (for explorer-viewer-builder), as a short table.
Quality Checks
- Learning outcomes are three to five and each starts with a verb
- Every interaction has a keyboard path, including selecting parts
- Every palette text pair is stated with a contrast of at least 4.5:1
- Layout is specified for both desktop and phone
- The image prompt names device, aspect, palette and every panel element
- The brief requires a named source for every label and calls the model illustrative
- The handover table lists the parts list and palette values
Anti-Patterns
- Labels floating over the model. They collide and become unreadable when the model rotates; use a side panel.
- Beautiful but unteachable. A brief with no learning outcomes produces a toy.
- Mouse-only selection. Keyboard and screen-reader users need the parts list.
- Mocks with unreadable text. Ask for legible placeholder text, or the mock misleads reviewers.
Example Trigger Phrases
- "Design the interface for a 3D explorer of the human heart for GCSE students."
- "Write an image prompt for a UI mock of an interactive jet engine viewer."
- "Plan the screens for a museum touch-screen 3D model of a volcano."
- "Brief for a 3D cell explorer app, phone first."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/explorer-interface-brief of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Explorer Interface Brief next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Explorer Interface Brief this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Material Design 3 UI/UX Guideskydashnet/material-design-3-ui-skill | 135 | — | ~3k | Automated safety check: Pass | MIT | |
| Better Designmarvkr/better-design | 254 | — | ~1.2k | Automated safety check: Pass | MIT | |
| UI Design Systemtry-works/role-model | 118 | — | ~5k | Automated safety check: Pass | MIT | |
| UI UX Pro MaxOhh-889/skyroc | 795 | 27 repos | ~3.6k | Automated safety check: Notes | MIT | |
| UI UX Pro Maxselmakcby/claude-agents-skills | 136 | — | ~777 | Automated safety check: Pass | MIT |
Similar skills
Better Design
marvkr/better-design
Build, improve, and review production interfaces with the Better Design MCP.
UI Design System
try-works/role-model
React UI component systems with TailwindCSS + Radix + shadcn/ui.
UI UX Pro Max
Ohh-889/skyroc
UI/UX design intelligence. An agent skill from Ohh-889/skyroc.
UI UX Pro Max
selmakcby/claude-agents-skills
UI/UX design intelligence for web and mobile. An agent skill from selmakcby/claude-agents-skills.
Apply Aesthetic
plugin87/ux-ui-agent-skills
Applies a chosen visual direction, an archetype or one of 138 named design systems, by remapping design tokens, then checks contrast before it finishes.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Explorer Interface Brief
What does Explorer Interface Brief do?
A skill your agent uses when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up. Explorer Interface Brief is an agent skill from mohitagw15856/pm-claude-skills. Use when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up.
When should I use Explorer Interface Brief?
Explorer Interface Brief fits situations like: asked to design the interface for an interactive 3D explorer; plan a UI for exploring a 3D model of a topic; write an image-model prompt for a 3D learning app mock-up.
How do I install Explorer Interface Brief in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill explorer-interface-brief -a claude-code`. Or copy the skill folder (skills/explorer-interface-brief in mohitagw15856/pm-claude-skills) into .claude/skills/explorer-interface-brief in your project. Claude Code loads it when a task matches its description.
How do I install Explorer Interface Brief in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill explorer-interface-brief -a codex`. Or copy the skill folder (skills/explorer-interface-brief in mohitagw15856/pm-claude-skills) into .agents/skills/explorer-interface-brief in your project. Codex loads it when a task matches its description.
Can I use Explorer Interface Brief in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill explorer-interface-brief -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/explorer-interface-brief, .gemini/skills/explorer-interface-brief, .github/skills/explorer-interface-brief and .opencode/skills/explorer-interface-brief in your project.
What does Explorer Interface Brief need to run?
SKILL.md names no scripts, command-line tools or credentials: Explorer Interface Brief is instructions for the agent only.
Does Explorer Interface Brief access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Explorer Interface Brief safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Explorer Interface Brief use?
Explorer Interface Brief is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Explorer Interface Brief use?
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Explorer Interface Brief?
Skills that share tags, products or a category with Explorer Interface Brief: Material Design 3 UI/UX Guide (skydashnet/material-design-3-ui-skill, 135 stars), Better Design (marvkr/better-design, 254 stars), UI Design System (try-works/role-model, 118 stars) and UI UX Pro Max (Ohh-889/skyroc, 795 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Explorer Interface Brief?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,433 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 8, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.