copycat

Inventory Next.js routes and scaffold app/<platform-segment> subtrees.

1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/timekeepur/copycat --skill copycat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copycat
Source: https://github.com/timekeepur/copycat/tree/main
Command: npx skills add https://github.com/timekeepur/copycat --skill copycat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates inventory and alignment of Next.js marketing and dashboard views by distinguishing public vs authenticated routes and guiding a user-confirmed naming and platform-scaffolding process.

Core Features & Use Cases

  • Inventory public vs authenticated views and role gates to avoid drift.
  • Generate a canonical view map and derive a consistent platform name and route segment.
  • Scaffold a clean App Router subtree under app/<platform-segment> with isolated legacy routes and shadcn-based blocks.

Quick Start

Identify router type and entry points, inventory routes and roles, derive platform naming, scaffold app/<platform-segment>, and link from the landing page.

Frequently Asked Questions about copycat

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I inventory and separate public vs authenticated Next.js routes?

To inventory Next.js routes, you audit role-based views to differentiate public vs authenticated routes, generating a canonical view map that prevents route drift and validates naming consistency across your application.

What is the best way to scaffold a new App Router subtree for a platform migration?

Scaffolding a new App Router subtree involves creating a clean directory under app/<platform-segment>, isolating legacy routes, and preparing shadcn-based UI blocks to recreate views without disrupting existing routing structures.

How do I plan a shadcn-based UI recreation for existing dashboard views?

Planning a shadcn-based UI recreation requires auditing existing dashboard views, mapping role gates, and deriving a consistent platform name and route segment to ensure accurate component recreation during migration.

Do I need to confirm platform naming before scaffolding App Router subtrees?

Yes, confirming platform naming is required before scaffolding App Router subtrees. The process validates naming consistency first, ensuring the derived platform segment accurately reflects the canonical view map before directory creation.

Can I split auth vs public routes across a new App Router subtree without breaking legacy paths?

Splitting auth vs public routes creates isolated legacy routes within the new App Router subtree. This approach separates authenticated views while preserving original paths, preventing drift during the platform migration process.