develop

To turn a Subframe design into production code, fetch the design layout using the get_page_info MCP tool with a URL, ID, or name, then create the corresponding page in your codebase following existing project conventions.

Component syncing fetches the latest presentational code from Subframe only when components do not exist locally, ensuring updated designs blend smoothly with your existing business logic without overwriting local implementations.

Yes, you can wire business logic into Subframe designs by adding data fetching, form handling, and event management to the page, making it interactive and production-ready while keeping existing hooks and state in mind.

Yes, you need MCP tools like get_page_info, list_pages, and get_component_info to locate Subframe designs and components by URL, ID, or name before translating them into codebase pages.

The best way to ensure implemented Subframe pages follow codebase conventions is to fetch designs via MCP, sync components safely, and wire business logic while adhering to existing project patterns, hooks, and state management.

Subframe components only sync when they do not exist locally; if components are already present, syncing is skipped to protect existing presentational code and business logic from being overwritten.