Next.js project scaffold

Create the prepared Next.js base from assets/template/. Keep its route groups, shared workspace shell, configuration ownership, and theme behavior intact while adapting the visible project name.

Inputs and boundaries

• Use the current directory as the project root unless the user explicitly supplies another destination. Derive PROJECT_NAME from that directory's basename and preserve its visible spelling and casing. Do not ask for a name when one is already available.
• Inspect the destination before writing. Preserve unrelated files, editor settings, agent instructions, and skill-installation metadata. Stop before overwriting user-authored project files; this skill creates a new project, not a migration.
• Treat assets/template/ as the source of truth. Copy its files rather than recreating or redesigning them from memory.
• Use Bun and keep bun.lock. Do not initialize Git, deploy, or add a publishing workflow unless requested.
• Keep the five example routes: Home, Work, Contact, Login, and Register. The (workspace) and (auth) folders organize layouts without changing URLs. Login and Register are placeholders; do not imply that authentication exists.
• Add APIs, authentication, databases, stores, services, or additional libraries only when the user requests them or the project needs them.

Procedure

1. Create the project

Run in the destination directory: