DocumentationAGENT-READY SETUP

One prompt. A repository-aware integration.

Choose your setup in the installation guide, then copy the prompt generated for those choices. Your agent reads the matching instructions, asks for required access, and verifies its work. No installed skill required.

Choose your setup

Context-aware

The agent derives answers from the repository before asking the user.

Change-safe

Branching, dirty-worktree checks, route mapping, and rollback are part of the contract.

Production-safe

The Studio stays read-only until a real authentication and storage design is approved.

The basics, on your infrastructure.

Local keeps blog data in your chosen repository folder. Login-based self-hosting uses email and password at /login or your chosen route, with GitHub or Supabase Storage for content and optional R2 uploads. Managed, OAuth, audit logs and advanced team features are deferred. The local runtime works today; remote authentication and storage adapters require implementation and verification during integration.

Choose your setup and copy personalized instructions

THE AGENT INSPECTS

Evidence before questions

Router, framework, runtime, package manager, and monorepo layout
Existing routes, CMS, content, design system, auth, and middleware
Image policy, CSP, base path, locales, analytics, and deployment
Git state, repository instructions, validation commands, and protected files

THE AGENT ASKS

Only decisions code cannot answer

Full application, embedded blog, or content engine only?
Which route should own the publication?
Should existing content be migrated or remain in its current system?
Which brand, authors, features, and deployment targets are required?
Should production stay read-only or use an authenticated remote backend?

CONTROLLED WORKFLOW

Inspect, decide, integrate, verify.

The contract supports a full application, an existing App Router product, a hybrid or Pages Router migration, and a content-engine-only installation.

01Record the baseline and repository constraints
02Map route ownership and resolve conflicts
03Merge only the selected content and product surfaces
04Configure identity, metadata, images, and deployment
05Test the complete acceptance matrix and review the diff

DEFINITION OF DONE

The agent must prove the result.

A successful install is not just a clean build. The public routes, read-only boundary, responsive UI, content outputs, and preservation of the host application all need evidence.

All selected public and machine-readable routes work
Keyboard navigation, labels, focus states, themes, and responsive layouts pass review
Local production writes are blocked; login-based installs verify sessions and provider persistence
Lint, types, content audit, tests, and production build pass
The final diff contains no unrelated changes and has clear rollback steps