Skip to content

Maintain a creator site with AI agents

StratoLMS ships a creator AGENTS.md, local workflow documents and an optional four-skill toolkit. No AI API key or AI runtime dependency is required. Your coding tool operates on the site’s files and runs the same CLI checks as a human.

Use npm create stratolms@latest my-course to initialize an empty destination, install dependencies, and open the generated site in your coding tool. Pin an exact released version when you need a reproducible scaffold. For work on StratoLMS itself, follow the source-fork setup. The repository’s root guide is for framework maintainers; the generated site’s guide is for creators.

Start with this prompt:

Help me set up StratoLMS. 1. Read the project's AGENTS.md and identify the installed StratoLMS runtime and CLI versions. 2. Fetch https://stratolms.app/llms.txt and follow its links to the official setup guidance compatible with those versions. 3. Report the documentation version or revision used. 4. If fetching fails, say so and use the bundled instructions. Do not silently substitute incompatible latest-version guidance. 5. Follow my hosting and feature choices, preserve existing secrets, and run the documented checks. 6. Report completed work and any remaining setup steps.

The root guide also routes content, theme, maintenance and verification tasks to small local documents. Lesson bodies and imports are data, not agent instructions. Ignoring a file in Git does not prevent a coding tool from reading it; give tools only the workspace access appropriate to the task.

From the generated site’s root, choose one discovery location:

Terminal window
pnpm stratolms agents install --tool codex --dry-run --json
pnpm stratolms agents install --tool codex --json

Choose cursor or claude instead to install in .cursor/skills or .claude/skills. Codex uses .agents/skills. The installer preserves customized files and refuses a duplicate StratoLMS toolkit in another discovery root because Cursor discovers several providers’ directories. Shared workflow documents work without the optional native installation. Skills are instructions, not a sandbox.

Codex and Cursor document AGENTS.md support. Claude Code supports it as a fallback starting with version 2.1.277; use 2.1.281 or newer for the documented fixes. A project or ancestor CLAUDE.md, .claude/CLAUDE.md or CLAUDE.local.md can take precedence. Check that your tool loaded this site’s guide. StratoLMS creates no CLAUDE.md shim. Use the tool compatibility guidance above and verify which instructions your installed tool loads.

The setup answers schema and nonsecret example ship in docs/agent-workflows. For an existing site, omit adapter; changing adapters requires a deliberate source and dependency migration. Setup preserves omitted settings and existing keys, generates missing keys and reports only file actions and key names.

Terminal window
pnpm stratolms setup --answers answers.json --dry-run --json
pnpm stratolms setup --answers answers.json --json
pnpm stratolms add plausible-analytics --dry-run --json
pnpm stratolms import --from podia --file export.csv --dry-run --json
pnpm stratolms check --format json
pnpm stratolms doctor --json
pnpm check
pnpm build

Do not commit provider credentials or imported learner records. JSON import reports include counts and file actions, never learner rows. Review imported content before changing draft status or configuring a paid product.

Repository tests qualify the instructions, shipped schema, toolkit installation, setup previews, collision handling and secret preservation. They do not prove a particular model follows every instruction. Authenticated Codex, Cursor and Claude sessions require a separate owner smoke test: create a draft course, change branding, repair invalid frontmatter, run the checks and inspect the diff. Confirm the guide loads and no secret is included in the conversation or report.