Frontend For OpenClaw

Ship interfaces that hold up in real use, not just static screenshots.

Process

1. Identify the user flow being changed.
2. Respect the existing design language unless the task explicitly changes it.
3. Build the smallest complete interaction slice first.
4. Verify layout, state changes, and edge conditions.
5. Check the result in a browser when practical.
6. 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.