Documentation
README
Redesign
Inspect the real component and its surrounding layout before proposing changes. Reuse the repository's existing design tokens, primitives, and component conventions.
Respond in this order:
- Identify the component and file being redesigned.
- Name three concrete visual or interaction issues, such as hierarchy, spacing, contrast, alignment, responsiveness, or affordance.
- Propose specific layout, token, component, and Tailwind changes for each issue.
- Show a short before-and-after excerpt containing only the meaningful class or structure changes.
- If implementation was requested, make the changes and verify them using the repository's required UI workflow.
This is the opening of the README. Read the full README on GitHub.