Give Claude Code, Codex, or Cursor a JEV Reference File

Updated 5 November 2026 · Standard formula, shown below

Giving Claude Code, Codex, or Cursor a JEV reference file lets a coding assistant consult the file while working, rather than relying on you to repeat its contents in every prompt. The most reliable approach is to place the file inside the project, explain what it is, and point the assistant to its exact path. First confirm that you have the correct JEV file and know which project should use it.

What You’ll Need

The JEV reference file, in a format your editor or assistant can read, such as plain text, Markdown, or PDF. If it is a specialized format, check whether your tool can open it.
The project folder you want the assistant to work on, and permission to add a reference file there.
Claude Code, Codex, or Cursor installed and open to that project. Menu names and supported file handling can differ between versions.
A way to inspect the file locally. Avoid placing passwords, API keys, private customer data, or other secrets in a reference file.

Step-by-Step

Identify the exact file. Check the filename, extension, and contents before sharing it. “JEV” can refer to different things, so do not assume an assistant will know what your particular reference contains. If the file is a download, make sure it is complete and is the intended version.
Open the intended project. In Cursor, open the project folder in the editor. In Claude Code or Codex, start the tool with the project folder as its working directory, following the launch method you normally use. Keeping the reference in the project makes its path clear and helps the assistant find it.
Add the reference file to the project. Copy or move it into a clearly named folder, for example references/jev-reference.pdf or docs/jev-reference.md. Use a descriptive filename and preserve the original if you may need it elsewhere. Do not overwrite an existing file without checking it first.
Check that the file is accessible. Confirm it appears in the project folder or editor’s file list and that you can open it. If the assistant runs in a terminal, check the relative path from the project root. A path such as references/jev-reference.pdf is usually easier to share than a path tied to one computer, such as a personal Downloads folder.
Give the assistant a direct instruction. Start with the file path and explain how it should be used. For example: “Read references/jev-reference.pdf before changing the parser. Use it as the reference for JEV field names, and tell me if a required detail is missing.” This is more dependable than saying only “use the JEV file.”
Use the tool’s file or context controls if needed. In Cursor, you can refer to a project file in chat using the available file-mention or context controls; the exact interaction may vary. In Claude Code and Codex, provide the path in your prompt and make sure the session is running in the project that contains it. If a tool offers an attach-file control, you can use it as an alternative, but still identify the file and its purpose in your prompt.
Ask for a quick confirmation. Before requesting a large change, ask the assistant to summarize the relevant JEV requirements or identify the section it will use. Check that its summary matches the file. If it cannot find or read the file, stop and fix access rather than letting it guess.
Make the instruction reusable when appropriate. If the file is a standing project reference, add a short note to the project’s existing guidance file, such as a README or tool-specific instruction file: give the relative path, what the reference governs, and when to consult it. Use the guidance format supported by your tool, and avoid creating several conflicting instruction files.
Review the result against the source. Ask for the assistant’s changes to cite the relevant section, heading, or page when the file provides one. Open that part of the reference yourself and verify important names, requirements, and edge cases before accepting code or documentation changes.

Common Mistakes

Using a path outside the open project: A file on your desktop or in Downloads may not be available to the current session. Put it in the project or attach it through the tool’s supported controls.
Giving an ambiguous prompt: “Use JEV” does not explain what the file is or which decisions it should guide. Include the path and the relevant task.
Assuming every format is readable: A file may be visible but not extractable, particularly if it is scanned, encrypted, damaged, or in an uncommon format. Confirm that text can be selected or extracted.
Adding a large or unrelated collection: Start with the specific reference the task needs. Extra files can make it harder to identify the right source and may not fit the tool’s context limits.
Trusting an unverified summary: Assistants can miss details or misread tables. Check critical requirements in the original, especially when a file has multiple versions.

Tips

Use a stable, relative path and a filename that makes the document’s purpose obvious.
Tell the assistant whether the file is authoritative, background reading, or only relevant to one part of the task.
For a long document, name the relevant section, page, or topic in your prompt. Ask the assistant to report uncertainty instead of filling gaps with assumptions.
If a PDF is a scan, use a text-searchable version or provide a clean text or Markdown extract when permitted. Keep tables and labels intact where they matter.
When the reference changes, replace it deliberately and update any project guidance that describes its version or location.
Keep private information out of prompts and project files unless you have confirmed that sharing it is appropriate for your setup.

Troubleshooting

The assistant says it cannot find the file: Check the current project or working directory, then verify the relative path and spelling. If the file is outside the project, move it into the project or use a supported attachment method. Give the assistant the corrected path and ask it to confirm access.

It sees the filename but cannot use the contents: Open the file yourself. If it is unreadable, password-protected, or a scanned image, provide an accessible, text-searchable copy if you are allowed to do so. For a large document, extract only the relevant section while retaining enough context to interpret it correctly.

The answer does not match the reference: Ask the assistant to identify the exact section it relied on and compare that section with its answer. Point out the discrepancy and request a correction based on the source. If multiple JEV files exist, specify which one takes precedence.

Cursor or another tool does not include the file automatically: Add the file explicitly through chat context or state its project-relative path in the prompt. Do not assume that opening a project, indexing it, or having the file visible means every conversation will consult it.

Frequently Asked Questions

What does “JEV reference file” mean?
It depends on your project. Identify the specific document and explain what JEV means in your prompt; the assistant cannot reliably infer that from the initials alone.

Should I attach the file or put it in the project?
Either can work if your tool can read it. A project-relative copy is convenient for repeated tasks; an attachment can be simpler for a one-off request.

Do I need to paste the entire file into chat?
No. Refer to the file by path or attach it when supported. Paste a relevant excerpt only if the tool cannot access the file directly.

Can I use a PDF?
Often, if its text is accessible to your tool. Scanned or protected PDFs may need a searchable copy or a permitted text extract.

Will the assistant remember the file in future sessions?
Do not assume so. Keep it in the project and add a concise pointer to the project’s supported instructions if you want future sessions to know where to find it.

What should I do if the assistant makes up a requirement?
Ask it to show the source section, then verify the claim in the file. Correct it with the relevant passage and request that it distinguish documented requirements from assumptions.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.