# Customize Consultiz With AI

## Customize Consultiz With AI

**Skill level:** Beginner · **Works with:** Claude, Cursor, GitHub Copilot, Windsurf, ChatGPT, and other assistants

Consultiz is built so that an AI assistant can change it safely. Three things make that work:

1. **Content is separate from code.** Almost every change is an edit to a Markdown, TOML, or JSON file, which is the kind of task AI tools do well.
2. **The rules are written down.** `config.toml` explains each key in comments, many content files list their options next to them, and `docs/section-ownership.md` maps every section to its content file and pages.
3. **The theme ships instruction files for AI tools.** They describe the folder structure and the rules for changing it. The tools in the table below load their file when you open the project folder.

### The AI Instruction Files In Consultiz
| File                                    | Loaded automatically by                          | What it contains                                       |
| --------------------------------------- | ------------------------------------------------ | ------------------------------------------------------ |
| `AGENTS.md`                             | Tools that read `AGENTS.md`, such as OpenAI Codex, Cursor, and GitHub Copilot's coding agent | The full rules: project structure, sections and page blocks, how overrides merge, validation limits, styling, components, forms, languages, customizing for your own site, and checks |
| `CLAUDE.md`                             | Claude Code                                      | Imports `AGENTS.md` (the `@AGENTS.md` line), plus a reminder to run the checks |
| `.github/copilot-instructions.md`       | GitHub Copilot                                   | A short summary that points to `AGENTS.md`             |
| `.cursor/rules/theme-architecture.mdc`  | Cursor (always on)                               | The architecture rules, pointing to `AGENTS.md`        |
| `.windsurf/rules/theme-architecture.md` | Windsurf (always on)                             | The architecture rules, pointing to `AGENTS.md`        |
| `NEXTJS-TO-ASTRO-GUIDE.md`              | None: mention it in your request                 | Worked examples: change the header and footer, add a section, create a page |
| `README.md`, `PUBLIC-VALUES-NEEDED.md`  | None: written for you                            | The editing map and override rules, and the demo values to replace before launch |

You don't need to edit these files. They tell an assistant to keep text in `src/content/`, to make every change in English and French, to reuse the theme's buttons, icons, and images, to use the color tokens in `theme.css`, and to run `npm run astro-check` when it finishes. `AGENTS.md` also covers the things that are easy to get wrong:

- **Page blocks**: how a page's named block merges with the section file, and that a misnamed block is ignored without an error
- **Validation limits**: section files only check their shared fields, so a misspelled option there isn't caught
- **Customizing for your own site**: change content and config first, don't invent testimonials, client names, logos, metrics, ratings, awards, or prices, and check every changed page at phone and desktop width in each language

### Two Ways To Work With AI
<CardGrid>
  <Card title="AI that can open your files" icon="laptop">
    Cursor, Windsurf, Claude Code, GitHub Copilot in VS Code, Codex. Open the
    `consultiz` project folder in the tool and describe the change. It loads
    its instruction file, edits the files, and can run the checks. **This is
    the best way to work.**
  </Card>
  <Card title="Chat assistants" icon="comment">
    ChatGPT, Claude, or Gemini in the browser. They can't see your project, so
    you paste `AGENTS.md` and the file you want changed, and copy the answer
    back. Fine for rewriting text, one file at a time.
  </Card>
</CardGrid>

The [AI Workflow](/consultiz/ai-customization/ai-workflow/) page shows both step by step.

### What AI Is Great At In Consultiz
- Rewriting the demo copy for your firm, in English and French
- Filling collections: solutions, people, careers, portfolio, case studies, industries, and blog posts
- Changing plans and fees, FAQ answers, and menus
- Trimming the demo menus and removing pages you don't need
- Replacing the demo contact details everywhere they appear
- Translating the site into another language
- Explaining an error message and fixing it

### What To Check Yourself
- **Facts and numbers.** AI writes convincing copy. Check every quote, statistic, rating, award, fee, and claim before you publish. Ratings and award badges must be ones your firm really has.
- **Longer names and labels.** A name or label longer than the sample can be cut off or wrap. Check banners, menus, buttons, and cards at phone width.
- **Legal pages.** The privacy policy and terms are placeholders. Have them reviewed for your business.
- **The result in the browser.** Look at each changed page in English and French, on a phone-sized window. Section files are only loosely checked, so the page is the real test.
- **Forms.** Submit each form once on the live site.

<Aside type="tip" title="Five rules for good results">
  1. One task per request. "Change the homepage banner" works better than "redo the site".
  2. Name the file when you know it. Every page in these docs tells you which one.
  3. Say what must stay the same: "keep every key and option, only change the text".
  4. Ask for both languages, or say you only use English.
  5. Save a checkpoint first (a git commit or a copy of the folder), so any change can be undone.
</Aside>

Ready? Go to the [Prompt Library](/consultiz/ai-customization/prompt-library/) for copy-paste prompts.