jev-rules
Jev picks which of your rules apply to each prompt, so Claude only sees the ones that matter.
Added to Jevfast
How it uses Jev
Jev evaluates one yes/no question per rule against each Claude prompt, then the plugin supplies matching rules and relevant map documents to Claude. It can also re-evaluate rules against a file path before Claude edits it.
What Jev decides
Illustrative Jev requestExample answers · not a recorded Jev response · Source ↗
Question 1 · payments rule
YOUR APP
INSTRUCTION
The user’s request is about changing code that computes prices, totals, discounts, taxes, refunds, payments, or the checkout flow.
STATE
A request to change checkout/payment logic, checked against the example payments rule.
JEV · NOUL
YesNo
App workflow
- Read project guidance
Load rule files from .claude/jev-rules and map documents from .claude/jev-map.
- Judge relevance
Send the prompt with one yes/no question per rule and map document to Jev.
- Provide matching context
Pass rules and map documents above the configured threshold to Claude; fall back to all rules if the call fails.
- Check edit targets
When Claude is about to edit a file, assess its path and add applicable rules not already delivered.
Why it is interesting
The plugin replaces keyword-triggered instruction loading with per-prompt judgments and has a fallback that supplies every rule if its decision path fails.