explain-plugin

Explains how the current plugin works in plain English.

What it does:

• Reads the codebase and generates a beginner-friendly explanation
• Describes what the plugin does from a user's perspective
• Explains the internal flow: plugin → UI → plugin messaging
• Lists key files and their roles

Usage: /explain_plugin

Output: Generates a markdown report at .cursor/reports/explain-plugin.md

Report format:

• What this plugin does — 1-2 sentence summary from user's perspective
• How it works — Plain-English explanation of the flow
• Key files — What each important file does
• Message flow — How plugin and UI communicate
• UI components — What the user sees and interacts with

Steps

1. Read key files

   • manifest.json — plugin name and configuration
   • src/shared/messages.ts — message types between threads
   • src/plugin/main.ts — plugin logic and handlers
   • src/ui/App.tsx — UI components and interactions

2. Analyze the plugin

   • What triggers actions? (button clicks, selection changes)
   • What messages are sent between plugin and UI?
   • What does the UI display?
   • What Figma API operations does it perform?

3. Generate explanation

   • Write in plain English, avoid jargon
   • Use analogies if helpful
   • Focus on "what" and "why", not implementation details

4. Save report

   • Create .cursor/reports/ directory if it doesn't exist
   • Save to .cursor/reports/explain-plugin.md
   • Tell user where to find the report

Approach: Explain as if to someone who has never seen the code. Focus on user-facing behavior first, then internal mechanics. Keep it concise but complete enough to understand the full picture.