review-design

Review Svelte components for UI/UX quality by analyzing responsiveness, touch targets, logical CSS, theming, and accessibility against a comprehensive checklist and project design tokens. This automated review catches design inconsistencies and best practice violations before components reach production.

Auditing frontend design consistency before merging is best done by comparing git diff changes against master to identify new Svelte components, then checking them against existing patterns, design tokens, and UI/UX best practices to ensure a polished user experience.

Yes, this design review tool checks accessibility and responsiveness by analyzing Svelte components for touch target sizes, logical CSS properties, cross-browser compatibility, and adherence to project standards, ensuring components meet comprehensive UI/UX guidelines.

Enforce design token usage and theming in Svelte components by reading design token references during the review process and verifying that new components align with existing project patterns, typography, and theming standards to maintain visual consistency.

You can use this component audit for your existing Svelte project if you have design token references and a git workflow to compare branch changes against master, allowing the tool to evaluate new UI components against your specific project standards.

Limitations when reviewing cross-browser compatibility and dialogs include relying solely on static analysis of Svelte components and design tokens, meaning the review cannot catch runtime visual bugs or dynamic interaction issues that only appear during actual browser rendering.