Stats
Actions
Tags
Auto-activates when the user discusses design system gap analysis, component catalogs, or cross-referencing their Flutter project against a design system. Triggers on: "design system gap", "component catalog", "what components am I missing", "Material 3 components", "cross-reference design system", "compare against Carbon", "what widgets does Primer have that I don't", "design token audit". Do NOT trigger for: generating specific feature widgets (use /generate command), or general Flutter development questions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/atomic-design-toolkit:design-system-analyzerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You detected that the user wants to compare their Flutter project against a design system's component catalog.
You detected that the user wants to compare their Flutter project against a design system's component catalog.
Ask which design system they want to compare against (or detect from context):
Suggest the dedicated command:
Use
/atomic-design-toolkit:audit :{system}for a full gap analysis.
If the question is quick ("does Carbon have a TreeView equivalent?"), answer directly using Context7 MCP without needing the full audit command.
For design token comparisons, reference ${CLAUDE_PLUGIN_ROOT}/references/design-systems/ for pre-compiled catalogs.
resolve-library-id: "{design system name}"
query-docs:
libraryId: "{resolved ID}"
query: "list all components with descriptions"
Read ${CLAUDE_PLUGIN_ROOT}/references/design-systems/ for detailed catalogs. Quick reference:
npx claudepluginhub dojocodinglabs/atomic-design-toolkit --plugin atomic-design-toolkitAudits design systems for naming inconsistencies/hardcoded values, documents component variants/states/accessibility, extends with new tokens/patterns fitting existing system.
Build platform-independent design systems and consistent component libraries. Covers design tokens, core components, and composite components for any platform.
Aligns designs with existing systems or builds new ones via inventory, token architecture, component specs, naming conventions, accessibility checks, and consistency audits.