Customizing your Summit theme
The Prompt Builder turns a few answers into a precise brief for your AI assistant — already loaded with your theme's architecture and the exact files each change touches — so you can make it your own without learning the codebase first.
Open the Prompt Builder →Why it helps
Your Summit theme is built so an AI assistant can reshape it — clean Astro + Tailwind
code, a single business.json config, and an llms.txt file that
maps the whole structure. The catch is that the AI has to be told to use all that. This
builder writes the prompt for you: it names your theme's conventions, points at the right
files for the change you picked, and adds the guardrails that keep the build green — the
difference between a vague request and one the AI can land in a single pass.
Step by step
Open your theme in an AI editor
Unzip your Summit theme and open the folder in an in-editor AI assistant like Claude Code or Cursor — one that can read and edit your files directly. That way it can read the theme’s llms.txt (the structure map) and edit the right files itself.
Build your prompt
Pick what you want to change and describe it. Each option tells the AI exactly which files that change lives in (business.json, global.css, a service page, and so on), so it doesn’t have to go hunting. The prompt builds itself as you type.
Copy and paste it in
Hit “Copy Prompt,” then paste it into your AI assistant pointed at the theme folder. The prompt already tells it to read llms.txt first and stay within the theme’s Astro + Tailwind conventions.
Review, then come back for more
A good prompt lands the change in one pass most of the time. Review the edits, run npm run build to confirm it’s clean, and tweak with a quick follow-up if needed.
What to expect back
A good assistant will usually restate its understanding, ask anything that's unclear, then explain its approach before giving you the code — with file paths and enough context to apply it. Treat the first response as a strong draft, not a final answer. Review it, try it, and send follow-ups for anything that needs adjusting. You're the one with the full picture of your site; the AI is doing the typing.
Tips for the best results
Point the AI at the theme folder
The magic is the theme’s llms.txt — it maps every file and config field. An assistant that can read the folder will use it; a chat window that can’t see your files will guess. Use an in-editor tool when you can.
Give the real values
Fill in your actual business name, phone, brand color, and copy. The prompt drops them straight in, so the AI applies your details instead of leaving placeholders.
Most content lives in business.json
Names, phone, hours, services, and service areas are all one config file. The prompt nudges the AI to edit that first — the cleanest, lowest-risk way to change your site.
One change at a time
Smaller, focused prompts one-shot more reliably than a giant wishlist. Ship one change, confirm the build is green, then come back for the next.
Ready to build a prompt?
Answer a few questions and copy a prompt you can paste anywhere.
Open the Prompt Builder →