What problem does it solve? Generated Next.js projects need their dev servers started, restarted, and validated after code changes, but port conflicts, stale processes, missing dependencies, and template drift make runtime management error-prone. This Skill provides the operational rules for safely controlling a generated project's runtime inside its workspace. ## Core Features & Use Cases - Runtime Lifecycle Control: Start, restart, and stop dev servers from the workspace path, reserving ports against both project records and existing runtime rows to avoid unique-index conflicts. - Log Inspection and Readiness Checks: Classify bounded log output into dependency, compile, port, or application errors, and emit preview-ready events only after the default route responds successfully. - Template Synchronization: Propagate template changes into generated projects and reverse-sync user customizations back to templates with typecheck and audit validation. - Use Case: After an AI edit changes a generated app's CSS, restart the dev server, confirm the new stylesheet hash is served, and only then mark the preview as ready. ## Quick Start Start the generated project's dev server from its workspace path, verify the port is listening and the default route returns HTTP 200, then report the preview as ready.
