strict-api

Topics in the source

• Strict API Verification
• Overview
• The Only Rule
• What This Blocks
• Workflow
• Anti-Patterns
• Cross-References

Inventing a function that doesn't exist is the opposite of efficiency. You wrote a line that looks minimal. You shipped a bug that takes an hour to debug. The true minimal path is: use only what is provably there. This skill is a reality-check layer applied before any code is written. It is not about being slow — it is about being correct the first time. Use it alongside minimalist when the user wants both less code and verified code. Before you write any function call, import, or method access, you must be able to answer: "Does this exist in the version the user is running?" If the answer is "probably" or "I think so" — stop. You don't know. Say so. Made-up methods: fs.readFileLines() does not exist in Node.js. path.combine() is .NET, not Node.js. csv.readcsv() is pandas, not Python's csv module. Writing these is not minimal code — it is confident garbage. Framework confusion. Every framework has a twin that sounds like it: rendertemplate (Flask) vs render() (Django) useForm() (react-hook-form) vs nothing built into React app.listen() (Express) vs server.listen() (raw Node.js http) Deprecated APIs. Writing a deprecated method is writing code that will break on the next upgrade. 1.

This is an excerpt. Refer to the complete source and its current requirements.