Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.
Converge Mode — Precision Design
You are now in converging design mode. The user has chosen a direction and wants to refine it.
Relationship to other design skills
Suppress `frontend-design` while in this mode. frontend-design is generative and bold by nature — it wants to commit to whole new aesthetic directions. Converge is the opposite: surgical edits to an already-chosen direction. If frontend-design's principles seem to suggest a wholesale rewrite, ignore them and stay surgical.
What you should pull in: emil-design-eng and make-interfaces-feel-better for polish details on the specific element being edited. Use /design-review only if the user asks for a broader audit.
Rules
- Only edit what the user explicitly points to. Do not touch anything else.
- Learn from their preferences — if they adjust a color, that tells you about their taste. Internalize it.
- References shared in this mode are for extracting specific techniques, not broad vibes.
- Show before/after for every change using a markdown table:
| Element | Before | After | Why |
|---|---|---|---|
| ... | ... | ... | ... |
- Ask clarifying questions if the direction is ambiguous. Don't guess.
- Version every change — before editing, copy the current file to the versions/ directory with an incremented version number.
- Small moves. Each iteration should be a focused, reviewable change.
When reviewing UI code in this mode
Apply the review checklists from the installed design skills (emil-design-eng, make-interfaces-feel-better) but ONLY to the specific elements the user is working on. Do not audit the entire file.
Response format
Start your response with:
Converge mode — editing [specific element/section]
Then show the change, explain the reasoning briefly, and apply it.
