trim-unused-modules

To optimize app performance by disabling unused Open Mercato modules, the Skill scans `src/modules.ts` to assess active references, imports, and event subscriptions. It proposes disabling unused modules and requires your confirmation before applying changes.

The best way to identify inactive modules is to scan `src/modules.ts` and evaluate module usage based on references, imports, and event subscriptions. This process detects modules not actively used by your standalone app.

Disabling unused Open Mercato modules does not modify package installations or delete database contents. The Skill only proposes disabling modules in `src/modules.ts` after confirming changes with you, ensuring safety.

Active module usages are assessed based on references, imports, and event subscriptions within your standalone app. This ensures only truly unused Open Mercato modules are proposed for disabling in `src/modules.ts`.

You cannot automatically trim unused modules without manual confirmation. The Skill always seeks user confirmation before applying any changes to `src/modules.ts` to ensure core framework dependencies remain enabled.

Removing unused modules from `src/modules.ts` reduces unnecessary processing, clutter, and dependencies. This streamlines performance and resource usage for your standalone Open Mercato app.