wonjangcloud9/brainres

Claude answers your brain can actually read.
English · 한국어
caveman makes Claude shorter. humanizer makes it sound human.
brainres makes it understandable. It reviews 725 findings from cognitive science, psycholinguistics, decision science and human–AI trust research. Each finding is either applied as a writing rule or excluded with a stated reason.
## Same question, two answers
> "My React component keeps re-rendering forever. Why?"
Default Claude-style answer · Brain Score 50 · 272 words With brainres · Brain Score 100 · 134 words
Great question! Infinite re-renders are a common issue that many React developers encounter… Let me break down the most common causes.
## Understanding the Problem
React re-renders a component whenever its state or props change. When a component triggers a state update during rendering, or when an effect updates a value that it also depends on, it can potentially create…
## Common Causes
1. Calling setState in render – …
2. useEffect with incorrect deps – …
3. Objects in dependency arrays – …
4. … (7 causes, all bold)
## Solutions
It is important to note that the right solution depends on the specific cause…
I hope this helps! Let me know if you have any other questions.
Your useEffect is almost certainly updating a value it also depends on, so every render schedules the next one.
The loop:
1. Render → effect runs → setItems(...)
2. items changed → React re-renders
3. items is in the deps → effect runs again → back to 1
Fix it by depending on the input, not the output:
js
useEffect(() => {
fetchItems(query).then(setItems);
}, [query]); // was [items]
To confirm, add console.count("render"). A count that climbs while you touch nothing means the loop is real.
If neither pattern matches, paste the component and I'll point to the exact line.
The answer is in sentence 1. The mechanism comes as a causal chain, with one worked fix and a way to verify it, and the answer ends on a next action. Full files: examples/. Score your own text with brainlint.
## Install
bash
claude plugin install brainres --marketplace wonjangcloud9/brainres
Or inside Claude Code: /plugin marketplace add wonjangcloud9/brainres → /plugin install brainres@brainres.
Use it anywhere (built by scripts/build_dist.py from the same sources):
| Where | File | How |
| claude.ai / Claude desktop | dist/brainres-skill.zip | Customize → Skills → upload |
| ChatGPT, Gemini, any LLM | dist/system-prompt.md | Paste into custom instructions (1,011 bytes, fits ChatGPT's 1,500-character field) |
| Codex and other AGENTS.md readers | dist/AGENTS.md | Copy to your repo root, or append to an existing AGENTS.md |
| Cursor | dist/cursor/brainres.mdc | Copy to .cursor/rules/brainres.mdc |
| Claude Code, without the plugin | skills/brainres/ | cp -R skills/brainres ~/.claude/skills/brainres, then /brainres |
Only the plugin install adds the hooks. With the other routes you get the rule card or the skill, not the per-message reminder.
Once installed, it's always on. A session-start hook adds the rule card once per session, and a short reminder rides along with each message, because instructions fade over long sessions.
Prefer an output style? The plugin also ships one. Run /output-style and pick brainres. It applies the same rules and keeps Claude Code's coding instructions. If you use it, set BRAINRES=off so the card isn't loaded twice. That also turns off the per-message reminder.