Docs · Refine
Refine a component and compare variants
Name what feels off, make one judgeable change, and compare a distinct alternative without losing the working source.
5 min read
Outcome and prerequisites
The outcome is a stronger live component whose improvement is visible and whose useful structure still works. You can refine the selected component or ask Tenor for a sibling variant when comparison will make the decision clearer.
- Start from the strongest working version on the canvas.
- Know what already belongs and should not change.
- Choose one important difference you will be able to judge.
A dependable refinement loop
- 01
Select the source component
Choose the version with the best product structure and working behavior.
- 02
Protect what belongs
State the content, behavior, hierarchy, or visual language that should remain stable.
- 03
Name what feels off
Describe one visible outcome in plain language and explain why it matters.
- 04
Choose an edit or a variant
Refine in place for a correction. Ask for a distinct variant when two directions deserve comparison.
- 05
Compare the working results
Judge product clarity, interaction, and fit with the surrounding system before small visual polish.
- 06
Keep the stronger direction
Continue only from the version that best preserves the job and makes every part feel like it belongs.
Expected result
You should be able to explain why the selected version is stronger, not only that it looks different. Continue with the handoff guide when the component is ready to meet real application data and constraints.