This FAQ covers everything from code export to working solo, and will clear up confusion about Shaper’s capabilities and roadmap.

​
Can I load components from another design system?

Yes.

If your design system uses Storybook, Shaper can automatically ingest and display the components inside the tool. This makes it easy to bring in existing UI systems without refactoring.

​
Will AI understand my design system and style guide?

Yes.

Our AI agent reads through the relevant source code, including component files and documentation, to build a contextual understanding of your design system. This helps ensure the output is aligned with your existing styles and standards.

​
Do you support frameworks like Angular or Flutter?

Not at the moment.

Shaper currently supports Next.js (v15) with Tailwind CSS. Expanding support to Angular or Flutter is not on our immediate roadmap, but we’re open to feedback and use-case requests.

​
Does Shaper support mobile app development?

Not directly.

Shaper is focused on web development right now. However, our team also built Gluestack, which is designed for React Native and uses NativeWind. That foundation positions us well to support mobile in the future.

​
How does Shaper handle API calls and dynamic behavior?

Everything just works.

Shaper runs your app in the cloud, so all existing API calls and dynamic logic continue to function. Designers can make edits live without needing to stub or simulate behavior. The result is a real product, not a static mockup.

​
Do you support SCSS or CSS files?

Currently, no.

We’ve optimized Shaper for Tailwind CSS to keep the system consistent and performant. Support for SCSS, plain CSS, or other preprocessors may be considered in the future based on demand.

​
Can we load existing projects into Shaper?

Yes, with some requirements.

If your project is built with Next.js v15 and uses Tailwind CSS, we can help you get started quickly in Shaper. Additional compatibility layers are under development.