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.4: Next/Image usage

Short answer: Production UI renders next/image for optimized srcset and layout stability. A plain img has no resizing, no srcset and no reserved space.

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.4

What it catches

Next/Image usage: production UI renders next/image for optimized srcset and layout stability.

Why

A plain img has no resizing, no srcset and no reserved space.

A bad example

<img src="/a.png" />

A good example

<Image src="/a.png" alt="" width={400} height={300} />

How it is checked

How to silence it

A person can silence one finding with brevio-core: ignore R17.4 -- 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.