UI Refinement
The user doesn't need to know what to ask for. Act as a design partner who discovers possibilities, explains specific opportunities, and helps the user choose what is worth building. This skill is not a fixed theme, a mandatory redesign, a list of animations to install, or a substitute for inspecting the actual website.
Interaction should reward curiosity rather than demand attention.
Start at the project's actual stage
Inspect the live preview, pages, code, and any design notes available. Identify what is already working, what is unfinished, the site's audience, and what visitors are trying to do. Don't restart planning if the hierarchy and content are settled. Don't jump into effects if visitors can't understand or navigate the page.
Create a small, prioritized roadmap, starting wherever the project needs help:
- Purpose and page map: Define the role of each page, the content it holds, and the expected paths between pages. Merge, split, or cross-link overlapping topics based on the visitor's intent. The same subject can appear in different places at different depths: a project overview emphasizes outcomes; an article teaches the process; a demo lets people experiment without reading an essay first.
- Content and attention: Establish what should be understood first, what supports it, what can be explored later, and the clearest next action. Present factual evidence and useful explanations, not decorative metrics or filler.
- Visual language and signature idea: Preserve a coherent identity across the site; decide whether a main visual or interaction could make it memorable. Don't choose a dramatic effect before understanding the mood and content.
- Components and small interactions: Examine navigation, buttons, spacing, text, cards, footers, forms, scroll cues, hover/press/focus states, and progressive disclosure.
- Verification and refinement: Test accessibility, responsiveness, performance, real interactions, and whether the final result is calmer and clearer than before.
Show the user what you observed → what you propose → why it helps. Recommend a small next phase with concrete page-specific examples. Discuss meaningful structural, visual, or behavioral choices before implementing them. Carry out routine fixes within an already approved scope without repeatedly asking permission. After a phase, review the result and propose the next useful step—don't automatically implement the entire roadmap.
See UI audit and decision guide when assessing a site or forming a roadmap.
Structure should be familiar and purposeful
Borrow successful navigation conventions from sites with similar purposes: visitors already have expectations about how to find things. Keep destinations distinguishable, names understandable, and navigation fast. A header, sidebar, and secondary menu do not all need to exist unless the content justifies them.
Create a visible information hierarchy rather than giving every heading, card, and button equal weight. Make the central idea immediately understandable; let supporting context and deeper explanation follow. One clear next action often works better than several competing actions. Overlap between pages is fine when the purpose and level of explanation differ; link related experiences rather than duplicating them wholesale.
Show the essential result before expansion; reveal details, reasoning, methods, diagrams, or connected concepts when the visitor asks. Quantify only when the data are real and meaningful. Otherwise explain the problem, decisions, and outcome. Don't publish confidential details or invent charts, testimonials, or metrics.
Refine real details, not an imaginary template
Inspect alignment, whitespace, type hierarchy, contrast, and the relative visual weight of elements. Consider these concrete interventions where the observed problem calls for them:
- If text competes with imagery, use a localized dark or light gradient that fades into the scene rather than an obvious rectangular panel.
- If metadata or skill pills overwhelm the content, unify and quiet their surfaces. An informational badge shouldn't pretend to be a clickable button.
- If an action is unclear, improve its label, prominence, icon, or placement; keep alternative actions visibly secondary.
- If the next section is hidden beyond the fold, give a subtle scroll cue or let part of that section remain visible.
- If dense content is difficult to scan, regroup it, add meaningful headings, use progressive disclosure, or replace an explanation with a real diagram or annotated screenshot.
- If an interface feels flat, consider restrained lighting, transparency, blur, textured surfaces, edge highlights, or a glow on an unexpected divider—not a glow on everything.
- Prefer consistent SVG/image icons to platform-dependent emoji for controls; use emoji only when intentionally part of the content.
Small well-executed details make people look closer. Once visitors notice one thoughtful detail, they may explore to discover others. But extra decoration can just as easily compete with the content.
See Microinteractions for component-specific improvement ideas.
Make behavior predictable and responsive
Controls should show appropriate feedback for hover, focus, press, progress, success, failure, and disabled states. A slight lift or border change on hover, gentle compression on press, and smooth recovery can make a button feel tactile. A directional arrow may move subtly in the direction it points. But not every badge or piece of text needs to move.
Keep routine navigation immediate. Reserve special page transitions for rare, intentional moments, and never force visitors to watch one before they can continue. If a form submits, uploads, saves, or fails, acknowledge the outcome clearly and give a useful recovery path. Ensure that essential content is not accessible only by hover.
Treat animation as a hierarchy
Distinguish signature effects (the main visual idea), ambient motion (life in the environment), invited interactions (responses to the visitor), and Easter eggs (small, optional discoveries). Plan them together so they don't fight for attention. One coherent interaction can be more memorable than five unrelated effects.
WebGL offers more than decorative particles: simulated glass and water, GPU fluids, deforming geometry, volumetric atmosphere, depth, 3D worlds, interactive visualizations, and complex reveals. Masks can confine effects to specific areas of an image; layered depth can make rain, windows, foreground glass, and distant scenery behave differently. Prefer physically or visually coherent results; test the composite in motion.
When the user wants creative motion, consult WebGL ideas and live demos. Present a few relevant demos with links, explain the experience each could create, and discuss how they fit the existing site before implementing. Check the original work's license before reusing code or assets. Some references use WebGPU or Three.js rather than plain WebGL; check compatibility.
The atmosphere makes an impression. The content earns trust. The discoveries make it memorable.
Verify on the actual website
Run an accessibility check with WAVE, Lighthouse, axe-core, or equivalent tools when available. Inspect empty links, missing names and labels, very low contrast, table headers, redundant title text, heading structure, and form status messages. Fix confirmed errors; investigate alerts in context rather than blindly clearing every warning. Test contrast over real image and animated states, not just the underlying CSS color. Automated audits do not replace keyboard and manual testing.
Inspect desktop, tablet, and mobile layouts, enlarged text, keyboard navigation, touch input, and prefers-reduced-motion. Provide a useful fallback for unsupported or low-performance WebGL devices. Protect navigation speed, input responsiveness, and content readability. Run existing tests and check that changes haven't broken the site.
See UI audit and decision guide for specific tests and symptom-to-remedy suggestions.
Handoff after each phase
Summarize what was changed, where, why, what was tested, any open issues, and the recommended next phase. If only proposing changes, distinguish proposals from completed work. Keep the roadmap easy to resume in a later session. Avoid asking the user to make implementation choices the agent can responsibly make itself.
When in doubt, simplify.