# How to work with a website template using AI: a simple step-by-step plan

> A simple step-by-step plan for editing an Astro website template with AI: setup, AGENTS.md rules, safe prompts, images and SEO. Checked October 26, 2026.

- Author: [Vas](https://shipthemes.com/authors/vas)
- Published: Oct 26, 2026
- URL: https://shipthemes.com/blog/work-with-website-template-using-ai

A ready-made template gives you the design, and an AI assistant takes over the routine: it changes texts and images, edits the menu, and adds pages. This is simpler than it sounds. You say in plain words what needs to change, the assistant finds the right file and makes the edit, and all you have to do is look at the result and accept it or undo it.

Why not just ask AI to build the site from scratch? Without guidance it picks the most common option: according to Anthropic, when asked to make a landing page, the model almost always chooses the Inter font and purple gradients on a white background.[1] With a template, the design is already chosen, and the AI works inside it. Astro itself recommends asking AI to start from an existing template.[2] We wrote about this kind of “AI slop” in [How to avoid AI slop on a website built with AI](https://shipthemes.com/blog/avoid-ai-slop-on-ai-built-websites).

We sell Astro templates, so we have an interest here. AI sometimes makes mistakes, so the plan below includes simple checks. We found no direct measurements of how much time the “template + AI” combination saves, so there are no savings figures here.

> **Current as of October 26, 2026.** Software versions, prices and service terms change, and everything here is stated as of this date. The numbers in brackets point to the sources at the end of the page.

## In short: six steps

1. **Choose a template** and check its license.
2. **Get ready:** Node.js, Git, an AI assistant. Run the template as it is.
3. **Give the AI rules:** a short AGENTS.md file.
4. **Make every change a small task** and check each one.
5. **Handle texts, images and SEO.**
6. **Publish** the site and update it from time to time.

## Step 1. Choose a template

For a non-technical buyer, three questions to the seller are enough:

- **Whose license is it?** Your own site, client sites, resale? The terms differ: on ThemeForest a standard license covers one end product,[3] and a paid Webflow template covers one project for you or one client, so each new client or project needs a new license.[4] Read the license text before buying.
- **What is inside?** Source code, setup instructions, a list of pages, and a rules file for AI (AGENTS.md).
- **What about updates and refunds?** For digital goods in the EU, the right to return a purchase within 14 days can be lost if you started the download after expressly agreeing to give up that right.[5]

For more, see our [10-point checklist before you buy a template](https://shipthemes.com/blog/premium-template-checklist). ShipThemes' terms in short: the standard licence lets you build sites for yourself and for clients, on as many projects as you need, but not resell the template itself, and it includes updates ([licence](https://shipthemes.com/license)). Templates are digital downloads, so there are no refunds as standard, but if something isn't right, write to us and we'll look at your case ([refund policy](https://shipthemes.com/refund-policy)).

## Step 2. Get ready and run the template

You need three programs:

- **Node.js.** Astro uses it to build the site. Astro requires Node.js v22.23.4 or higher; odd-numbered versions such as 23 are not supported.[6] You can check your version with the command `node -v`.
- **Git.** It stores the history of your changes so that any of them can be undone. Install it and let the assistant run the commands.
- **An AI assistant that opens and edits files in the site folder by itself.** A chatbot where you have to copy code back and forth will not do. Examples: Claude Code (it needs a paid Claude plan: Pro costs $20 a month, or $17 a month if you pay annually;[7] it is also in the Claude desktop app, on the Code tab, with no command line to install[8]) and Codex (included in ChatGPT plans from Free up: Go is $8 a month in the US, Plus is $20 a month[9]). AI editors such as Cursor work too. We do not name a best option: we have not compared them on the same task.

If the terminal scares you, start with the assistant’s desktop app: it runs the commands, and you see what changed. You still need Node.js to run the site.

Now the first run. Unpack the template archive into a separate folder, open it in the assistant and write:

> Read the README. Install the dependencies, save the current state in Git with the message “Initial template” and start the site. Tell me which address to open it at. Don’t change anything.

The site will open on your computer, usually at `localhost:4321`.[10] Commands differ between templates: the assistant will read the README and pick the right ones. If the site opened, the foundation is ready, and from here you only change what you need.

## Step 3. Give the AI rules

AGENTS.md is a plain text file in the project root where you write rules for the assistant in advance: where things are, what not to touch, how to check the result. Many tools read it.[11] Claude Code reads AGENTS.md on its own only if the project has no CLAUDE.md file; if CLAUDE.md exists, add `@AGENTS.md` as its first line.[12] If such a file already comes with the template, just check that the paths in it are correct. Astro's docs warn that AI tools may use outdated patterns and suggest asking them to check the latest documentation,[2] so it also helps to note your Astro version in the file.

An example (the paths are illustrative; use the real ones from your template):

```markdown
# AGENTS.md

## Commands
- `npm run dev` — site at localhost:4321
- `npm run build` — must pass without errors before you say “done”

## Where things are
- Site name, menu, footer: src/config/site.ts
- Page texts: src/content/
- Colors and fonts: src/styles/tokens.css
- Images: src/assets/ (not public/)

## Do not
- Change layout, spacing or component files if the task is about texts or branding.
- Change the content schema: if the build fails, fix the content.
- Add libraries or fonts without my permission.

## Texts
- Use only the facts I gave you. If a fact is missing, write [TODO]. Do not invent names, numbers, reviews or awards.
- Every image must have a description (alt).

## Workflow
- The Astro version is in package.json: check the docs for that version.
- If a change touches more than three files, propose a plan first and wait for my answer.
- At the end, list the changed files and run the build.
```

Keep it short and include only what the AI cannot figure out from the code. In a 2026 study (a preprint on arXiv), such files did not reliably increase the share of tasks solved and raised the cost by about 20%; project overviews didn't help, and the authors conclude the files are worth it only for non-standard practices the AI can't learn from the code.[13] The study looked at resolving GitHub issues (bug fixes and new features) in Python projects, not at editing a site from a template, so its conclusion cannot be applied directly. One more thing: AGENTS.md is advice, not a ban,[12] so always check the result anyway (step 4).

## Step 4. Make every change a small task

The rule is simple: one task, one request, one check. A good request answers four questions: what to do, where it is, what not to touch, and how to tell it is done. Here is how to turn a vague request into a clear one:

| Vague | Specific |
| --- | --- |
| “Tell me about the project” | “Read AGENTS.md and the folder structure. Don’t change anything. Answer in 10 lines: where the site name and menu are, where the page texts are, where the colors and fonts are, and which command checks the site” |
| “Make it fit my brand” | “Replace the demo name with Acme Analytics. Change only: the site name, the logo file, the accent color and the texts in src/content/. Don’t touch layout, spacing, fonts or component files. Run the build and list all changed files” |
| “Write an About page” | “Rewrite the About page using only the notes below. If a fact is missing, write \[TODO\] instead of guessing. Tone: simple and specific. Keep all the fields in the file header. Notes: …” |
| “Add a services page” | “Plan first, don’t change files. Add a /services page using only blocks that already exist on the /features page. Don’t create new components. Show which blocks, which text file, and what will change in the menu. Wait for my answer” |

These examples are ours and are a starting point: adjust the paths and wording to your template.

**How to check the result.** After every task:

1. Open the site in your browser and look at the page.
2. Ask the assistant to run the build and list the changed files. Anthropic advises giving the model a check it can run itself: tests, a build, or a screenshot to compare.[14] If files you did not ask about were touched, undo the change.
3. Before the next task, ask: “Save the current state in Git.” Then any bad change can be undone with one phrase: “Return the files to the last save” (unsaved changes will be lost). Checkpoints inside Claude Code help, but they do not replace Git.[14]

If the result is not what you wanted, don’t argue with the assistant for long: after two failed corrections, Anthropic advises starting a new conversation and stating the task more precisely.[14]

## Step 5. Texts, images and SEO

**Texts.** Template texts usually live in separate files (in Astro these are “content collections”) with a schema: a list of fields and their types. If a required field is missing or the type is wrong, Astro shows a clear error.[15] It is a safety net: a typo in the name of a required field will not go unnoticed. Ask the AI to write only from your notes and to put \[TODO\] instead of guessing: without that rule it makes up numbers, awards and reviews. Google says appropriate use of AI is not against its guidelines, but reminds us that generative models do not retrieve facts, they predict likely words, so you should check the text by hand before publishing.[16]

**Images.** Ask the assistant to find all the demo images: image folders, the cover and image fields in content files, the social sharing image, the site icon. Put your own files in `src/assets/`: Astro can optimize images from `src/`, but serves files from `public/` as they are.[17] Add descriptions (alt): they are required on the `<Image />` and `<Picture />` components, and for a decorative image they are empty, `alt=""`.[17] Use your own photos, stock photos with a commercial license, or images from an AI service whose terms you have read.

**SEO.** Give the assistant three jobs:

- **Page titles and descriptions.** Ask: “List all pages, find duplicates, gaps and overly long titles and descriptions, suggest unique versions in a table and don’t change anything yet.”
- **A sitemap.** Run `npx astro add sitemap`; the settings must contain the site address (`site`). After the build you will get a `sitemap-index.xml` file, and you add a link to it in `robots.txt` with the line `Sitemap: https://your-site/sitemap-index.xml`.[18]
- **A check of image descriptions and links.** A report first, then changes.

After publishing, add the site to Google Search Console: it shows which pages are indexed. What not to expect: FAQ markup no longer produces rich results in Google (since May 7, 2026), and llms.txt files are not needed by Google Search and do not affect rankings.[19] The AI does not know real search volumes or your rankings: for that you need Search Console and SEO tools.

## Step 6. Publish and keep it updated

The build result is the `dist` folder of static files; any static hosting accepts it. Step-by-step instructions for Cloudflare are in [How to publish an Astro site on Cloudflare](https://shipthemes.com/blog/publish-astro-site-on-cloudflare). It is better to set up the domain and the access to hosting and payment accounts yourself rather than hand them to the assistant.

From time to time, ask the assistant to update Astro: the command `npx @astrojs/upgrade` updates Astro and its official integrations.[20] After updating, run the build and look at the site. ShipThemes lists template updates on the [changelog](https://shipthemes.com/changelog), and you download a new version from your Blink customer portal. Don't copy it over your edited site: ask the assistant to compare the two versions and carry over only the changes you need.

## Where the assistant copes and where you decide

This is our assessment based on experience and documentation, not the result of measurements.

- **Handles it on its own:** replacing texts and names, the menu and footer, a page built from existing blocks, a new blog post from a pattern, draft titles and descriptions, finding forgotten demo data, a second look at the changes already made.
- **Does it, but check:** forms (a static site needs an external service, and keys must not be stored in plain view), translations (a native speaker should check them), analytics (cookie consent may be needed), image descriptions.
- **You decide:** what you offer and to whom; facts about your business, prices, reviews and case studies; access to accounts and secret keys; legal texts (a privacy policy should be shown to a lawyer).

## Summary

- A template decides in advance how the site looks, and the AI works inside that frame.
- First run the template as it is, then change it in small tasks and check each one.
- A short AGENTS.md, a build and a look at the changes help you catch mistakes right away.
- Texts are your facts, images come with clear rights, and SEO is for people.

### Want to skip the setup?

If you pick a ready-made template: ShipThemes templates are standard Astro projects with the full source code and every page from the live preview, so everything in this guide applies to them as is. Browse the [template catalog](https://shipthemes.com/templates). And if you need a page in an evening with no terminal, a website builder is a better fit: we compared the options in [How to test a product idea fast](https://shipthemes.com/blog/test-product-idea-with-landing-page).

We described how to publish a site in [How to publish an Astro site on Cloudflare](https://shipthemes.com/blog/publish-astro-site-on-cloudflare). How to avoid the generic “AI look” is covered in [How to avoid AI slop on a website built with AI](https://shipthemes.com/blog/avoid-ai-slop-on-ai-built-websites).

## FAQ

### Do I need a programmer to work with a template and AI?

No, but you need basic skills: installing Node.js and Git, running the site, reading an error message and checking what changed. For the risky parts (the domain, forms with a server side, publishing), it is easier to do them once together with a specialist.

### Which AI subscription do I need, and how much does it cost?

Claude Code needs a paid plan: Pro costs $20 a month ($17 a month if you pay annually).[7] Codex is included in ChatGPT plans, Free included; Go is $8 a month in the US and Plus is $20 a month.[9] Prices are as of October 26, 2026; check them on the websites before buying.

### What if the AI breaks the site?

Return the files to the last save: ask the assistant, or run `git restore`. That is why you save the current state before every task and run the build. Checkpoints inside Claude Code do not replace Git.[14]

### Can I do it without the terminal?

Partly. The Claude desktop app (the Code tab) works with a project folder without installing a command line,[8] but you still need Node.js to run the site, and the assistant runs the commands. We have not tested cloud options that need no installation.

### Will Google penalize texts written with AI?

Not for the mere fact of using AI. Mass-producing pages with no value for people may count as a violation. Check facts and metadata by hand.[16]

### Can I use a template for client sites?

It depends on the license. On ThemeForest a standard license covers one end product,[3] and a paid Webflow template needs a new license for each new client or project.[4] ShipThemes' standard licence covers client work: you can build websites for your clients and charge for that work, but not resell the template itself ([licence](https://shipthemes.com/license)). Always read the license text before buying.

## Sources

Pages checked October 22–26, 2026. The numbers match the numbers in the text.

1. [Anthropic, “Improving frontend design through Skills”, November 12, 2025](https://claude.com/resources/articles/improving-frontend-design-through-skills)
2. [Astro Docs, Build with AI](https://docs.astro.build/en/guides/build-with-ai/)
3. [ThemeForest, Licenses](https://themeforest.net/licenses/standard)
4. [Webflow, Template licensing info and guidelines](https://templates.webflow.com/template-licenses)
5. [Your Europe, returning goods bought at a distance](https://europa.eu/youreurope/citizens/consumers/shopping/returns/index_en.htm)
6. [Astro Docs, Install and setup](https://docs.astro.build/en/install-and-setup/)
7. [Claude, Pricing](https://claude.com/pricing)
8. [Claude Code Docs, Get started with the desktop app](https://code.claude.com/docs/en/desktop-quickstart)
9. [ChatGPT, Pricing (including Codex)](https://learn.chatgpt.com/docs/pricing)
10. [Astro Docs, Develop and build](https://docs.astro.build/en/develop-and-build/)
11. [AGENTS.md, the format’s official site](https://agents.md)
12. [Claude Code Docs, How Claude remembers your project (CLAUDE.md and AGENTS.md)](https://code.claude.com/docs/en/memory)
13. [Gloaguen et al., “Evaluating AGENTS.md: Are Repository-Level Context Files Helpful for Coding Agents?”, arXiv, version 3 of September 29, 2026 (preprint, not peer-reviewed)](https://arxiv.org/abs/2602.11988)
14. [Claude Code Docs, Best practices](https://code.claude.com/docs/en/best-practices)
15. [Astro Docs, Content collections](https://docs.astro.build/en/guides/content-collections/)
16. [Google Search Central, Using generative AI content (updated October 1, 2026)](https://developers.google.com/search/docs/fundamentals/using-gen-ai-content); [Google Search Central Blog, Google Search's guidance about AI-generated content (February 2023)](https://developers.google.com/search/blog/2023/02/google-search-and-ai-content)
17. [Astro Docs, Images](https://docs.astro.build/en/guides/images/)
18. [Astro Docs, @astrojs/sitemap](https://docs.astro.build/en/guides/integrations-guide/sitemap/)
19. Google Search Central, updates: [FAQ rich results no longer shown](https://developers.google.com/search/updates#deprecating-the-faq-rich-result-feature) (May 2026) and [guidance on llms.txt files](https://developers.google.com/search/updates#clarifying-guidance-on-llms.txt-files) (June 2026)
20. [Astro Docs, Upgrade Astro](https://docs.astro.build/en/upgrade-astro/)
