brevio-core

Catches the mistakes coding agents repeat before they merge: a pull-request gate with no model call and no API key.

View the Project on GitHub Brevio-Ventures/brevio-core

R17.6: Client boundary minimization

Short answer: Push ‘use client’ directives down to leaf interactive nodes. A directive at the top of a big tree sends all of it to the browser.

Group: React and Next.js patterns. Status: stable. Generated from the rule definitions; do not edit by hand.

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R17.6

What it catches

Client boundary minimization: push ‘use client’ directives down to leaf interactive nodes.

Why

A directive at the top of a big tree sends all of it to the browser.

A bad example

'use client';  // on the whole page

A good example

'use client';  // only in <LikeButton />, a leaf

How it is checked

How to silence it

A person can silence one finding with brevio-core: ignore R17.6 -- reason on the line or the line above. Without the reason it does not count. An agent cannot silence it: the agent hook and the MCP tools never honour the comment, and a pull request that adds one is reported until a reviewer allows it. Fixing the code is still the better answer.

To change what the rule flags, edit its definition in dev_rules.py or code_rules/__init__.py. That is a code change and is reviewed like one.