# Cleanup Unused Assets

> Reduce plugin size by scanning resources/icons and removing unreferenced assets.

- Skill: `flutter/cleanup-unused-assets` (Agent Skill)
- Install (CLI): `npx skillmds@latest add flutter/cleanup-unused-assets`
- Raw SKILL.md: https://api.skillmd.com/api/skills/flutter/cleanup-unused-assets/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: flutter (https://skillmd.com/u/flutter)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/flutter/cleanup-unused-assets

---


# Skill: Unused Asset Cleanup

You are tasked with reducing plugin size by removing unused icons, images, and resources.

## Objective
Reduce plugin size by removing unused icons, images, and resources.

## Workflow Instructions

### 1. Baseline
- Run `./gradlew test` and `./gradlew verifyPlugin` to ensure the project is stable.

### 2. Scan Assets
- List all files in `resources/icons` and other asset directories.

### 3. Search Usages
- Check if each asset is referenced in code or `plugin.xml`.

### 4. Remove
- Delete assets with zero references.

### 5. Verify
- Run `./gradlew buildPlugin` and check that the plugin still loads correctly without missing resource exceptions.
- Run `./gradlew testClasses`, `./gradlew test` and `./gradlew verifyPlugin` to ensure no regressions.
- Suggest manual test steps: Check code changes made and write test steps for a user to execute that trigger changed code paths. If needed, add logging statements to verify code paths successfully run.

### 6. Report & Review
- Summarize assets removed.
- **Test Location:** Explicitly state *where* in the IDE user should go to test changed functionality (e.g., "Go to Preferences > Languages & Frameworks > Flutter").
- **Action:** Ask user to review deletions closely.
- **Do not commit or push.**
- Provide a suggested Git commit message (e.g., "Cleanup: Remove unused icon [Icon Name]").