> ## Documentation Index
> Fetch the complete documentation index at: https://help.emaillove.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Help from Claude or Codex

> Use the Email Love workflow to inspect a Figma file, diagnose email problems, and make careful fixes on the canvas

Claude and OpenAI Codex can do more than build a new email. They can inspect your Figma file, explain what is wrong, and help you fix it.

This is most useful when the problem lives on the canvas: broken structure, clipped text, unexpected spacing, missing components, or an email that will not export.

<Note>
  You need the Email Love workflow and the official remote Figma MCP. [Set up Claude or Codex first](/plugin/ai/agents-in-figma#set-up-your-agent). A write request also needs a Full Figma seat, edit access to the file, and the `use_figma` tool.
</Note>

## Start with a read-only diagnosis

Let the agent inspect before it edits. Give it the Figma file link, the page and frame name, what you expected, and what happened instead.

```text theme={null}
Use the Email Love workflow and the Figma MCP to inspect this email.

Figma file: [link]
Page and frame: [name]
Problem: [what happened]
Expected: [what should have happened]

Do not change the canvas yet. Return:
1. The most likely cause
2. The evidence you found in the file
3. The smallest safe fix
4. Anything I need to verify inside the Email Love plugin
```

This separates diagnosis from repair. You can review the evidence before approving any canvas changes.

## Ask it to make the fix

Once the diagnosis looks right, continue in the same task:

```text theme={null}
Make the smallest safe fix you recommended.

Preserve the existing design system, components, variables, and page structure.
Do not detach instances or hand-build email structure. Verify the result with
a fresh screenshot and tell me exactly what changed.
```

The agent asks for approval before each Figma write. Approve the `use_figma` calls if you want the change to continue.

## Prompts for common jobs

<AccordionGroup>
  <Accordion title="Check my setup">
    ```text theme={null}
    Check whether my Claude or Codex setup can build Email Love emails in Figma.
    Confirm the Email Love workflow is available and the Figma connection includes
    use_figma, get_metadata, and get_screenshot. Do not change any files or canvas content.
    Tell me the exact missing step if the setup is incomplete.
    ```
  </Accordion>

  <Accordion title="Preflight an email before export">
    ```text theme={null}
    Inspect this Email Love email before export: [Figma frame link].
    Do not edit it. Check the root frame, component structure, fixed-height text,
    image blocks, CTA count, alt text, links I still need to verify, mobile risks,
    and anything likely to flatten into an image. Return a prioritized checklist.
    ```
  </Accordion>

  <Accordion title="Diagnose a Figma-to-preview mismatch">
    ```text theme={null}
    Diagnose why this Email Love email looks different in the plugin Preview.

    Figma frame: [link]
    Preview screenshot: [attach image]
    Difference: [describe it]

    Inspect the canvas without changing it. Compare structure, sizing, padding,
    font fallback risk, column widths, and mobile settings. Tell me what can be
    fixed in Figma and what must be checked inside the plugin.
    ```
  </Accordion>

  <Accordion title="Choose between AI Import and migration">
    ```text theme={null}
    Help me choose the right Email Love route for these existing emails: [describe source].
    I have [number] emails and want [one converted email / reusable components / a full design system].
    Compare AI Import, a manual rebuild, and the design-system migration workflow.
    Recommend the smallest route that produces the result I need.
    ```
  </Accordion>

  <Accordion title="Turn a brief into an email plan">
    ```text theme={null}
    Turn this campaign brief into an Email Love email plan before touching Figma.
    Recommend the section order, one primary CTA, copy for each section, a subject
    under 45 characters, and a preheader that adds new information.

    Brief: [paste brief]
    ```
  </Accordion>
</AccordionGroup>

## What the agent can inspect

With the remote Figma MCP connected, Claude or Codex can inspect:

* Pages, frames, layers, components, variables, text, fills, sizing, and auto layout
* Screenshots of the email and individual sections
* Whether the file contains a usable Email Love design system
* Visible structure problems that commonly break preview or export

With `use_figma`, it can also create or update canvas content after you approve the write.

## What you still need to show it

The agent cannot see the Email Love plugin panel or values stored only inside the plugin. Attach a screenshot or paste the exact message when the problem involves:

* An export or API error
* An account, plan, license, or quota message
* A link or mobile setting entered inside the plugin
* A mismatch visible only in Preview
* The final output inside your ESP

Never paste API keys, passwords, license keys, or other secrets into the task. Describe the error and redact sensitive values from screenshots.

## When to contact support

Contact [support@emaillove.com](mailto:support@emaillove.com) when the problem involves your account, billing, quota, a server error, or an ESP connection. Include the exact error, your Figma frame link, and a screenshot with secrets hidden.

For canvas and structure problems, a read-only agent diagnosis is usually the fastest first step.

## Related articles

* [Build Emails in Figma with Claude or Codex](/plugin/ai/agents-in-figma)
* [Troubleshooting and FAQ](/plugin/getting-started/troubleshooting)
* [Import Existing Designs with AI Import](/plugin/ai/ai-import)
* [Migrating an Existing Design System or Template](/plugin/getting-started/migrate-design-system)
* [Export Overview](/plugin/export/overview)