research-component

To research UI component variants, you define the component scope and fetch UI library pages to extract variant axes, values, sub-parts, interactive states, and accessibility patterns. This process generates a classified research document for cross-library observations.

Documenting interactive states and accessibility patterns for a UI recipe involves fetching target UI library pages and extracting their structural metadata. The findings are classified and written into a structured markdown file to ground design decisions.

You can extract component design patterns from Nuxt UI, Shadcn, Radix, Chakra, and Mantine. The research process fetches these library pages to gather variant axes, sub-parts, and accessibility patterns for the specified UI component.

You start defining UI component research scope by providing the component name, type, multi-part status, color pattern, and target HTML element. These parameters establish the boundaries for extracting variant axes and accessibility patterns.

If UI library URLs are not provided during component research, the process flags gaps in the generated findings document. This ensures traceability and highlights missing work scope for the UI recipe research.

Yes, UI recipe research supports multi-part components by explicitly asking for multi-part status during scope definition. This allows the extraction of sub-parts and interactive states across fetched UI library pages.