Solution

Govern the content your AI coding workflow creates

AI coding makes product surfaces faster to ship, but it also spreads copy, labels, docs, and locale strings across components. Contentrain gives that output structure, review, and reuse.

Open Studio

Solo developers

Local-first packages, MCP, and a generated SDK — no account needed.

Problem

AI-built apps create content faster than teams can govern it

Coding agents can generate pages, components, labels, docs, and localization candidates in minutes. Without a content system inside the repo, that copy becomes invisible product debt.

Hardcoded strings spread through components
Prompts create copy without shared rules
Reviewers see code changes but miss content intent

agent · Contentrain MCP

▸ "Add a pricing FAQ entry"

→ contentrain_content_save

model: faq locale: en

→ contentrain_validate

✓ Saved to branch cr/content/faq

# agent proposes · you approve in Git

Normalize

Normalize turns agent output into structured content

The first move is not a CMS migration. Run Normalize against the codebase, approve what should become content, and generate access so future agents work with models instead of loose strings.

Scan generated UI code
Extract approved strings into models
Patch reuse points after review

contentrain — normalize

$ contentrain scan ./src

Scanning source for hardcoded strings…

✓ Scanned 47 files

123 candidate strings found

marketing/hero 18

ui/navigation 24

ui/buttons 31

→ extracted to branch cr/normalize/marketing

✓ Ready for review in Git

Agent context

Rules and skills give agents a shared playbook

Contentrain rules and skills explain schema, SEO, i18n, accessibility, validation, and workflow expectations in a way agents can follow. That reduces prompt drift across sessions and teammates.

Content quality and SEO rules
Normalize and translation workflows
MCP usage and security rules

.contentrain/rules/contentrain.md

# Agent operating rules

- Save content through MCP tools only

- Validate against the schema before submit

- Open a review branch per change

- Never edit generated files

# shared by every agent on the repo

Team review

Studio adds human approval when the team grows

A solo developer can start locally, but AI-native teams need content review, roles, branch health, media, and delivery controls. Studio gives that surface without moving content away from Git.

Review branches and diffs
Editor and reviewer roles
Media, CDN, forms, and webhooks

contentrain diff

$ contentrain diff

● Pending branches (3)

cr/content/marketing/hero +2 / -1

cr/content/blog/launch +5 / -0

cr/content/faq/pricing +1 / -0

✓ Approve in Git → merged to main

Outcome

The result is faster AI work with fewer uncontrolled changes

Agents still generate and modify content quickly, but the operating path is visible: models, validation, branches, review, and runtime access. That is the difference between acceleration and entropy.

AI speed stays in the workflow
Git remains the audit layer
Content becomes reusable across product surfaces

The result is faster AI work with fewer uncontrolled changes

Common questions

Why do AI-native teams need a content layer?

Because AI agents create copy constantly. A content layer makes that output reviewable, reusable, localizable, and visible to future agents.

Should the first CTA be Studio or init?

npx contentrain init should be first for AI-native teams because the wedge is inside the codebase. Studio becomes the second CTA when review and collaboration enter.

Can agents use Studio too?

Yes. Studio exposes governed content operations and conversation paths, while local MCP covers developer-side workflows.

Next paths

Build a governed content layer before content becomes product debt.

Developers can start with the MIT packages. Teams can move into Studio when review, roles, delivery, and licensing matter.