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.
Produces an implementation-ready spec from a finished design, covering layout, tokens, states, responsive behavior, edge cases, motion and accessibility, so engineers do not have to guess.
Install Design Handoff Spec
$ npx skills add getcrew44/crew44 --skill design-handoff -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install getcrew44/crew44 design-handoff --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/getcrew44/crew44.git skills-src && mkdir -p .claude/skills && cp -r skills-src/daemon/internal/presets/defaultcrew/skills/designer/design-handoff .claude/skills/design-handoff && 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 "design-handoff" agent skill from https://github.com/getcrew44/crew44/tree/main/daemon/internal/presets/defaultcrew/skills/designer/design-handoff into .claude/skills/design-handoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-handoff", 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/getcrew44/crew44/tree/main/daemon/internal/presets/defaultcrew/skills/designer/design-handoffType 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 getcrew44/crew44 --skill design-handoff -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install getcrew44/crew44 design-handoff --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getcrew44/crew44.git skills-src && mkdir -p .agents/skills && cp -r skills-src/daemon/internal/presets/defaultcrew/skills/designer/design-handoff .agents/skills/design-handoff && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "design-handoff" agent skill from https://github.com/getcrew44/crew44/tree/main/daemon/internal/presets/defaultcrew/skills/designer/design-handoff into .agents/skills/design-handoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-handoff", 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 getcrew44/crew44 --skill design-handoff -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install getcrew44/crew44 design-handoff --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getcrew44/crew44.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/daemon/internal/presets/defaultcrew/skills/designer/design-handoff .cursor/skills/design-handoff && 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 "design-handoff" agent skill from https://github.com/getcrew44/crew44/tree/main/daemon/internal/presets/defaultcrew/skills/designer/design-handoff into .cursor/skills/design-handoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-handoff", 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/getcrew44/crew44.git --path daemon/internal/presets/defaultcrew/skills/designer/design-handoff--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 getcrew44/crew44 --skill design-handoff -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install getcrew44/crew44 design-handoff --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getcrew44/crew44.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/daemon/internal/presets/defaultcrew/skills/designer/design-handoff .gemini/skills/design-handoff && 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 "design-handoff" agent skill from https://github.com/getcrew44/crew44/tree/main/daemon/internal/presets/defaultcrew/skills/designer/design-handoff into .gemini/skills/design-handoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-handoff", 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 getcrew44/crew44 design-handoffInstalls 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 getcrew44/crew44 --skill design-handoff -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/getcrew44/crew44.git skills-src && mkdir -p .github/skills && cp -r skills-src/daemon/internal/presets/defaultcrew/skills/designer/design-handoff .github/skills/design-handoff && 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 "design-handoff" agent skill from https://github.com/getcrew44/crew44/tree/main/daemon/internal/presets/defaultcrew/skills/designer/design-handoff into .github/skills/design-handoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-handoff", 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 getcrew44/crew44 --skill design-handoff -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install getcrew44/crew44 design-handoff --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getcrew44/crew44.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/daemon/internal/presets/defaultcrew/skills/designer/design-handoff .opencode/skills/design-handoff && 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 "design-handoff" agent skill from https://github.com/getcrew44/crew44/tree/main/daemon/internal/presets/defaultcrew/skills/designer/design-handoff into .opencode/skills/design-handoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-handoff", 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
design-handoff- GitHub stars
- 356
- Token cost
- ~680 tokens
- SKILL.md length
- 362 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT
At a glance
Produces an implementation-ready spec from a finished design, covering layout, tokens, states, responsive behavior, edge cases, motion and accessibility, so engineers do not have to guess.
- Works in 9 steps: Overview. What this screen or component… → Layout. Grid, breakpoints, responsive… → Tokens used. Color, typography, spacing,… → …
- Handing a finished screen or component design to engineers
- SKILL.md covers Principles, Sections the spec must cover, Common spec gaps that cause… and Output
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
This skill writes the document that carries a design to engineering. It rests on four habits: cite design tokens by name instead of raw pixel or hex values and flag any value missing from the system as a token gap, list every state of every element, give the reason behind decisions so engineers can make good calls when reality differs from the spec, and pin down edge cases beyond the happy path.
The spec has nine sections: overview, layout, tokens used, components, states and interactions, responsive behavior, edge cases, motion and accessibility. Motion entries give trigger, movement, duration and easing and respect reduced-motion settings; accessibility covers focus order, ARIA roles, keyboard use, screen reader announcements and contrast. It is a single document built from tables and short bullets, with open questions at the end labeled by who must answer: engineering, product or content. A list of commonly missed items, such as loading, error and empty states, helps avoid rework.
When your agent uses it
- Handing a finished screen or component design to engineers
- Checking an existing design spec for missing states and edge cases
- Documenting responsive and motion behavior before implementation begins
Example prompts
- “Write the handoff spec for the new billing settings screen, using our token names.”
- “Review this component spec and list which states and edge cases it leaves out.”
- “Document how the checkout summary changes at each breakpoint and what animates.”
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Overview. What this screen or component does, who uses it, and the user state when they encounter it.
- Layout. Grid, breakpoints, responsive behavior at each breakpoint. Where things move, hide, or change order.
- Tokens used. Color, typography, spacing, radius, shadow — listed with their token names and where they apply.
- Components. Each component named, with variants, props that matter for behavior, and any composition rules.
- States and interactions. Per element, the full state list with the visual change and trigger.
- Responsive behavior. What changes at each breakpoint. Not just "stacks on mobile" — what gets prioritized, what gets cut.
- Edge cases. Long copy, empty data, zero results, max items, slow connection, error states. The expected behavior for each.
- Motion. Per animated element: trigger, what moves, duration, easing. Honor prefers-reduced-motion.
- Accessibility. Focus order, ARIA labels and roles, keyboard interactions, screen reader announcements, contrast confirmations.
What it can do on your machine
Read from SKILL.md and the folder at commit cfcf1e7. 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
Design Handoff Spec loads about 680 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 362 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 getcrew44/crew44 at commit cfcf1e7, republished under its MIT licence (© getcrew44). 362 words, ~680 tokens.
Download SKILL.mdSave it as
.claude/skills/design-handoff/SKILL.md (or your agent's skills folder).- name
- design-handoff
- description
- Use when a design is ready for engineering — produce an implementation-ready spec covering layout, tokens, states, responsive behavior, edge cases, motion, and accessibility.
Design Handoff
Produce a spec that lets the Coding Agent build the design without guessing. If it isn't specified, they'll have to invent — and they'll invent inconsistently.
Principles
- Tokens, not values. Reference
--space-4orcolor-primary-600, not16pxor#2563eb. If a value isn't in the system, flag that as a token gap, not a one-off. - Show every state. Default, hover, active, focus, disabled, loading, error, empty, success. A state you skip becomes a bug.
- Explain the why. "This collapses to a sheet on mobile because the action is one-handed" helps the engineer make sensible judgment calls when reality diverges from the spec.
- Specify edges, not just the happy path. Long text, no text, slow connection, partial data — pin the behavior.
Sections the spec must cover
- Overview. What this screen or component does, who uses it, and the user state when they encounter it.
- Layout. Grid, breakpoints, responsive behavior at each breakpoint. Where things move, hide, or change order.
- Tokens used. Color, typography, spacing, radius, shadow — listed with their token names and where they apply.
- Components. Each component named, with variants, props that matter for behavior, and any composition rules.
- States and interactions. Per element, the full state list with the visual change and trigger.
- Responsive behavior. What changes at each breakpoint. Not just "stacks on mobile" — what gets prioritized, what gets cut.
- Edge cases. Long copy, empty data, zero results, max items, slow connection, error states. The expected behavior for each.
- Motion. Per animated element: trigger, what moves, duration, easing. Honor
prefers-reduced-motion. - Accessibility. Focus order, ARIA labels and roles, keyboard interactions, screen reader announcements, contrast confirmations.
Show full SKILL.md (87 more words)Show less
Common spec gaps that cause rework
- Loading and error states for async content.
- What happens when content overflows (truncate? wrap? scroll?).
- Empty state for collections that start empty.
- Behavior under slow or failed network.
- Keyboard shortcuts and tab order through complex layouts.
- Animation choreography across linked elements.
Output
A single document with the sections above. Each section uses tables or short bullets, not prose paragraphs. Tokens and component names cited verbatim. Open questions called out at the bottom, tagged with who needs to answer (engineering, product, content).
© getcrew44, 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 daemon/internal/presets/defaultcrew/skills/designer/design-handoff of getcrew44/crew44.
Open the folder on GitHubat commit cfcf1e7
Compare with similar skills
Design Handoff Spec 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 |
|---|---|---|---|---|---|---|
| Design Handoff Spec this skillgetcrew44/crew44 | 356 | — | ~680 | Automated safety check: Pass | MIT | |
| Material Design 3 UI/UX Guideskydashnet/material-design-3-ui-skill | 130 | — | ~3k | Automated safety check: Pass | MIT | |
| UI Design Systemtry-works/role-model | 118 | — | ~5k | Automated safety check: Pass | MIT | |
| Interface KitJuliusBrussee/skills | 161 | 1 repos | ~5.3k | Automated safety check: Pass | MIT | |
| Stitch to React and Vite Dashboardgoogle-labs-code/stitch-skills | 8.4k | — | ~914 | Automated safety check: Notes | Apache-2.0 | |
| Design Code for Any Frameworkplugin87/ux-ui-agent-skills | 1.5k | — | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
UI Design System
try-works/role-model
React UI component systems with TailwindCSS + Radix + shadcn/ui.
Interface Kit
JuliusBrussee/skills
Authoritative guide for implementing stunning, accessible, performant UI.
- Official
Stitch to React and Vite Dashboard
google-labs-code/stitch-skills
Turns Stitch screens into a React, Vite and TypeScript dashboard with TanStack Query data fetching, DESIGN.md tokens as CSS variables and optional read-only Web3 data.
Design Code for Any Framework
plugin87/ux-ui-agent-skills
Generates complete, accessible, token-driven UI component code for a chosen framework such as React with Tailwind, SwiftUI, Vue, Flutter or Jetpack Compose.
OpenClaw Design Audit
openclaw/clawhub
Audits OpenClaw frontend code and rendered pages for token misuse, reimplemented primitives, accessibility and responsive defects and off-brand copy, with an evidence-based report.
More from getcrew44/crew44
All 9 skills in this repoEnd-of-Life Announcement Writer
getcrew44/crew44
Drafts a clear, empathetic end-of-life announcement for a product, feature or plan, covering rationale, customer impact, transition support, timeline and next steps.
Session Skill Mining
getcrew44/crew44
Reviews past Codex or Claude Code sessions from a time range you choose and proposes skills to codify and memories to pin, as a summary plus structured JSON.
WCAG 2.1 AA Accessibility Review
getcrew44/crew44
Audits a design or page against WCAG 2.1 AA for contrast, keyboard use, focus, labels, touch targets and screen reader behavior, with a severity-ranked report.
Design Critique
getcrew44/crew44
Walks an agent through five review passes on a screen, flow or mockup, then returns ranked findings with a severity and a suggested fix for each one.
Interaction Review
getcrew44/crew44
A skill your agent uses to evaluate or design a user interaction flow — states, edge cases, microinteractions, motion, and feedback patterns.
UX Copy
getcrew44/crew44
A skill your agent uses to write or review microcopy — CTAs, error messages, empty states, confirmation dialogs, tooltips, onboarding text.
Related
Questions about Design Handoff Spec
What does Design Handoff Spec do?
Produces an implementation-ready spec from a finished design, covering layout, tokens, states, responsive behavior, edge cases, motion and accessibility, so engineers do not have to guess. This skill writes the document that carries a design to engineering. It rests on four habits: cite design tokens by name instead of raw pixel or hex values and flag any value missing from the system as a token gap, list every state of every element, give the reason behind decisions so engineers can make good calls when reality differs from the spec, and pin down edge cases beyond the happy path.
When should I use Design Handoff Spec?
Design Handoff Spec fits situations like: handing a finished screen or component design to engineers; checking an existing design spec for missing states and edge cases; documenting responsive and motion behavior before implementation begins.
How do I install Design Handoff Spec in Claude Code?
Run `npx skills add getcrew44/crew44 --skill design-handoff -a claude-code`. Or copy the skill folder (daemon/internal/presets/defaultcrew/skills/designer/design-handoff in getcrew44/crew44) into .claude/skills/design-handoff in your project. Claude Code loads it when a task matches its description.
How do I install Design Handoff Spec in Codex?
Run `npx skills add getcrew44/crew44 --skill design-handoff -a codex`. Or copy the skill folder (daemon/internal/presets/defaultcrew/skills/designer/design-handoff in getcrew44/crew44) into .agents/skills/design-handoff in your project. Codex loads it when a task matches its description.
Can I use Design Handoff Spec 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 getcrew44/crew44 --skill design-handoff -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/design-handoff, .gemini/skills/design-handoff, .github/skills/design-handoff and .opencode/skills/design-handoff in your project.
What does Design Handoff Spec need to run?
SKILL.md names no scripts, command-line tools or credentials: Design Handoff Spec is instructions for the agent only.
Does Design Handoff Spec 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 Design Handoff Spec 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 Design Handoff Spec use?
Design Handoff Spec 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 Design Handoff Spec use?
About 680 tokens (SKILL.md is roughly 2.7k 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 Design Handoff Spec?
Skills that share tags, products or a category with Design Handoff Spec: Material Design 3 UI/UX Guide (skydashnet/material-design-3-ui-skill, 130 stars), UI Design System (try-works/role-model, 118 stars), Interface Kit (JuliusBrussee/skills, 161 stars) and Stitch to React and Vite Dashboard (google-labs-code/stitch-skills, 8.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Design Handoff Spec?
getcrew44 (a GitHub organization) maintains it in getcrew44/crew44, which has 356 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on June 11, 2026.
Source: getcrew44/crew44 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.