Use this plugin when the user wants to hand an accepted Open Design artifact to a Next.js App Router project.
- Decide whether the result should be a route, layout fragment, or reusable component.
- Keep components server-first unless interactivity, browser APIs, or client state require
'use client'. - Preserve the artifact's visual system while adapting image, link, font, and metadata usage to Next.js conventions.
- Prefer Tailwind CSS when the target project already supports it; otherwise keep styling local and easy to move.
- Finish with file placement notes, client/server assumptions, assets, and any data requirements.
- Do not mark the whole tree as client-side unless necessary.
- Do not add framework features unrelated to the artifact handoff.
- Keep route and component boundaries easy to review.