Component
A Component is a reusable part of an interface with clear structure, behavior, states, and limits.
Another example
One ProductCard component shows every product with the same image and action rules.
Main parts
- 01Foundation or token
- 02Applied component
- 03Visible state and rule
Use it when
Use one when a pattern or behavior repeats and should have one trusted source.
Do not use it when
Never turn every plain wrapper into a component if it has no meaning or reuse.
Name used in code
<Component /> Before you ship
Check content order, shared design values, component consistency, contrast, zoom, and layout changes by screen size. Verify every theme, language, and state. If there is motion, offer an equal reduced-motion experience.
Outcome: Use or define Component to make the visual experience clear and easy to use. User context: One ProductCard component shows every product with the same image and action rules. Design concept to apply: Component. Why it fits: Use one when a pattern or behavior repeats and should have one trusted source. Do not use it when: Never turn every plain wrapper into a component if it has no meaning or reuse. Design requirements: Set the content order, shared design values, and reusable components. Define how the layout changes by screen size and state. Keep useful design choices separate from decoration. Inclusion and resilience: Check contrast, zoom, languages, themes, and reduced motion when needed. Do not use color or effects as the only way to show meaning. Acceptance criteria: The design stays clear on phones and desktops, at zoom, in every theme, and in all supported languages. Interactive states stay clear and consistent. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Brand limits, amount of content, supported themes and languages, target devices, and design-system rules.
Check this request
Review the current use of Component. Definition: A Component is a reusable part of an interface with clear structure, behavior, states, and limits. Release checks: Check content order, shared design values, component consistency, contrast, zoom, and layout changes by screen size. Verify every theme, language, and state. If there is motion, offer an equal reduced-motion experience. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.