AI-assisted development

This starter is built to be operated by AI coding agents (Cursor, Claude, Copilot, Windsurf, ChatGPT, …). It ships a small “operating system” of instructions, a canonical design knowledge base, and portable audit prompts so an agent — or you — can make changes that stay on-system instead of drifting.

What the agent reads

Each tool picks up its own instruction file, but they all point at the same rules:

File	Used by	Purpose
`AGENTS.md`	Cursor, Codex, most agents	The universal brief: architecture tiers, hard rules, verification commands
`.cursor/rules/*.mdc`	Cursor	Project rules (`architecture`, `design-system`) applied automatically
`.cursor/hooks/` + `.cursor/hooks.json`	Cursor	Guard hooks that flag off-convention edits
`.windsurfrules`	Windsurf	Same rules in Windsurf’s format
`.github/copilot-instructions.md`	GitHub Copilot	Same rules for Copilot Chat
`.agents/skills/` + `.agent-skills.lock.md`	Skill-aware agents	Project-scoped skills; the lock file pins reviewed skills (checked in CI)

The design knowledge base

Design decisions are centralized so an agent never has to guess:

system/globals/ — the single source of truth for colors, typography, spacing, interaction, imagery, effects, responsiveness, accessibility, and the component/ pattern catalog. Read these before any UI work.
src/config/site.config.ts — bring-your-own-brand input. Brand values are translated into design tokens, never inlined.
src/registry.json — a machine-readable catalog of every component, section, and page.

Architecture (three tiers): components (src/components/ui/**) → sections (src/components/sections/**) → pages (src/pages/**). Build pages by composing sections; build sections from components.

Hard rules (what “on-system” means)

Tokens only. Colors/spacing/typography come from design tokens — no hardcoded hex/rgb, no raw Tailwind palette utilities (bg-blue-500). Use semantic tokens like bg-primary, text-foreground, var(--muted-foreground).
Dark mode stays working. Class strategy; never hand-invert colors.
Preserve cross-cutting features. i18n (English default, locale routing ready under src/pages/[locale]/), Cloudflare Pages deployment, SEO/OG/RSS/sitemap, Pagefind search, and the Starlight docs.
Content lives in collections. Blog, services, pages, FAQs, and stack are file-based content collections under src/content/ — see Content Management. Don’t hardcode copy that belongs in a collection.

Verify before “done”

Ask the agent to run these and fix anything that fails:

pnpm build          # static production build
pnpm lint           # eslint + stylelint + type-check + KPIs + i18n
pnpm run check:kpis # design-convention checks (the on-system source of truth)

Prompting

Starting a task

Point the agent at the system first, then state the goal:

Read AGENTS.md and system/globals/ before editing.
Add a "Logos" section to the homepage that reuses existing components and tokens.
Keep dark mode and i18n intact, then run `pnpm build` and `pnpm lint`.

Self-audit prompts

system/prompts/ holds portable prompts you can paste into any chat tool to audit the project against its conventions. They reference system/globals/ and the check:kpis script.

Prompt	Audits
`system/prompts/tokens.md`	Hardcoded colors / off-token usage
`system/prompts/accessibility.md`	WCAG AA: keyboard, focus, alt text, landmarks
`system/prompts/responsive.md`	Layout integrity from 375–1920px
`system/prompts/darkmode.md`	Dark-mode parity & contrast
`system/prompts/performance.md`	Islands, assets, Lighthouse
`system/prompts/seo.md`	Metadata, OG, sitemap, structured data

Example:

Run the audit in system/prompts/accessibility.md against src/pages/contact.astro
and list concrete fixes with file:line references.

Keeping skills reviewed

Project skills live in .agents/skills/. The reviewed, pinned set is recorded in .agent-skills.lock.md; the Skills Verification CI job reports the locked skills on every run. Add or update a skill, then refresh the lock file so collaborators (and CI) see the same pinned set.