Debugging Claude Code's Build-Check Logic: Why Name Search Fails and Structural Footprint Search Fixes It

A developer on r/ClaudeAI reports that Claude Code repeatedly failed to detect existing features, claiming “is X built?” returned “no” four times in a single session — each time the feature already existed. The root cause: the agent searched by name (keywords, synonyms) instead of by structural footprint (routes, schemas, registered tools, scheduled jobs, documented decisions). Names drift; architectural artifacts don’t.
The pattern
Asking “is this feature already built?” triggered a confident “no, here’s how we’d build it,” even when the feature was partially implemented. Each time the user had to push back to extract the real answer. The developer diagnosed that the agent was searching, but using vocabulary-based queries that missed code with different naming conventions.
The rule (structural footprint search)
The synthesized rule forces the agent to search by shape, not name. For example, instead of “find feature X,” it asks “what plugin tools exist?” or “what routes, schemas, or registered jobs match this functionality?” This catches prior code that a name search never would have matched.
Key shift: “Searching by better synonyms is still searching by name. The footprint version catches it (the prior code registered a plugin tool, and ‘what plugin tools exist?’ is a high-signal narrow search).”
Requested feedback from the community
- Hallucination shapes structural footprint search would NOT catch
- Audit-theater patterns where the form is satisfied without substance
- Over-triggering on questions that aren’t actually absence claims
- Confidence amplification: post-audit, agent more confident in conclusions, making wrong-ontology errors harder to catch
- Wrong-ontology rigor: agent searches GraphQL patterns on a REST system, finds nothing, confirms absence
The developer is testing the rule in a separate project for 2–3 weeks before considering a global config. They invite others to share rules that solved “hallucination with rigor” (not just hallucination).
📖 Read the full source: r/ClaudeAI
👀 See Also

Open-Sourced the-vibe-stack: Markdown Rules to Maintain Claude Code Consistency
A developer has open-sourced 'the-vibe-stack' — a set of Markdown rules designed to keep Claude Code on track during long sessions by enforcing a rigid schema. The approach aims to reduce logic drift and token waste while ensuring predictable output.

Code-Graph-MCP: Open Source MCP Server Reduces Claude Code Token Usage by 40-60%
code-graph-mcp is an MCP server that indexes codebases into an AST knowledge graph, replacing multiple grep/read calls with single structured queries. The developer reports 40-60% total session token savings and 80% fewer tool calls per navigation task.

Mímir: A Python Memory System Built on 21 Neuroscience Mechanisms
Mímir is a Python memory system for AI agents that implements 21 cognitive science mechanisms like flashbulb memory and retrieval-induced forgetting. It uses a hybrid BM25 + semantic + date index and shows benchmark improvements including 13% higher tool accuracy on Mem2ActBench versus VividnessMem.

Declawed: A Community-Driven OpenClaw Malware Scanner
Declawed is a new OpenClaw SKILL.md malware scanner focused on detecting arbitrary prompt injection, malicious content, and info stealers in ClawHub skills.