AI tool comparison
Context Engineering Reference vs React Doctor
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Tools
Context Engineering Reference
Runnable 5-layer stack that enforces RAG output against retrieved context
75%
Panel ship
—
Community
Paid
Entry
Context Engineering Reference Implementation is an open-source project by Brian Carpio at OutcomeOps that makes a concrete claim: RAG is not enough. The project defines and implements a 5-layer context engineering stack — Corpus, Retrieval, Injection, Output, and Enforcement — where the final Enforcement layer is what separates it from standard retrieval-augmented generation pipelines. The enforcement layer actively verifies that generated content actually reflects what was retrieved, closing the loop on hallucinations that occur when an LLM "knows" something from pretraining that contradicts the retrieved document. The reference implementation runs against Amazon Bedrock and Claude using a Spring PetClinic codebase with Architecture Decision Records as the corpus — making it practical to study with real enterprise artifacts. Launched April 17 and already trending as a Show HN post, the project is winning the framing war around "context engineering as a discipline." As prompting has matured into prompt engineering, RAG is now maturing into something more rigorous. This is one of the cleaner articulations of that shift.
Developer Tools
React Doctor
Catch every anti-pattern your AI agent baked into your React app
75%
Panel ship
—
Community
Paid
Entry
React Doctor is a one-command static analysis tool that scans your React codebase and outputs a health score from 0 to 100 alongside a detailed diagnostic report. Run `npx react-doctor@latest .` and it identifies anti-patterns across six dimensions: state & effects, performance, architecture, security, accessibility, and dead code. It auto-detects your framework (Next.js, Vite, React Native) and React version, adjusting rules accordingly. The tool was built by Million.co—the team behind the Million.js performance library—and is clearly aimed at the post-AI-coding era. Its killer feature might be the "agent instruction installation" mode: it teaches Claude Code, Cursor, and other coding agents the project's quality rules, so future agent-written code conforms to them before React Doctor even runs. It also integrates with GitHub Actions and can post PR comments with health score diffs, making it easy to catch regressions before merge. With 8.7K stars and one of today's fastest-growing GitHub repos, the timing is perfect. Developers are increasingly shipping agent-written React code they didn't review line by line, and React Doctor fills the gap. It's MIT-licensed, requires no config to get started, and the CI integration takes about five minutes to set up.
Reviewer scorecard
“The Enforcement layer is the real insight here — I've seen so many RAG systems where the LLM just ignores the retrieved context and answers from weights anyway. Having a verifiable check that output actually uses retrieval is table stakes for production. This implementation shows exactly how to do it.”
“The GitHub Actions integration with PR health score diffs is the feature I didn't know I needed. Installing it took three minutes and immediately flagged three useEffect anti-patterns Cursor introduced last week.”
“The 5-layer framing is useful for communication but it's mostly reorganizing concepts practitioners already know. The enforcement check adds overhead and the reference implementation is tied to Bedrock — not everyone wants another AWS dependency in their AI stack.”
“Static analysis for React isn't new—ESLint with react-hooks/exhaustive-deps, Biome, and others already catch most of these patterns. The 'health score' framing may encourage false confidence if teams focus on the number rather than the individual findings.”
“Naming and systematizing a practice is how it scales. 'Context engineering' as a discipline with a formal 5-layer model will shape how teams hire, design systems, and evaluate results — just as 'prompt engineering' gave teams a shared vocabulary for something they were already doing intuitively.”
“Teaching agents the rules upfront rather than fixing their output afterward is the right architectural direction. As agent-written code becomes the norm, tools that close the feedback loop at the prompt level will be as important as compilers.”
“For teams building editorial AI tools or knowledge bases, the enforcement layer concept translates directly to brand safety and accuracy guarantees. Knowing your AI isn't wandering off into its own hallucinations is what makes these systems publishable.”
“For designer-developers who use Cursor or v0 to prototype quickly, this is a sanity check that doesn't require deep React expertise. A green health score before shipping is a meaningful confidence boost.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.