THE CONTEXT YOUR AGENT NEEDS

For agents.

Give your coding agent the maintained Storypane skills. They point to existing services, explain authorization boundaries, and help keep a concrete change small.

For coding agents

Set up with an agent

Open your Storypane checkout in your coding agent, then paste these instructions. Enter the administrator password in your own terminal.

In the Storypane checkout, read AGENTS.md and docs/getting-started.md,
then set up a fresh local Storypane installation.
Check Node and Docker prerequisites, run node scripts/setup-env.mjs, and
start the bundled Compose services. Keep secrets in the ignored env file;
never print them or replace existing configuration, keys, or volumes.
Check readiness, then give me the administrator bootstrap command to run
in my own terminal so I can enter my password privately.

Read the setup guide Get the agent instructions

Each download records the CMS revision it was checked against. Ask your agent to read AGENTS.md and re-read your checkout before making changes.

The getting started guide covers Docker and source development. For an existing installation, use the agent upgrade instructions to preserve data, keys, and backups.

Once you are signed in, follow the team workflow: production for content editors and a linked dev space per developer. The editor quickstart walks through building a schema in dev, promoting it, and publishing in production.

Customize your copy

The storypane-customize skill covers repository structure, direct integration recipes, schema and type changes, UI patterns, and relevant tests. Add the thing your team needs directly to your application.

Download customize skill ↓Read SKILL.md

Run your installation

The storypane-deploy skill covers local Node/Docker setup, generated configuration, upgrades, recovery, and verification.

Download deploy skill ↓Read SKILL.md

Give the skills to your agent

Get your own copy of the Storypane source.
Extract a skill archive. Keep its SKILL.md and references/ together.
Install the folder in your agent’s skill directory, or give your agent the path to SKILL.md. For Codex, use ~/.codex/skills/.
Describe the change, then review and test it in your own copy before deploying.

Try: “Use storypane-customize to connect our internal asset library.” This is an illustrative request, not a prebuilt integration. You maintain your source changes when taking upstream updates.

Connect an agent to the CMS

Use the MCP adapter or the management API and CLI for content automation. Start with a read-only token and grant specific write scopes when needed. For schema authoring, target the developer’s dev space and provide a separate production token only when sync or promotion is needed. Keep credentials in your secret store or local agent configuration.

View this guide on GitHub ↗