Code review & debugging21 categories
Should I add this dependency?
Before `npm install` on something you could write yourself.
Help me decide whether to add this dependency. 1. What would I have to write myself, realistically, to cover only the part I need? 2. What does the library give me beyond that — edge cases, platform quirks, maintenance? 3. What does it cost: bundle size, transitive dependencies, upgrade burden, supply-chain exposure? 4. How hard is it to remove later if it stops being maintained? Give a recommendation, not a balanced list. If it's genuinely marginal, say that and tell me which way you'd lean. Dependency: What I need it for:
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Refactoring and design calls. Cutting code down, naming things properly, and choosing between two workable options.
Related prompts
Delete as much of this as possibleCode that works but feels bigger than the problem.Better names for these thingsWhen you've written `data2`, `handleThing`, or `utils`.Improve these error messagesErrors that say "something went wrong".Critique this API designBefore other people start depending on an interface you're designing.Name this functionYou've called it doThing and you know it.Two fixes, pick oneTwo plausible approaches and no strong feeling about either.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free