moodspec

For solo devs

Your seventh side project shouldn't look like a stranger built it.

You build alone and fast, mostly with an agent. The code carries over between projects. Your taste doesn't — you retype it, badly, at the start of every repo. moodspec keeps it in one place your agent can read.

See pricing

What goes wrong

Nothing is written down, so everything starts over.

  • The blank-repo tax

    Every new project starts with twenty minutes of "use a warm neutral palette, tight radius, no gradients" — typed slightly differently than last time.

  • Client work bleeds together

    Three clients in one head. The agent picks up whatever brand was in the last chat and quietly puts it in the wrong invoice screen.

  • Changing your mind is expensive

    You drop the serif for a grotesk. Now it's a find-and-replace across four repos, plus the emails and the landing page.

How it goes instead

One week, as it actually goes.

Nothing here needs a teammate, a ticket or a design system meeting.

  1. Fri 21:40

    New repo, no style brief

    You paste the MCP endpoint into the project config once, then prompt "build the marketing page." You don't describe the type, the palette or the radius — you never do again.

    cursor · ~/side-seven

    > build the marketing page

    ↳ reading moodspec canvas "my taste" · 31 assets

    What you get: Archivo over Newsreader, orange on buttons only, radius 9, no gradient hero — the same decisions as the last three projects.

  2. Tue 09:12

    Client work, kept in its own lane

    Two clients this week. One canvas each, one endpoint each. The dental repo can only see the dental brand, so the agent can't quietly reuse the fintech blue you were staring at yesterday.

    Northgate Dental/c/northgateLedgerly/c/ledgerly

    What you get: when the engagement ends you hand over the canvas — a real deliverable, not a chat log.

  3. Sun 14:03

    You change your mind about the serif

    One edit on the canvas, saved. The previous version stays in history for the inevitable Sunday-night regret. Then: "re-run the marketing pages against the current canvas."

    What you get: four projects updated from one decision, instead of four find-and-replaces you'd never finish.

Start on Free. Go Pro when you want a second canvas.

One canvas is free forever with no account. Pro is $10 a month for unlimited canvases, cloud backup and an MCP endpoint for each.

What solo devs ask

Do I have to sign in to try it?
No. One canvas works with no account at all — it lives in this browser. You sign in when you want it backed up or connected to an agent over MCP.
I already keep a CLAUDE.md with style rules. Why bother?
Because it only lives in that repo, and it's text. A canvas holds actual fonts, hex values, marks and saved references, is versioned, and one edit reaches every project you connected.
What if a client wants the whole thing when we're done?
Hand over the canvas. It reads as a spec a human can review and as an endpoint their own agents can use.