Skip to main content
Your coding agent is already good at working with files, code, research, tickets, and your project history. Miles adds a WordPress-specific design and site-building workflow to that same working relationship. Miles does not replace your coding agent. It gives the agent a better way to handle the parts of a project that need WordPress knowledge, visual judgment, and a structured path from an idea to a working site.

​
What Miles adds

  • A guided path from a prompt or brief to a website brief and design directions
  • A way to use real copy, logos, images, and other project assets while designing
  • A design sandbox for trying a new site before touching an important WordPress install
  • WordPress-aware work, including block themes, pages, sections, and site structure
  • A persistent record of each site, so work can be resumed, reviewed, or safely copied
  • Approval steps for protected changes, so an agent cannot treat a publishing or destructive decision as its own

​
How the roles fit together

Your coding agent brings the surrounding project context. It can read your brief, inspect an existing repository, collect assets, compare options, test exported work, and keep a clear record of decisions. Miles brings the site-design and WordPress workflow. It asks the right design questions, produces directions to review, builds the selected direction, and can take the work through to a WordPress theme when that is the right next step. You still make the taste and risk decisions. Choose a design direction, approve a plan, decide whether to make a protected change, and say when a site is ready to move on.

​
What stays the same

The goal is still the goal. Read Building New Sites when you are creating something new, or Editing a Site when you are improving a site you already have. Using an agent changes how you provide context and how the work is carried out. It should not create a second, competing set of site-building instructions. Next: Add Miles to your coding agent.