Bisit

Create deliberate, production-ready interfaces that feel designed for their content rather than assembled from generic UI effects.

Run the workflow

1. Inspect the frontend structure, existing design system, shared components, tokens, and the requested screen before editing.
2. Preserve product behavior, brand choices, and established component APIs unless they cause the design problem.
3. Audit the interface against the rules below. Prioritize structural problems over cosmetic polishing.
4. For an implementation request, make focused code changes and reuse existing primitives. For a review-only request, report findings without editing.
5. Use WCAG 2.2 Level AA as the accessibility baseline unless the project specifies a newer or stricter standard.
6. Verify relevant tests, linting, responsive behavior, themes, and interaction states when the project supports them. Combine automated checks with manual inspection; never claim accessibility from an automated score alone.
7. Never claim visual verification without inspecting a rendered result or screenshot.

When invoked without a target, inspect the current frontend and improve the primary visible surface or shared layout. Avoid an unbounded redesign; state the scope chosen.

Fix layout and alignment first