---
title: AI Workflow
description: Give AI chatbots and coding agents the Initium assets they need to build consistent pages.
slug: ai-workflow
order: 6
---

# AI Workflow

Initium works best when your AI tool has two sources of truth:

- `DESIGN.md` for visual direction.
- `STRATEGY.md` for audience, offer, positioning, and page structure.

Place both files in your project root while you work. You do not have to commit them.

```txt
DESIGN.md
STRATEGY.md
```

## What Each File Does

`DESIGN.md` tells the AI tool how the interface should look. It captures your selected style preset, color direction, typography, type scale, radius scale, button style, form style, spacing, and overall visual rules.

`STRATEGY.md` tells the AI tool what the page should communicate. It captures the business, audience, offer, pain points, proof, objections, conversion goal, and suggested structure.

Use both files together. A page can look polished with only `DESIGN.md`, but it will be more generic without `STRATEGY.md`. A page can be strategically clear with only `STRATEGY.md`, but it may drift visually without `DESIGN.md`.

## Generic AI Workflow

Start a new chat and ask the tool to read the files before writing code:

```txt
Read DESIGN.md and STRATEGY.md from the project root.
Treat them as source material for this page.
Use Initium blocks for major sections.
Keep the installed Initium style preset intact.
Do not invent proof, testimonials, logos, metrics, awards, guarantees, or customer names.
```

Then ask for a specific outcome:

```txt
Build a landing page for the primary offer in STRATEGY.md.
Use installed Initium blocks where possible.
Match the visual direction in DESIGN.md.
Ask before filling in missing proof or claims.
```

If the Initium skill pack is installed, add:

```txt
Follow .agents/skills/initium/SKILL.md before changing UI code.
```

## Cursor

Place `DESIGN.md` and `STRATEGY.md` in the project root, then ask Cursor:

```txt
Read DESIGN.md, STRATEGY.md, and .agents/skills/initium/SKILL.md if it exists.
Use Initium blocks and styles to build the requested page.
```

Cursor can use the installed skill when project skills are enabled. If it does not pick the skill up automatically, reference the skill path directly.

## Claude Code

Ask Claude Code to read the project files explicitly:

```txt
Read DESIGN.md and STRATEGY.md first.
If .agents/skills/initium/SKILL.md exists, follow it as the workflow.
```

Then give it one page or section at a time.

## Codex

Attach or reference `DESIGN.md` and `STRATEGY.md` at the start of the task:

```txt
Use DESIGN.md for visual rules and STRATEGY.md for page strategy.
Do not create UI until you have read both files.
```

If the project includes the Initium skill files, point Codex at `.agents/skills/initium/SKILL.md`.

## v0

Use `DESIGN.md` and `STRATEGY.md` as prompt context:

```txt
Use the attached DESIGN.md as the visual system.
Use the attached STRATEGY.md as the page brief.
Generate a page that can be implemented with Initium and shadcn components.
```

When moving code back into your app, install the matching Initium styles and blocks through shadcn.

## Lovable

Add `DESIGN.md` and `STRATEGY.md` as project context or paste the relevant sections into the prompt:

```txt
Follow this design direction and strategy brief.
Keep the page specific to the offer.
Use shadcn-compatible structure and avoid unsupported claims.
```

Use the Initium registry in your code project when you install the final styles and blocks.

## Replit

Add `DESIGN.md` and `STRATEGY.md` to the project root, then prompt Replit:

```txt
Read DESIGN.md and STRATEGY.md from the repository.
Use them before editing the UI.
```

If the skill pack is installed, ask it to read `.agents/skills/initium/SKILL.md`.

## Windsurf

Place the files in the root and reference them in your first message:

```txt
Use DESIGN.md as the visual source of truth.
Use STRATEGY.md as the page strategy.
Follow .agents/skills/initium/SKILL.md if present.
```

Keep the task narrow: one page, one section, or one revision pass per chat.

## Machine-Readable Documentation

AI tools can read this documentation directly without scraping HTML:

- [`/llms.txt`](https://initium.sh/llms.txt) lists every docs page with a short description.
- [`/llms-full.txt`](https://initium.sh/llms-full.txt) bundles the full documentation as one markdown file.
- Every docs page is available as raw markdown by appending `.md` to its URL, for example `https://initium.sh/docs/getting-started.md`.

The registry catalog itself is also machine-readable:

- [`https://app.initium.sh/r/registry.json`](https://app.initium.sh/r/registry.json) is the full catalog — every block, style, and preset with its name, description, categories, and tags. No authentication required.
- [`https://app.initium.sh/api/registry/search?q=pricing`](https://app.initium.sh/api/registry/search?q=pricing) searches the catalog by section type, tag, or text and returns ranked JSON results with install commands.

Point your agent at these URLs when it needs Initium setup or registry details that are not already in your project.

## Keep The Files Current

Regenerate `DESIGN.md` when you change the visual direction in the Style Builder.

Regenerate `STRATEGY.md` when the offer, audience, positioning, pricing, proof, or conversion goal changes.

Start new AI chats after major changes so the tool reads the latest files instead of relying on older context.