Solution · Add dark mode
Add dark mode across your app, delivered as a reviewed PR
Connect your GitHub repo and ask for dark mode. The agent indexes the code, makes the change in a sandbox, verifies it builds, and opens a pull request for you to review.
The challenge
Why this is usually hard
Dark mode is a cross-cutting change: it touches theme tokens, every component that hard-codes a colour, and the toggle plumbing that persists a preference. Doing it by hand means hunting down stray colours across the codebase and hoping you did not miss a corner. The risk is a half-themed UI and a noisy diff that is hard to review.
How it works
From prompt to shipped
- 1
Connect your repo
$ connect repoPoint the agent at your GitHub repository. Nothing is changed on your default branch — work happens against a clone.
- 2
Describe the change
$ add dark mode across the appAsk for dark mode across the app, including a toggle that remembers the user choice. The agent indexes the code semantically and by symbol to find every place colour is set.
- 3
Edit in a sandbox
The agent introduces theme tokens, replaces hard-coded colours, and adds the toggle inside an isolated sandbox clone — never your real repo.
- 4
Verify it holds
verifyIt runs typecheck, tests and the build to confirm the app still compiles and nothing regressed before the change is offered.
- 5
Open a pull request
$ open prYou get a reviewed PR with a clear summary of what changed. The repo only updates if and when you merge it.
Why code-anything
What you get out of the box
Nothing gets missed
Semantic and symbol-aware indexing finds every component and stray colour, so the whole app gets themed — not just the obvious screens.
Verified before you see it
Typecheck, tests and build all run in the sandbox first, so the PR arrives already known to compile.
Reviewed, not auto-merged
The repo changes only through a pull request you review and merge. No direct writes to your branches.
Your code stays isolated
Edits happen in a sandbox clone, so your real repository is untouched until the PR is merged on your terms.
In practice
What it looks like
A short, honest version of the flow: connect the repo, describe the change, and the agent verifies before opening a PR.
$ connect repo acme/web-app
$ add dark mode across the app, with a toggle that persists
✓ indexed 142 files (semantic + symbol)
✓ added theme tokens, replaced hard-coded colors
✓ added a persisted theme toggle
✓ typecheck · tests · build all pass
→ opened PR #318 "Add dark mode"What you get
- A dark theme applied consistently across the app
- A theme toggle that remembers the user preference
- A pull request that passes typecheck, tests and build
- A reviewable diff — your repo only changes when you merge
FAQ
Common questions
Build add dark mode in minutes, not weeks.
Start free. Managed database, auth, email and payments are wired in — and every workspace is monitored after you ship.