What problem does it solve?
It prevents common frontend UX failures in Ethereum dApps that cause users to double-submit transactions, misread addresses and amounts, get confused by pending/approval states, and encounter opaque errors or unreliable RPC behavior.
Core Features & Use Cases
- Onchain button lifecycle: Forces a deterministic per-button pending state with immediate disable, clear action labels, and guaranteed unlock via finally blocks.
- Approval-to-action correctness: Implements a four-state flow (connect, switch network, approve, execute) using fresh onchain reads to avoid stale allowance and mid-flight re-enablement.
- Address and amount usability: Requires explorer linking, copy support, and validation/normalization, plus USD context and human-readable decimal conversions for token/ETH values.
- Operational robustness: Sets guidance for RPC reliability/polling hygiene, contract error translation to human-readable messages, and theme semantics that preserve light/dark coherence.
- Release readiness: Mandates pre-publish metadata checks so social previews and branding are accurate before production.
Quick Start
Use the frontend-ux skill to audit or implement your Ethereum dApp UI so every onchain button, approval flow, address display/input, token value display, RPC polling, error handling, theming, and production metadata follow the required UX rules.
