mockup-graduate

Mockup integration into production involves transforming approved sandbox components into main app code by analyzing existing conventions, wiring routing and state management, installing missing dependencies into the target package, and validating everything against the app's build and tests.

Refactoring mockup components to production conventions is handled by analyzing existing components in the main app and transforming the mockup to match those patterns. This includes aligning routing, state management, and asset wiring to ensure the main app's conventions are respected.

Yes, dependency installation during mockup graduation is handled by installing missing dependencies directly into the target package. This ensures the production-ready code has all required libraries aligned with the main app's setup before validating the integration.

Yes, you can wire routing and state management when moving a mockup to production. The graduation process explicitly handles production patterns, dependencies, routing, and asset wiring to ensure the integrated component functions correctly within the main application architecture.

Production integration validation is performed by running the main app's build and tests after the mockup component is transformed and wired in. This ensures the graduated code respects existing conventions and does not break the target package's existing functionality.

You should not use an automated mockup graduation workflow if your approved variant requires bespoke architectural changes outside standard routing, state management, or asset wiring, as the process focuses on aligning with existing app conventions rather than introducing entirely new structural patterns.