Designer

Submergent for Designers

The distance between a design and the thing that ships is a hundred small inconsistencies: spacing that drifted two pixels, a transition easing wrong, a colour someone hardcoded instead of using the token. Finding them means reading code. Fixing them usually means writing a ticket and waiting. Submergent lets you do both yourself, in the actual codebase, and look at the result.

Coming soonSubmergent 1.0.0 · macOS 14+ · Apple Silicon · get notified when it ships
01

Audit the spacing and type you can feel is off

You can tell a screen is inconsistent before you can say why. The evidence is spread across a dozen components, and none of it is visible from the design file.

Ask for it like this› Audit the spacing and typography in this UI and point out inconsistencies, grouped by how bad they are.

A list of what actually differs, by file, with the values. You decide what is intentional and what drifted before anything gets changed.

02

Fix the motion instead of describing it

"Make it feel snappier" survives no handoff. The specifics — duration, easing, what animates and what does not — live in code, which is where the conversation should happen.

Ask for it like this› Review the animations in this UI and suggest more polished motion. Respect reduced-motion preferences.

Concrete changes to durations, easings, and which properties animate, applied to the components that render them.

03

Prototype the idea to see whether it works

Some ideas cannot be evaluated as a static frame. You need it on screen, responding, before you know whether it is right.

Ask for it like this› Prototype this idea as a throwaway component so I can look at it: a settings row that expands inline instead of opening a modal.

A working component you can open and click. Throwaway is the point — if it is wrong, delete the session’s work and try the other idea.

04

Look at the result, not the code

Reading a diff tells you what changed. It does not tell you whether it looks right, which is the only question you actually have.

Ask for it like this› Start the dev server and tell me the URL.

The Browser tab in the side panel opens the running app next to the conversation. It is available whether or not Developer Mode is on.

05

Find every place the design system got bypassed

A token nobody uses is worse than no token. The bypasses accumulate quietly, and each one is a place the next redesign will not reach.

Ask for it like this› Find every place that hardcodes a colour, radius, or spacing value instead of using a token. List them by file with the literal value.

The full list, which is usually longer than expected. Fix them in the same session, or hand the list to whoever owns those files.

06

Build the states everyone forgets

Empty, loading, and error states get designed last and built never. They are also the states users hit on their worst day.

Ask for it like this› Add empty, loading, and error states to this component, and show me how to see each one.

The states get built, plus a note on how to trigger each one so you can actually look at them.

Where it stops

What Submergent will not do.

Submergent works on the code that renders your design. It does not work on your design files. There is no Figma, Sketch, or design-tool integration — the only mockups it can see are files inside the workspace you opened, and the only running app it can see is one you point the Browser tab at.

Questions designers ask

Do I need to know how to code?

No, but you need to be comfortable describing what you want precisely and looking at the result. You never have to read a diff — those surfaces are hidden unless you turn on Developer Mode.

Where do my changes go?

Into the files in the folder you opened, on your Mac. Nothing is pushed anywhere. If the folder is a git repository, your team’s normal review process still applies.

Can it read my Figma file?

No. There is no design-tool integration in 1.0. If you export a frame or a spec into the workspace as a file, it can read that.

How do I look at what it built?

The Browser tab in the side panel is an embedded browser scoped to the workspace — point it at your dev server and it sits next to the conversation. It is available in both interface modes.

Other ways in
EngineerRefactors, flaky tests, and the coverage you inherited — with the diff to check.ProductFind out what shipped, what is half-built, and what a request would touch.Writer / ResearcherDocumentation that matches the code, in a folder that does not need git.

Ready when you are.

Coming soonSubmergent 1.0.0 · macOS 14+ · Apple Silicon · get notified when it ships