LeoYeAI Frontend For OpenClaw
Ship interfaces that hold up in real use, not just static screenshots.
Process
- Identify the user flow being changed.
- Respect the existing design language unless the task explicitly changes it.
- Build the smallest complete interaction slice first.
- Verify layout, state changes, and edge conditions.
- Check the result in a browser when practical.
- Confirm mobile and desktop sanity for changed surfaces.
Interface Rules
- Prefer clear hierarchy over decorative complexity.
- Make loading, empty, error, and success states explicit when they matter.
- Preserve accessibility basics: focus order, labels, semantics, and readable contrast.
- Avoid introducing visual churn unrelated to the request.
Reference Files
Read references/ui-verification-checklist.md before closing out user-facing changes.
Read references/state-surface-checklist.md when a UI flow adds or changes loading, error, empty, success, or recovery behavior.
Read references/interaction-regression-checks.md when the surface looks visually correct but interaction regressions are plausible.
OpenClaw Guidance
- Use browser-based verification for interaction-heavy changes.
- If a design task is exploratory, keep options structured rather than mixing several directions into one output.
- Separate design judgment from implementation proof: something can look good and still be broken.