[Feature] Implement twig component #239
                
     Open
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Summary
This MR introduces an experimental workflow for exporting Figma designs directly to Twig + Tailwind components.
The goal is to streamline the design-to-code workflow and improve consistency between UI and implementation.
How it works
Component mapping: Each Figma component instance is replaced with a Twig component, using the Figma component’s name as the Twig component name.
Property binding: Figma component properties are converted into Twig attributes.
Component composition: If a Figma component includes a Frame named TwigContent, its content will be rendered as HTML/Tailwind inside the Twig component tags.
Example
You can test it, on the Figma example file: https://www.figma.com/design/2SO4cvRbzKcTIPdY76FEDW/Figma-to-Twig?node-id=2185-255&p=f&m=dev
Notes
This feature is experimental and may evolve based on design and dev feedback.
This feature is enable with a Twig button in tailwind tabs