How It Works

Sonic is built on one conviction: the why behind the design comes before the design. Most AI site builders start from a template and fill it with content. Sonic starts from the brand and lets every downstream decision flow from it.

The mental model

Brand  →  Identity  →  Theme  →  One perfect page  →  Hundreds of pages  →  Quality gates

Read that left to right. You never jump ahead. A site bulk-generated before the brand and the template are locked looks generic, and generic does not rank or convert.

Brand first, not content first

This is the agency way, encoded into an agent:

1. Discover the brand before drawing anything. Voice, tone, positioning, target customer, brand pillars. This becomes the source of truth for every copy and design choice downstream. (Skill: brand-philosophy, output BRAND-BRIEF.md.)
2. Design the identity from that brief. Color palette, typography, image style, mood board. Sonic decides based on the brief rather than asking "what colors do you want," then checks if it lands. (Skill: visual-identity, output STYLE-GUIDE.md.)
3. Build the theme and homepage referencing both files. Then it perfects that one page.
4. Only then scale. One signed-off template page becomes the bar for the next 99.

Two artifacts carry the brand through the entire build: BRAND-BRIEF.md and STYLE-GUIDE.md. Every later skill reads them. That is how 200 pages stay on-brand instead of drifting.

Sign-offs gate every stage

The standard build (/sonic-build) pauses for your approval at the end of each stage. You review the brand brief before any design happens. You review the homepage before 100 pages are built. If you want tweaks, they happen at the cheapest possible moment, before the change has to propagate across the whole site.

Autopilot can run these gates as self-reviews instead (full-auto mode), but the brand-philosophy discussion still happens. The order is never skipped, only the approval pauses.

Sandbox first

You do not need a live host to start. Sonic can spin up an instant local WordPress site (wrapping the WordPress Playground CLI as a background process) and build against that. The operator never sees the word "Playground," it is just a Sonic sandbox. When the build looks right, you deploy fresh to a real host. Autopilot is sandbox-only by design and never deploys live on its own.

The Sonic voice

Sonic has a deliberate personality, blue-hedgehog speed energy, and it shapes how the agent behaves:

• Speed-first. Get to the point, ship, iterate.
• Honest. It tells you the truth even when it is not what you want to hear, and it is direct about scope. If you ask for something out of scope, it says so and offers the closest realistic option.
• Practical. Real working output over abstract theory. It does the work: builds the file, writes the code, ships the page, generates the real image instead of suggesting a placeholder.
• Quality plus speed. Most tools pick one. Sonic is built to deliver both.

What it is deliberately not good at

Sonic stays narrow on purpose. It is not the tool for:

• General coding (use a general agent).
• Non-WordPress platforms like Webflow or Framer (planned for v2).
• Legal or financial advice.

Narrow scope is the price of speed and quality at scale.

Next: walk the full Build Pipeline stage by stage.