Skip to content

Dev inspector

The inspector is a small floating panel that appears in development. It lets you try theme changes on the real app and shows where the page breaks the design system. It also feeds the same findings to your AI agent.

Turn it on

Nothing to do: ThemeProvider renders it whenever NODE_ENV is not production. Pass devTools={false} to hide it, or render it yourself to change its props:

import { ShavinDevInspector, ThemeProvider } from "@shavin/ui";

<ThemeProvider devTools={false}>
  {children}
  <ShavinDevInspector position="bottom-left" />
</ThemeProvider>

Tabs

The WiseOwl finance dashboard with the Shavin Dev Inspector open on the DS Audit tab, the WiseOwl logo in the sidebar, four violations listed and the hand-written budget alert outlined in dashed red.

The inspector over an example app (the WiseOwl finance dashboard) on the DS Audit tab: the contrast check, the violation count with Re-scan, the highlight toggle, and the list of problems. The hand-written budget alert is outlined on the page.

ThemeTry brand, gray, radius, scaling, panel and fonts on the live app, then copy the ThemeProvider props.
DS AuditLists token problems on the current page: raw colours, off-token radius, low contrast. Click one to jump to it.
MCPBridge connection status and the MCP tools your agent can use with this page.
StreamThe events passing between the page and the bridge, for debugging.

Props

PropWhat it does
positionStarting corner: bottom-right (default), bottom-left, top-left or top-right. You can drag it; it snaps to a corner.
forceShowRender in production too. Off by default.
bridgePortBridge port, if you changed it. Also read from NEXT_PUBLIC_SHAVIN_BRIDGE_PORT or VITE_SHAVIN_BRIDGE_PORT.

How your agent sees the page

The inspector sends each audit to the bridge, a local server on port 7036 that starts with your dev server (see MCP setup). Your agent reads it with three tools:

get_live_auditThe current problems on each open page.
trigger_live_rescanAsks open pages to audit again after a change.
wait_for_live_cleanWaits up to a few seconds for the problem count to reach zero, then returns what is left.

A clean audit means the page uses the tokens correctly. It does not tell you the page looks right, so still look at it yourself.

Configure Theme
Theme
Brand Color
Custom
Gray Family
Appearance
Radius
Scaling
Panel Style
Heading Font
Body Font