no-invented-code
Skill39 starsChanged 17 days agoMITView on GitHub
Use whenever writing or suggesting code that calls a function, file, module, package, CLI flag, config key, environment variable, or API endpoint — especially third-party libraries, SDKs, or framework features. Prevents hallucinated APIs by checking the repo and docs before using anything.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- fvkmizel/soulkeeperedited, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- fvkmizel/soulkeeper★ 079% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- plan-firstSkill
- systematic-debuggingSkill
- verify-before-doneSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 7 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Every identifier you use must exist.
- Distinctive: line 11
Before calling or importing something from the codebase:
- Very specific: line 12
Search for it (grep -rn, file search, IDE symbols).
- Distinctive: line 13
Read the file it lives in.
- Distinctive: line 14
Before referencing a file path, confirm the file exists.
- Distinctive: line 15
Use the project's existing helpers instead of inventing new ones with similar names.
- Very specific: line 18
Check the installed version first: package.json / lockfile, requirements.txt / pyproject.toml, go.mod, Cargo.toml.
- Very specific: line 20
Verify the API against one of: the library source in node_modules / site-packages / module cache, official docs for that version (use web …
- Very specific: line 22
If you cannot verify, say so: *"I believe the option is X in v4, but I could not confirm it — please check."*
- Distinctive: line 26
Prefer what the project already uses.
- Very specific: line 29
Check --help, the tool's docs, or existing scripts/config before using a flag or key.
- Distinctive: line 30
Never invent environment variables.
- Very specific: line 39
If you discover a version-specific gotcha (renamed API, breaking change, wrong docs), save it with mem_save so it is not rediscovered next …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
No Invented Code
Every identifier you use must exist. If you have not seen it, check it — or say you have not.
Inside the project
Before calling or importing something from the codebase:
- Search for it (
grep -rn, file search, IDE symbols). Confirm the exact name, signature, and export. - Read the file it lives in. Check argument order, return type, and whether it is async.
- Before referencing a file path, confirm the file exists.
- Use the project's existing helpers instead of inventing new ones with similar names.
Third-party libraries
- Check the installed version first:
package.json/ lockfile,requirements.txt/pyproject.toml,go.mod,Cargo.toml. APIs change between major versions. - Verify the API against one of: the library source in
node_modules/ site-packages / module cache, official docs for that version (use web search when available), or the project's existing usage. - If you cannot verify, say so: "I believe the option is
Xin v4, but I could not confirm it — please check."
Adding a dependency
- Confirm the package name exists and is the right one (watch for look-alike/typosquat names).
- Prefer what the project already uses. Mention every new dependency in your report.
Commands, flags, config keys, env vars
- Check
--help, the tool's docs, or existing scripts/config before using a flag or key. - Never invent environment variables; find where the code reads them.
Red flags — stop and check
- "This library probably has a method for that."
- A function name that sounds right but you have not seen in this codebase.
- Copying a pattern from a different framework or an older major version.
- Mixing APIs from two different SDKs.
Memory
If you discover a version-specific gotcha (renamed API, breaking change, wrong docs),
save it with mem_save so it is not rediscovered next session.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.