run-ui-registry-variations

Manual workflow for UI work that must start from approved component registries instead of hand-rolled interface code. The skill hard-gates registry access, then builds three real variations for the user to compare.

When to use

• /run-ui-registry-variations <UI request>
• The user explicitly says run-ui-registry-variations.
• The user asks for three UI options using shadcnblocks, Aceternity, or the Darkmatter shadcn registry.
• The user wants a one-off UI, new no-design-system project surface, or darkmatter.io surface and wants registry-backed options.

When NOT to use

• The user only asks which registry to use. Answer directly or use ui-ux-pro-max.
• The project is a flagship app with its own design system and the user did not explicitly invoke this skill.
• The task is backend, infra, copywriting, or non-visual.
• The user asks for one final implementation only and does not want alternatives.

Contract