coding-fe

To convert Stitch designs into Next.js UI code, provide approved .stitch artifacts and run the conversion. It reads .stitch/metadata.json to generate production-ready route slices, feature components, and mock data for your project.

A route slice in Next.js is a route-ready UI assembled from .stitch/metadata.json using desktop and mobile artifact pairs. It consists of thin layout files and feature components built when the target route does not yet exist in the src/ directory.

To validate design parity when converting Stitch HTML to Next.js, the generated UI is checked against Stitch HTML and PNG exports. This ensures the output thin layout files and components match the approved design artifacts visually and structurally.

Yes, you need a design token file to generate Next.js components from Stitch. The process enforces design tokens from .stitch/DESIGN.md and project standards to ensure the output route slices match the approved design system rules.

No, you cannot use this to update existing Next.js pages if the target already exists in src. It is a create-only design-to-code process that builds route-ready UI exclusively when the target route slice does not yet exist in the source directory.