Fix Figma Weave Generating Non-Existent Components

When Figma Weave begins generating design outputs, code blocks, or UI layouts containing non-existent components, it is suffering from model hallucination. Instead of pulling from your active, published Figma libraries or design system tokens, the model invents component names, properties, and variable mappings that do not exist in your workspace.

This behavior typically stems from outdated workspace indexing, context window drift, or ambiguous prompt structures that allow the model to guess rather than verify. Follow these steps to ground Figma Weave in your actual design system data.

1. Force a Re-Index of Your Published Libraries Figma Weave relies on an underlying vector index of your team's published libraries. If you have recently deleted, renamed, or refactored components, the model may still reference cached versions of those elements.

1. Open the main Figma file hosting your primary design system / UI library.
2. Click on the Assets tab in the left sidebar, then click the Library icon (book symbol).
3. If there are any pending changes, click Publish to push the latest updates.
4. In the Figma Weave configuration panel or plugin settings, locate the Linked Libraries list.
5. Toggle the affected library Off, wait 10 seconds, and toggle it back On to force a schema sync.

2. Purge Context to Eliminate Hallucination Drift Model-based generators carry a memory of previous prompts and outputs. If Weave hallucinated a component once, it will continue to reference that fictional component in subsequent generations because it remains in its active session context.

1. End your current generation thread. Do not continue typing in a thread where non-existent components have already been suggested.
2. Start a fresh session or project workspace in Figma Weave.
3. If you are using Weave via an API or custom plugin, clear your local session cache or state to wipe the conversational history buffer.

3. Implement Strict Negative Constraints in Your Prompts To prevent the model from taking creative liberties when it cannot find a perfect match, you must explicitly limit its operational boundaries in your prompt or system configuration.

Modify your system instructions or append a grounding block to your user prompt. Use this exact syntax structure:

`text [CONSTRAINT] Use ONLY components, variants, and variables explicitly defined in the active library. Do not invent, guess, or extrapolate any component names, nesting structures, or design tokens. If a matching component does not exist, return an empty placeholder block labeled 'MISSING: [Component Name]' instead of generating a proxy. `

4. Validate and Repair manifest.json Mappings If you use Figma Weave to generate code from designs (or vice versa) using a custom developer configuration, the tool references a `manifest.json` or mapping configuration file. A broken link here will cause the model to generate fallback components that do not match your actual code base.

1. Open your project's mapping file (often named weave.config.json or manifest.json).
2. Look for any components that are flagged as "unmapped" or contain empty target arrays.
3. Ensure that the component IDs in your code repository map exactly to the Component Keys exported from your Figma file.
4. Run the validation command via your CLI if applicable (e.g., npx weave-cli validate) to catch broken component references before running the model.

5. Simplify the Structural Scope of Your Request When Figma Weave is asked to generate a complex, multi-layered layout in a single prompt, it easily runs out of context tokens or processing depth. To save compute overhead, it will make assumptions and invent components.

Break your request down using component-first modular generation: 1. Instead of asking Weave to "Generate a complete dashboard layout using our library," 2. Start by generating individual sub-layouts: "Generate the navigation sidebar using only our 'Sidebar' component." 3. Once validated, prompt for the next block: "Generate the main metrics grid using only our 'Card' and 'Icon' components."

When to Escalate If Figma Weave consistently invents components even after you have cleared your history, forced a library sync, and applied strict negative constraints, the issue likely points to an upstream database sync failure on Figma's servers.

Check the developer console in Figma (Help > Developer > Show Console) for any 500 or 502 sync errors occurring when Weave attempts to read your design system schema. If these errors persist, contact your company's Figma Enterprise Administrator to verify if your workspace's API access limits have been throttled, or open a support ticket with Figma for backend indexing remediation.