figma weave not using local library components

When generating layouts, Figma Weave attempts to map user interface requirements to existing master components located in your document or team libraries. If the engine outputs raw vector shapes, uninstantiated rectangles, or generic buttons instead of swapping in your local component instances, the component matching process has failed. Use these troubleshooting steps to fix component matching.

Quick checks

• Verify that Figma Weave missing in Figma issues aren't preventing the plugin extension from reading canvas memory.
• Check if Figma Weave is down or experiencing API degraded states that disable deep library analysis.
• Confirm that your local components are set as Main Components or published team library assets, rather than simple group selections.

1. Standardize component naming conventions

Figma Weave relies on semantic naming to match prompts with component structures. Ensure your local components use standard slash-naming or clear variant metadata (e.g., `Button/Primary/Large` or `Input/TextField`). Obscure names like `Frame 9402` prevent the AI model from recognizing the node's intent.

1. Expose component variants in the current page

If master components reside on a hidden or archived page inside the file, Weave may fail to index them during prompt construction. Copy key component sets onto an active page or publish them to a shared team library so the engine can scan their component properties.

1. Simplify context and isolate generation prompts

Large prompts requesting full page layouts can exhaust the prompt context buffer, causing Weave to generate basic shapes rather than indexing complex component libraries. Break down your request into section-level prompts (e.g., generate the navigation bar first, then the card grid).

1. Force cache re-indexing

In your Figma document, make a small change to a main component (such as updating its description property) and save or publish. This triggers an index update in Figma's engine, allowing Weave to re-scan the component registry.

Still stuck?

If component mapping continues to fail and prompts result in empty or broken frames, follow our general troubleshooting guide for Figma Weave not generating to inspect session logs and clear local plugin data.

Disclaimer: Figma Weave Support is an independent troubleshooting resource. We are not affiliated with, endorsed by, or connected to Figma, Inc.