Skip to content

DEVELOPMENT / CODING RULES

Make Every Code Change Start with the Right Rules

Before writing or reviewing code, your agent identifies the affected behavior, language and project, then follows the rule graph to read the applicable requirements and exceptions. When the scope changes, it checks which additional rules apply.

OUR DEVELOPMENT STORY

We Kept Repeating Our Coding Rules

We built this approach while developing Lorebo, after long rulebooks kept failing us.

INCONSISTENT APPLICATION

Agents Still Missed the Rules

Our agents did not consistently follow the same coding rules, even when those rules were written in the repository. Naming, structure and agreed conventions varied between tasks and sessions, so keeping the documents up to date was not enough.

CONTEXT OVERLOAD

Every Rule, All at Once

Agents read the repository rules as one large set, including guidance unrelated to the task. As that context grew, important requirements became harder to keep in focus. We had no common change-driven method for deciding what to read and when.

ONE SHARED METHOD

Rules in a Graph, Read for Each Change

We moved our coding rules into a graph database in Lorebo, linking each rule to shared principles, language guidance and repository profiles.

Our project instructions and review workflow require agents to consult the graph before writing, correcting or reviewing code. This keeps our approach consistent across tasks and sessions: project instructions define when to consult the rules, while Lorebo holds the detailed guidance.

We use this approach to develop Lorebo itself.

Illustrative Coding Rules review in an isolated demo. Tests were not run.

WHY IT WORKS

The Right Rules At Each Decision

Two filters keep the rule context focused. The agent reads what matters for the decision ahead.

CODE CONTEXT

Match the Code

A request handler and a storage layer need different guidance.

The agent selects rules for the code’s responsibility, language and project conventions, focusing on the relevant area.

PLANNED CHANGES

Follow the Change

The planned change narrows that context further.

Input changes call for validation and compatibility rules. The agent reads for the specific decision it is about to make.

TIMELY CONTEXT

Apply When Needed

Your agent follows the decision map to find the rules and exceptions that apply to the change.

If the scope changes, it checks what else applies.

TRY IT YOURSELF

Start with a Small Code Review

Try Coding Rules on a diff or a guided exercise before setting up your project. Need to install Lorebo or connect your agent? Get Started

Find Coding Rules in Templates → Development in Lorebo Desktop. Download it and apply it to a writable base, then open Start Here to get started.

Video coming soon

We’re preparing a walkthrough for this section.

Frequently Asked Questions

Good to Know

Can I start in Free?

Yes. In Free, check that your active local base is empty and writable, then choose Replace Active Base. Lorebo makes a backup before replacing it.

What’s in the template?

55 rules covering common coding decisions, Python and TypeScript, plus a decision map, repository profiles and a Practice Library.

How do agents use my rules?

Your project instructions or review skill guide your agent to the relevant rules before it writes or reviews code. The agent can cite those rules in its findings. MCP Setup Instructions

Can I adapt the rules to my repository?

Yes. Ask your agent to connect your repository and record the standards and CI checks you already use. You can add profiles for other repositories later.

Does activating the template make it writable?

Activate only opens the template in read-only mode. To use it fully, create a base from it as shown in Try It Yourself

What should I try first?

Open Start Here and choose a small diff or an exercise. You can try a review before connecting a repository. Ask your agent to cite the rules and explain each finding.

Can we use this as a team?

Yes. Run Free Headless on your server and grant your partners server access. Agents running there can use the same coding-rules base, so everyone works from shared project standards. Explore Headless

Is the template on Headless?

Yes. Use the Headless CLI to find and download Coding Rules. You can restore it into a local base. Register and Merge require Pro.

A person leaps from a laptop keyboard with an insect net to catch an enormous winged bug.

Try a small code review with Coding Rules. Start with your own diff or a guided exercise.

Privacy choices

Choose whether to allow optional cookies.