jev-rules

# Jev picks which of your rules apply to each prompt, so Claude only sees the ones that matter.

<p>
  <img src="https://img.shields.io/badge/Claude%20Code-Plugin-5A67D8?style=for-the-badge" alt="Claude Code plugin" />
  <img src="https://img.shields.io/badge/Version-0.5.0-3178C6?style=for-the-badge" alt="Version 0.5.0" />
  <img src="https://img.shields.io/badge/Dependencies-None-1C7C54?style=for-the-badge" alt="No dependencies" />
  <img src="https://img.shields.io/badge/License-MIT-yellow?style=for-the-badge" alt="MIT License" />
</p>

<p align="center">
  <a href="https://github.com/EliaAlberti/jev-rules/releases/tag/v0.5.0">
    <img src="social/jev-rules-pane.gif" alt="The rules pane beside a Claude Code session: a checkout bug report turns three of fifteen rules green, then an edit to package.json turns the dependency rule green at 0.97." width="800" />
  </a><br />
  <em>A real Claude Code session with the rules pane, edited to 30 seconds. The full-quality video is attached to the <a href="https://github.com/EliaAlberti/jev-rules/releases/tag/v0.5.0">v0.5.0 release</a>. The earlier <a href="https://eliaalberti.github.io/jev-rules/">40-second demo</a> is still online.</em>
</p>

If you use Claude Code for a while, you end up with a pile of standing instructions: test the payment code, use British spelling, follow the deploy checklist. Show all of them on every prompt and Claude wades through rules that have nothing to do with the request; pick them by keyword and a rule is missed the moment the request does not contain its trigger word. jev-rules asks a small, fast decision model called Jev one yes/no question per rule, "is this request about that?", and passes Claude only the rules that get a yes. It takes well under a second and costs a fraction of a cent per p