# Quick Start Prompt (Condensed Version)

Use this for a quick paste into a new session. For detailed instructions, see `PLUGIN_FEATURES_EXTRACTION_PROMPT.md`.

---

```
I need a comprehensive list of ALL user-facing features for the Divi BodyCommerce plugin. This will be imported into Supabase RAG for n8n agent processing.

## Requirements

1. **Thoroughly explore the entire codebase** - check all modules, renderers, settings, integrations
2. **Extract every user-facing feature** - anything users configure or interact with
3. **Categorize with complete metadata** - see format below
4. **Accurately assign use_case** - don't be too conservative (see guidelines)
5. **Check for duplicates** - ensure each feature appears only once
6. **Organize logically** - group by modules/categories

## Metadata Format

Each feature:
```
- **Feature Name** - Description.
  - Metadata: `module: [MODULE] | component_type: [TYPE] | layer: [LAYER] | platform: [PLATFORM] | category: [CATEGORY] | requires: [DEPS] | use_case: [INTERNAL/EXTERNAL]`
```

**Fields:**
- `module`: Parent module name (use `core` for plugin-wide)
- `component_type`: module, filter_type, template, ui_helper, server_feature, setting, core_feature
- `layer`: frontend, backend, server_side, settings, both
- `platform`: divi_4, divi_5, gutenberg, common (comma-separated for multiple)
- `category`: filtering, rendering, ui, performance, configuration, core
- `requires`: woocommerce, acf, pro (optional, comma-separated)
- `use_case`: **external** (marketing-worthy, user-facing) or **internal** (support-only, fine-grained)

## Use Case Guidelines

**EXTERNAL** (marketing/documentation-worthy):
- Query/filtering capabilities (post types, categories, search, ACF, WooCommerce)
- Display/rendering features (layouts, templates, grid/list, maps)
- Major design customization (loop templates, button styles, grid columns)
- User-facing functionality (Ajax, load more, mobile toggle, sync)
- Integration features (WooCommerce, ACF, WPML, Gutenberg)
- Performance features users configure (caching)

**INTERNAL** (support-only, fine-grained):
- Granular styling (specific padding/margin values, icon sizes, colors)
- Technical details (CSS selectors, element IDs, field mappings)
- Fine-tuning (placeholder text, button text, icon selection)
- Support-only settings (very specific technical configs)

## Exploration Steps

1. Read main plugin file + changelog
2. List directory structure, identify modules
3. For each module: read module.json/config, renderer files, settings components
4. Check integration files (WooCommerce, ACF, etc.)
5. Extract all settings, filter types, display options, templates, UI helpers
6. Assign metadata (especially use_case - don't be too conservative!)
7. Organize into logical sections
8. Check for duplicates

## Output

Create **JSON file** with:
- Array of feature objects
- Each feature with all metadata fields
- `section` field for organization (optional)
- Valid JSON syntax
- No duplicates
- Only user-facing features (exclude internal implementation details)

JSON structure:
```json
{
  "features": [
    {
      "name": "Feature Name",
      "description": "Description",
      "section": "Section Name",
      "module": "ModuleName",
      "component_type": "setting",
      "layer": "frontend",
      "platform": ["common"],
      "category": "ui",
      "requires": null,
      "use_case": "external"
    }
  ]
}
```

Fields:
- `platform`: Always an array (even single value: ["common"])
- `requires`: Array or null (e.g., ["woocommerce"] or null)
- `section`: String or null (for organization)

## Critical Reminders

- **Be thorough** - explore entire codebase systematically
- **Don't be too conservative** - if users configure it, it's likely external
- **Check for duplicates** - same feature might appear in multiple places
- **Complete metadata** - every feature needs all fields
- **User-facing only** - exclude API endpoints, handlers, internal functions

Start by reading the main plugin file and exploring the directory structure.
```