Support project-level component extraction and reuse in Stitch to improve UI consistency across generated screens

When using Google Stitch to generate multiple screens for the same app, UI inconsistencies often appear across the project. This is especially noticeable in foundational design elements such as the TabBar, navigation bar, custom icon sets, logos, as well as overall color usage, corner radius, and typography hierarchy. Without project-level component extraction and reuse, these elements tend to drift stylistically from screen to screen, making it difficult to maintain a consistent design system and increasing the amount of manual correction required. I would like Stitch to support turning key UI elements from existing screens into reusable project-level components, and to prioritize reusing those components or following predefined design rules in future generations, so that visual consistency and long-term design efficiency can be significantly improved.

this, otherwise stitch is only good for initial idea generation afterwards you just move to whatever tool allows you to stick with predefined components…