Skip to main content
Improve my app runs a structured quality pass without requiring you to write a prompt. Choose an agent and Zite inspects the current app, verifies issues before changing the code, and makes focused improvements. The agents do not need to find a problem. If the app already passes a check, a zero-finding review is a valid result.
Improve my app uses the AI agent and consumes credits. The number of credits used depends on the size and complexity of the app.

​
Start an improvement pass

  1. Open the app you want to improve.
  2. Click the + button beside the prompt box.
  3. Select Improve my app.
  4. Choose Review agent, Design agent, or Accessibility agent.
Improve my app menu with Review agent, Design agent, and Accessibility agent

​
Review agent

Review agent reads the app’s code and checks each concern before making a change. It focuses on problems that can make a generated app feel incomplete or fail in normal use, including:
  • Buttons, links, tabs, and navigation that do not work
  • Filters, forms, endpoints, or integrations wired incorrectly
  • Missing loading and empty states
  • Authentication logic that does not match the app’s access mode
  • Components that bypass the shared Zite design system
  • Placeholder content, unclear actions, and obvious visual inconsistencies
The review stays focused on evidenced problems. It does not perform speculative rewrites or change working code simply for style, naming, file organization, or test coverage.
Use Review agent after building a feature or before publishing. It is especially useful when the app works at first glance but you want a systematic check of the underlying implementation.

​
Design agent

Design agent explores the running app like a user. It captures the screens it reviews and reads the code when needed to confirm how the interface is implemented. The pass looks for:
  • Inconsistent colors or one-off values instead of the app’s theme tokens
  • Uneven spacing, sizing, alignment, and visual hierarchy
  • Overflowing text, badges, tabs, cards, tables, and lists
  • Inconsistent controls that should use shared components
  • Missing or unresponsive loading states
  • UI patterns that feel unfinished or behave inconsistently across screens
When exploration is complete, Zite shows Design review ready. Expand Reviewed screens to check which screens were captured, then click Improve design to apply the design pass.
Design review ready panel showing reviewed screens and the Improve design button
Design agent works with the app’s existing direction. It improves theme usage, spacing, consistency, components, and states rather than redesigning the product without evidence.
Make sure the main pages and core interactions exist before running Design agent. It is best at polishing a working app rather than defining an unfinished product.

​
Accessibility agent

Accessibility agent reviews the app against WCAG 2.1 AA and fixes issues it can verify in the code. It checks details that are easy to miss during a visual review:
  • Text contrast across the surfaces the app actually renders
  • Badges, status pills, placeholders, and disabled states
  • Focus-ring visibility when navigating with a keyboard
  • Keyboard access for interactive controls
  • Hand-built buttons, dropdowns, dialogs, tables, and other elements that lack native semantics
The agent prefers the shared components in @project/components/ui, which already provide accessible behavior through shadcn and Radix primitives. It avoids adding redundant ARIA when native HTML or an existing primitive already carries the correct semantics. Accessibility changes should preserve the design. For example, the agent raises contrast by adjusting the relevant theme token rather than restyling the entire screen.

​
After the pass

Review the changes in chat and test the affected screens before publishing. Check the main user flow, any updated forms or integrations, and responsive behavior. You can also open History to inspect the resulting code changes or return to an earlier version. If you only need to change one specific element, use Selective Edits instead. If you want to guide a broader visual direction with a brand, theme, website, or screenshot, see Design tools.

Related topics

Design toolsSelective EditsRestore an older versionTroubleshooting
Last modified on August 17, 2026