Agent Setup

Goal: Turn the freshly extracted paid theme into your site — in one conversation with your AI agent, without hand-editing configuration files.

Paid theme only

The agent workspace and setup command ship with the paid theme. Using the free starter theme? Configure it by hand instead — the Getting Started guide walks you through the same files in about 10 minutes.

With your AI agent ^recommended

The theme ships ready for agentic coding tools: Claude Code, Codex, Cursor, Antigravity, OpenCode, Gemini CLI, GitHub Copilot, Windsurf, Claude Cowork. Your agent reads the bundled AGENTS.md and already knows what to do.

1. Extract the purchased ZIP and install dependencies

   npm install

2. Open the folder in your AI tool and ask it to set up your site — for example:

   Set up this theme for my company. We’re called …, our domain is …, we want the site in French and English.

   In Claude Code you can simply run the bundled /setup command.

3. Answer its questions. The agent collects your company details, drafts SEO titles and descriptions per language for your approval, writes setup.config.json, validates it, and runs the setup.

4. Review the result — the agent verifies the build and starts npm run dev so you can see your site.

Without an agent ^{same result, by hand}

The agent drives the exact same command you can run yourself:

1. Copy the example config

   cp setup.config.example.json setup.config.json

2. Fill it in — company details, site URL (a bare domain is fine), the languages you want (fr, de, en — must include fr), an SEO title (30–60 characters) and description (120–160 characters) per language, team members, and an optional Google Tag Manager ID.

3. Validate — errors name the exact field to fix, and nothing is written:

   npm run setup:check

4. Apply

   npm run setup

What it writes

Setup is deterministic — the same input always produces the same files — and never destructive: every touched file is first backed up to a timestamped copy in .setup-backups/ at the project root.

File	What happens
src/consts.ts	Regenerated: company information and team members (COMPANY, EMPLOYEES)
src/i18n/ui.ts	Updated in place: language list, site title and description per language — the full translation dictionary is preserved
.env	Regenerated: your GTM ID (if provided)
astro.config.mjs	The site URL is patched to your domain
public/images/team/	Team portrait files are copied in

Languages

The theme ships complete translations and page trees for French, German and English; setup lets you choose any subset that includes French (the default locale — existing URL structures depend on it). To genuinely add another language, follow the Adding Languages guide after setup.

After setup

Your agent’s setup flow includes writing your team members’ roles and bios (employee.<ID>.title / .bio in src/i18n/ui.ts, per language) — if the team cards show names with empty roles, ask your agent to complete that step. The demo copy beyond that — navigation labels, service descriptions — still carries the example agency’s text. Edit the values in src/i18n/ui.ts per language (keep every locale’s key set identical), or simply ask your agent to translate the remaining content for your business.

From here the docs apply to both themes:

• Configuration — everything setup wrote, explained file by file
• Customization — logo, colors, content
• Adding Languages — extend beyond FR/DE/EN
• Deployment — go live

You can re-run setup at any time — each run creates fresh backups first.