Design on your real app,
not a picture of it.

Hyperpowers Studio puts your running app on a canvas. Click anything, ask Claude for a change, and keep the version you like.

Uses your own Claude Code sign-in. No API keys. Nothing changes in your code until you click Apply.

Open the app you already have.

Pick your project's folder. Your real app runs on the canvas from your own code, signed in, with real data.

Click anything. Say what you want.

The element you select goes with your message, so “make this yellow” means that button. Claude edits the code and you watch the page change.

Try it four ways. Keep one.

Each version is a full copy of your app, running side by side. Apply puts the one you like into your code.

Works with

Your code changes only when you say so.

Claude never works in your checkout. Every change lands in a version, and you decide what goes into your code.

Every version is its own copy.

A version is a copy of your code with its own dev server. Claude edits there. Your working folder stays exactly as it was until you click Apply.

src/App.jsx+3−1
src/styles.css+6−0
ApplyUndoSave as branch

See what changed, and take it back.

Changes lists the files each version touched. Every request can be undone on its own, and Commit happens only on your click. Hyperpowers Studio never deploys.

Bmake this yellow1 file
Bmore room around the card2 files
Dshow me 4 options for it1 file

Change styles by hand, too.

Select an element and edit padding, colour, type and radius in the Properties panel. When your app has its own tokens, changes are saved by name.

Your account, your keys.

Hyperpowers Studio runs the Claude Code on your Mac with your own sign-in. It has no key of its own, and it leaves your API keys alone unless you turn that on.

Claude Code · signed inEnv file values are never shown to Claude

What you get here that a mockup doesn't give you.

Most design changes start in a drawing of the app and are rebuilt in code later. This is what changes when the canvas is the app.

TopicA mockupHyperpowers Studio
What you look atA picture of a page, with sample content.The page itself, running from your code, signed in, with real data.
What a change isA new drawing someone rebuilds in code later.An edit to the code, shown live, that you can apply.
Comparing ideasArtboards side by side.Up to four running versions side by side, each one clickable.
When it's wrongRedraw it.Undo that one request, or delete the version.

Questions

What do I need?

A Mac with Apple silicon on macOS 12 or later, git, and Claude Code installed and signed in. Your app needs a dev server (the usual npm run dev).

Does it change my code?

Not until you click Apply. Claude works in a version, which is a separate copy of your code with its own dev server. Apply puts that version's changes into your code, and Commit is a separate click.

Which apps does it work with?

It is tested on Next.js 14 and 16, on Vite with React and Tailwind, and on a plain static page. Other apps with a dev server usually open, but those are the ones tested end to end.

What does it cost to use Claude here?

Hyperpowers Studio has no key of its own. It runs the Claude Code on your Mac with its sign-in, so with a Claude subscription it uses that subscription.

Where does my code go?

It stays on your Mac. Requests go to Claude through your own Claude Code, the same as when you use it in a terminal. Values in your env files are never shown to Claude.

How is this related to Shapi for VS Code?

Same idea, different size. Shapi for VS Code makes icons that match your app's style. Hyperpowers Studio works on whole pages of your running app.

Open your app and start changing it.

Apple silicon, macOS 12 or later. Needs git and Claude Code.