Coding is a small category with finished products

Coding has 7 entries in this directory, fewer than Productivity or Finance, but almost every one ends with something shipped: a website, a game, a tracker or a review workflow that runs every day. That makes this category a useful test of what Muse does when the finish line is not a reply but a working piece of software.

The entries split into two groups. Experienced developers use Muse Spark and Muse Code as part of a daily workflow. People with no coding background use Muse to build a complete site in a single sitting. Both groups appear in the list below, with links to their original posts.

Websites are the clearest starting point

Two entries are pure website builds. One person built a complete website using Muse Spark and its built in developer tools. Another, with no prior web experience, had Muse rebuild a church website in a day. If your question is whether Muse can handle web design, these two stories are the direct evidence in this directory: a full site, not a mockup, in both cases.

A practical way to copy them is to start with one page and a clear purpose, then review the result in a browser before asking for more pages. The multi-agent entry in this guide shows a developer doing that kind of checking himself, opening the project in a browser and clicking around to test it.

Games show the range, from a song to a VR title

One builder asked Muse for a side scrolling game inspired by a song it had composed, then an FPS variant with multiple levels and NPCs, then a 3D third person adventure game called Garden Quest with enemies and a boss, and assembled them into a retro website named Garden Signals. A second entry goes further: Meta WebXR tech lead Felix Zhang used Muse Code with the Immersive Web SDK to build HYPERFORM, a VR rhythm game with direct hand interactions, from prompt to publish.

The lesson is sequencing. Each game started as one playable idea and grew by adding levels, characters and features in later rounds, instead of asking for a finished studio title in a single prompt.

Developers use Muse as part of a loop, not a magic button

The most detailed workflow in this category comes from Alexandru. He talks to Muse to plan, gets the plan reviewed by Codex, implements with Muse Spark via OpenCode, then has Codex review again. Muse runs his projects locally, and he tests the result himself in a browser. A second developer, who runs PIXIPACE, an LLM tooling company, has used Muse Spark daily since April 9, 2026 for code review, research synthesis and light architectural planning on real internal tooling.

Notice the pattern: plan, review, build, review again. Muse speeds up each stage, but a human or a second model still checks the work. That is the honest version of coding with an agent, and it is the version the directory actually documents.

Start from one sentence, then inspect what it built

One entry began with a single sentence about a food tracker. Muse found its GitHub repo, mapped its hidden API, and the builder then built a full tracker on it and wrote up the whole process. Starting small works for research and reverse engineering too, as long as you read what the agent found before building on it.

Pick one small project from the list below, give Muse the outcome and the constraints in plain language, and keep a review step before anything goes live. If it works, submit your build to the directory so this guide can point to it next time it is updated.

The examples in this guide

Want more like these in your inbox? The weekly email below rounds up the five best new use cases. Or submit your own and help the directory grow.