uzhussain/copycat

Overview

This skill inventories a Next.js app’s marketing and dashboard views by authenticated vs unauthenticated roles, confirms view names with the user, and plans a shadcn-based clean platform scaffold in a separate App Router folder. It maps public/auth boundaries, proposes clean route names, and scaffolds only the confirmed boilerplate under app/<platform-segment> while keeping legacy routes intact.

How this skill works

The skill scans the Next.js routing tree to identify public pages, authenticated app pages, and role-gated routes, then produces a human-readable view inventory template. After a librarian-style route naming audit, it asks the user to confirm which views to recreate and their final names, then outputs a scaffold plan for a shadcn-first platform subtree under the App Router (app/<platform-segment>) without touching legacy code or auth logic.

When to use it

• Auditing role-based views to separate public vs authenticated UX.
• Planning a clean shadcn UI recreation while keeping legacy routes unchanged.
• Preparing to split auth and public routes into an App Router subtree.
• Performing a route-name / navigation consistency audit before refactor.
• Scaffolding only confirmed views to avoid premature migration work.

Best practices

• Run a discovery pass and route-naming audit before scaffolding anything.
• Confirm every recreated view name with stakeholders (confirmation-first).
• Keep legacy routes isolated and do not import legacy CSS into new layouts.
• Install shadcn components up-front (MCP/CLI) and prefer prescribed blocks.
• Use clear, clean names—avoid New*, *V2, Temp*, or legacy prefixes.

Example use cases

• Map an app that mixes marketing pages and a role-gated dashboard to decide what to re-create.
• Create a clean app/<platform-segment> scaffold using shadcn blocks (sidebar, dashboard, auth).
• Run smoke tests to verify public routes load unauthenticated and auth routes redirect.
• Derive a platform route segment from existing product copy and confirm naming with the product owner.
• Add a landing header dropdown entry that points to the new platform root without removing old links.