Problem Description:
When using Figma Make to generate pages, the AI does not use the custom components from my published library that are mapped via Code Connect. Instead, it uses default base components, even though the library is enabled and all components (such as Button, Card, etc.) are mapped and published correctly.
Steps to Reproduce:
Create a Figma component library (e.g., OceanBase Design System) with multiple components (Button, Card, etc.) and map them to code using Code Connect.
Publish the library and enable it in the target file.
In Figma Make, select "Use library in Make".
Enter a prompt such as: "Create a page with a primary button."
The generated page does not use the custom Button component from the library, but instead uses a default base component.
Expected Result:
Figma Make should recognize and use the custom components mapped via Code Connect when generating pages, so that the output is consistent with the design system and can be linked to code.
Actual Result:
Figma Make ignores the custom components and uses default base components, breaking the design-to-code workflow.
Environment:
Code Connect CLI version: [your version, e.g., 1.2.3]
Operating system: macOS
(Optional) Figma file link and screenshots attached
Additional Info:
Code Connect is intended to bridge Figma design and code by mapping components, enabling a seamless design-to-development workflow. Figma Make, as an AI design generator, should ideally leverage these mapped components to ensure generated designs are consistent and ready for code handoff.
If you need more details or access to the Figma file, please let me know.
Problem Description:
When using Figma Make to generate pages, the AI does not use the custom components from my published library that are mapped via Code Connect. Instead, it uses default base components, even though the library is enabled and all components (such as Button, Card, etc.) are mapped and published correctly.
Steps to Reproduce:
Create a Figma component library (e.g., OceanBase Design System) with multiple components (Button, Card, etc.) and map them to code using Code Connect.
Publish the library and enable it in the target file.
In Figma Make, select "Use library in Make".
Enter a prompt such as: "Create a page with a primary button."
The generated page does not use the custom Button component from the library, but instead uses a default base component.
Expected Result:
Figma Make should recognize and use the custom components mapped via Code Connect when generating pages, so that the output is consistent with the design system and can be linked to code.
Actual Result:
Figma Make ignores the custom components and uses default base components, breaking the design-to-code workflow.
Environment:
Code Connect CLI version: [your version, e.g., 1.2.3]
Operating system: macOS
(Optional) Figma file link and screenshots attached
Additional Info:
Code Connect is intended to bridge Figma design and code by mapping components, enabling a seamless design-to-development workflow. Figma Make, as an AI design generator, should ideally leverage these mapped components to ensure generated designs are consistent and ready for code handoff.
If you need more details or access to the Figma file, please let me know.