Skip to content

Coding-agent context file builder

Give Claude Code, Cursor and other coding agents the basics of your product before they write a line. Answer a few questions, then copy or download a starter file.

This tool runs in your browser. What you type stays on your device.

Answer a few questions

Skip anything you don’t have. The file leaves out every question you leave empty.

Go to your file

The example is a made-up insurer. It shows what each answer becomes.

Step 1Your product

One or two sentences.

Languages, frameworks, data and hosting. One per line, or all on one line.

Step 2Run and test

One command each. Leave out any you don’t use.

Step 3Conventions and rules

One per line. Skip what your linter already checks.

One per line. A reason next to each rule helps the agent apply it well.

Step 4Recent decisions

Choices an agent could otherwise undo. Say who confirmed each one, so the next person knows how far to trust it.

  1. Decision 1
Step 5Where agents should stop

One per line: a path or area, and why.

A person, channel or page for what the file can’t answer.

Your file

Empty so far

File type

Your file appears here as you answer.

Start with the product name, or fill the form with an example. You can skip any question.

Claude Code reads this file at the start of every session.

Save it as CLAUDE.md in the root of your repository. If your team also uses Cursor or another tool that reads AGENTS.md, keep the content in AGENTS.md and give CLAUDE.md the single line @AGENTS.md.

Keep it true as the product changes

A context file is a snapshot. Decisions change, rules get replaced, and the file keeps saying the old thing.

In Rivora, your team confirms each answer as a decision or rule. Each one records where it applies, where it came from and who confirmed it. You can stop one or replace it when things change.

Approved work goes to coding agents such as Claude Code and Cursor, with the decisions and rules attached.

See how it works

Decision · Active

Members on legacy NSW policies keep paper statements until June 2027.

Applies to
Member Portal
Confirmed by
Head of Claims Operations · 3 Oct 2026
Came from
Question on “Digital statements for members”
Used in
Backend and Platform · Delivery Backlog · Implementation Handoff

Illustrative example

Bring one real feature you’re planning in the next month.