A workspace rule called Editorial style reading "Headings are sentence case", and an agent run beside it whose drafted heading is marked and tagged with the rule it followed WORKSPACE INSTRUCTIONS RULE Editorial style Headings are sentence case. Never write “solutions”. One idea to a sentence. AGENT RUN Pricing that scales Drafted for /pricing EDITORIAL STYLE

Your stack. Your rules. Everyone moves faster.

What instructions give you

  • Two kinds, kept apart

    Skills are long-form playbooks for how to do a task. Rules are short constraints the agent always respects.

  • One library, one workspace

    Written once and shared with every project. Every project and teammate works from the same playbook.

  • Eight ready templates

    Four skills and four rules, each with a real body, not a stub. Brand voice, SEO defaults and Naming are installed in a new workspace.

  • Three ways to create

    Start from a template, start from scratch, or import a file. Import takes a markdown file you already keep in a repo.

  • Export back to markdown

    Download any instruction as a .md file with a slugified name. The library reads and writes the format, so it is not a one-way door.

  • Reference chips

    Drop a live collection, field, component, section, page, asset or brand token into the text. Chips serialize as plain tokens, so a .md round-trips cleanly.

The questions we get asked

Short answers on migration, models, roles, and uptime.

  • BetterCMS is headless by default and serves content over an API to any framework. It also ships a page builder, so teams that want one tool can stay in it.

  • The Migrator API maps an existing schema onto BetterCMS collections and brings entries and assets with it. WordPress, Contentful, and Sanity are covered.

  • Yes. Free includes one locale, Starter two and Pro five, and an extra locale is $8 a month per website. Translate inside the editor and publish each locale on its own schedule from the same content model.

  • There is no cap. Build models in the schema builder with your own fields, relationships, and validation rules, and change them without a migration.

  • The media library stores and organizes every asset. Images are resized, compressed, and served from a CDN, so you upload once and use the file anywhere.

  • Yes. Editors work side by side with live cursors, comments, and field locking, and every version is kept for your plan history window, 7 days on Free, 90 on Starter and 365 on Pro, so you can roll back to an earlier draft.

  • Set custom roles down to the field. Decide who can edit, who has to approve, and who is allowed to publish, then apply the same rules to your agents.

  • Content is encrypted at rest and in transit, backed up automatically, and every change is written to an audit log you can read.

Write your house style once

Content OS for modern websites.