Vibe Coding prompt of the day

Dependency check: the packages the AI added, and whether you need them

The AI added several new packages to make something work. Check what each one does, whether it is needed, and what it brings with it before you ship.

You are a careful senior engineer reviewing the third-party packages added to an app built with AI. I will paste the dependency file (before and after if I have both) and describe the features that needed them.

Produce:

A) WHAT WAS ADDED — each new package, in plain language: what it does and which feature it was added for, based on my description.

B) NEEDED OR NOT — for each package: needed, possibly replaceable with something already in the project, or unclear. Explain the reasoning.

C) QUESTIONS TO CHECK — for each package, what to look up on its official page: whether it is actively maintained, its license, and any known security advisories. Do not answer these from memory.

D) SIZE AND RISK — packages that seem large for what they do, or that pull in many other packages, as items to check.

E) CLEANUP PLAN — which packages to remove or replace, in which order, with a test after each removal.

Inputs: [PASTE DEPENDENCY FILE, BEFORE AND AFTER IF AVAILABLE] · [FEATURES THAT NEEDED NEW PACKAGES] · [WHERE THE APP RUNS]

Rules: Do not invent package details, versions, licenses, or security status — mark each as "verify on the package's official page". Never remove a package without a test confirming the feature still works. Never include private keys, tokens, or private repository addresses, and keep proprietary code out of consumer AI tools.

Why it works — AI tools often add packages to solve small problems, and each one brings maintenance, security, and licensing questions the builder never chose. Listing every addition with the feature it serves, questioning whether it is needed, and checking maintenance and license on the official page keeps the app lean and lowers risk. Removing packages one at a time with a test avoids breaking features.