Yes for the core visual workflow. You can create Components, arrange elements, set design properties, define responsive screens and variants, animate properties, connect supported events, and use Preview from the editor. Code knowledge becomes useful when you integrate generated output, author a Code Component, or debug an application boundary.
You can build visual interface Components and Pages with responsive design, states, variants, animation, logic, and supported data connections. Mockups provide a related visual workspace, but they do not export production code. Some data, authentication, publishing, and media surfaces have explicit limitations, so check Current limitations before choosing a production workflow.
A Component is a reusable visual unit and the main exported component contract. A Page uses the same editor model for a route-level result. A Mockup is an exploratory visual file with no generated code output.
Compare their exact file behavior.
Properties are caller-supplied inputs, states are values owned by a Component instance, events expose behavior to the caller, and variants select named style combinations. They are related, but they are not interchangeable: a state-driven style is stored as a style variant associated with a state value, while a public Component variant is selected by the consumer.
Yes. Responsive screens store different style values for the same Component hierarchy and export responsive CSS through container queries. They are not separate copies of the element tree.
Yes. Component timelines keyframe supported style and transform properties on actual elements, and the exporter carries supported timeline data into the generated runtime. Timeline behavior has important trigger, target, and responsive limits, so verify it in Preview and in the exported consumer.
Yes. Project design-system files centralize themes, colors, fonts, spacing, radius, images, audio, and video registrations. Coverage differs by token type: for example, registered video has no native canvas Video element, and Font Weights is currently a limited compatibility surface.
Yes. Give the agent one project, file, target, constraint, and proof requirement, then review the same content in the editor. MCP changes project data; it does not need to reproduce your selected tab, zoom, open panel, or other session navigation.
Check the element hierarchy, each intended responsive screen and variant, interactive states, timeline behavior, Preview, diagnostics, and the generated result if it will ship. A screenshot proves appearance at one state; it does not prove interaction, responsive behavior, accessibility, or consumer compatibility.