anti-slop

Topics in the source

• Anti-slop
• Code
• Writing (docs, READMEs, commit messages, PR descriptions, replies)
• Before you finish

Slop is output that looks finished but isn't, or that pads the work with words and code nobody asked for. Hold every change to these rules. Do what was asked, and only that. No extra features, options, config flags, abstraction layers or "future-proofing" the task doesn't need. No stubs. Never leave TODO, FIXME, pass, throw new Error("not implemented"), "implement this", "your logic here" or "... rest of the code". Write the real code, or say plainly what you didn't do and why. No debug leftovers. Remove console.log, print debugging and debugger statements you added. Real logging goes through the project's logger. No commented-out code. Delete it; git keeps history. Comments explain why, not what. Don't narrate code ("This function adds two numbers", "Increment i"). Keep comments that record a reason, a constraint or a non-obvious decision. Match the codebase. Follow the file's naming, structure, error handling and comment density. Reuse existing helpers instead of writing near-duplicates. No new files without a reason. Don't add READMEs, example files, summary markdown or test scaffolding unless asked. Don't swallow errors. No empty catch, no except: pass, no silent fallbacks that

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