From design
Research user needs, existing patterns, and accessibility requirements before designing a component
How this skill is triggered — by the user, by Claude, or both
Slash command
/design:empathizeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Research the problem space for "$ARGUMENTS" before any design work begins. Gather user needs, existing patterns, accessibility requirements, and contextual constraints.
Research the problem space for "$ARGUMENTS" before any design work begins. Gather user needs, existing patterns, accessibility requirements, and contextual constraints.
None — this is the first phase.
Read the design system via MCP tools:
figma_get_design_system to fetch existing components, tokens, and stylesfigma_get_components to list all published componentsInspect existing components (if found):
figma_get_component and figma_get_component_for_dev for related componentsfigma_export_image to get visual referencesReview accessibility requirements:
plugins/design/shared/wcag-criteria.md for applicable WCAG criteriafigma_a11y_contrast_check on any existing color pairs used in related componentsSynthesize findings into a research brief covering:
Write the artifact to .metapowers/design/$ARGUMENTS/01-empathize.md
The research brief written to .metapowers/design/$ARGUMENTS/01-empathize.md. Present a summary to the user highlighting:
npx claudepluginhub bromso/metapowers --plugin designCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.