Open brand schema

Your brand’s meaning,
written down and checkable.

The open schema for what your brand means. Draft it free, publish it free, and give every producer the same page.

Draft in your browser$ npx ramoira init
$ npx ramoira init
 
↳ ramoira/DRAFTING.md installed for your agent
↳ Your agent reads your project
↳ and asks what only you know
 
✓ Valid 3.2.0 schema
✓ brand.schema.json saved
 
→ ramoira push
→ you review it, then make it public
The same problem. Four different angles.
Solo Builder
"My AI content sounds different every time I post."
Every session starts from scratch. Early recognition requires consistency.
Developer
"I rebuild the same brand context for every project."
The brief never travels with the code. Every handoff is a re-brief.
Brand Founder
"My website says one thing. My ads say another."
The brand lives in your head. Every vendor reinterprets it slightly.
Agency
"Our review cycles eat our production time."
Violations happen because the spec isn't machine-readable. Every piece is a judgment call.
How to use it

Free to draft. Free to publish.

Draft
FreeNo account required
npx ramoira init
  • ✓Full 5-layer candidate schema, drafted from your project and your answers
  • ✓By your own coding agent after npx ramoira init, or in your browser at /draft
  • ✓Works with Claude Code, Cursor, Windsurf, Replit, Lovable, v0
  • ✓Validate and check your drafts locally against the spec
Read the docs
Published
FreeFree account
ramoira push
  • ✓Everything in Draft
  • ✓You review each push: affirm rules, then make it public
  • ✓Public summary at ramoira.com/brands/[slug]/
  • ✓Shown as a candidate, not ratified
  • ✓Machine-readable status endpoint
  • ✓Remote agents and pipelines can consume it
Sign in to publish
What publishing gives you

Your schema at a stable URL.
The brief travels with the work.

Publishing extracts your public rules and the Identity, Narrative and Voice layers of your schema and serves them at a public, cacheable endpoint, while the full schema stays private. Any agent, pipeline, or collaborator can fetch your brand spec without you managing a hosted file or re-briefing from scratch. The schema travels with the work.

GET/brands/[slug]/schema.summary.json
Public rules, plus the Identity, Narrative and Voice layers. Cached. Any agent can fetch it.
GET/brands/[slug]/status
Publication state. Facts only, never a score. Machine-readable.
Cache-Control: public, max-age=300, stale-while-revalidate=3600
Open source

Open format. Open source tools.

The CLI and schema spec are entirely open source. You can integrate brand validation natively into your GitHub repos, CI pipelines, and Cursor rules without any vendor lock-in.

ramoira/cli
npx ramoira init
GitHub →

The CLI that drafts brand.schema.json locally. Fully open source so you can inspect exactly how it works before bringing it into your workflow. The CLI runs locally and only connects to Ramoira when you push a version for your review.

npx ramoira initSet up drafting for your coding agent
ramoira checkCheck a draft against your rules
ramoira validateValidate against spec
ramoira pushSend a version to ramoira.com for your review
ramoira pullBring down the version you reviewed
ramoira statusCheck publication status
ramoira/brand-schema-spec
SPEC.md
GitHub →

The open schema format specification. Designed to be completely transparent and open so you can build internal tools and automations without proprietary lock-in.

SPEC.mdFull format specification
examples/Worked examples (fictional brands)
validation/Reference validator
layers/Per-layer documentation
ramoira/docs
agent-readable
GitHub →

Integration guides for Cursor, Claude Code, Lovable, and v0. Written for agents and developers, not humans.

integrations/cursor.mdCursor rules integration
integrations/claude-code.mdClaude Code CLAUDE.md setup
integrations/v0.mdv0 system prompt setup
Why open
No vendor lock-in
The schema format is open by design. Every brand.schema.json file on GitHub, every Cursor rules reference, and every CLAUDE.md you create belongs to you. You can use the format with or without Ramoira.
Complete transparency
When you run npx ramoira init, you can read the CLI source and see exactly what's happening. Openness is the difference between a tool you trust and a black box you avoid.
Built for the ecosystem
The schema is designed to be the connective tissue between your brand and the AI agents you use. By keeping the specification open, we ensure it can be natively supported by any tool, pipeline, or agent.