anti-phantom-symbols

To prevent LLM code hallucination, verify API and import existence by checking methods, class members, and imported modules against your project's codebase and framework documentation before execution.

You can check method existence on class objects by performing runtime verification against the project codebase, ensuring the method signature is valid before the code attempts to call it.

The best way to validate imported modules and symbols is to verify import paths and class constructors against framework documentation, ensuring imported items actually exist before runtime execution.

Runtime verification on class constructors and import paths involves checking the actual existence of APIs and class members in the codebase, preventing issues caused by fictional or missing imports.

Yes, this import validation tool is specifically applicable to code generation and modification workflows, ensuring reliability and correctness by verifying generated APIs and imports against existing codebase documentation.

Generated code fails with missing APIs during execution due to scaffolding hallucination, where plausible code is generated with fictional imports or methods that do not exist in the project's framework documentation.