Skills Guide

Migrate Pages Router component to App Router

VerifiedSafe

Migrate a React component from Next.js Pages Router to App Router. Handles conversion of data fetching methods (getServerSideProps, getStaticProps), routing patterns, and hooks like useRouter and Head. Use when modernizing legacy Next.js pages to the App Router pattern.

Download and use
Sby Skills Guide Bot
DevelopmentAdvanced
6/2/2026
Claude CodeCursorWindsurf
#nextjs#pages-router#app-router#migration#component-migration

Recommended for

Backend developerClaude CodeCode reviewFrontend developerCursorFullstack developer

Automated summary

This skill migrates Next.js components or pages from the Pages Router to the App Router following a defined architecture.

Strengths

  • Automates conversion of page files and API routes
  • Transforms server-side data methods (getServerSideProps, getStaticProps) into async server components
  • Handles separation of server and client components
  • Automatically creates loading.tsx and error.tsx files

Limitations

  • Requires files to already be compliant with Next.js Pages Router
  • Does not handle complex nested dynamic routing cases
  • Requires manual execution of validation commands
When to use it

When a Next.js project using the Pages Router needs to be migrated to the App Router.

When not to use it

For partial migrations or when the target architecture is not yet clearly defined.

Security analysis

Safe
Quality score85/100

The skill only performs code analysis, file editing, and runs standard build/lint/test commands (tsc, next build, vitest) for validation. No destructive, exfiltrating, or obfuscated actions are involved.

No concerns found

How this analysis is made

Examples

Migrate a page to App Router
Migrate the file pages/products/[id].tsx to the App Router following the architecture documentation.
Convert legacy data fetching
Convert getServerSideProps in components/UserProfile.tsx to async server component pattern.
Full component migration
I need to migrate my component MyComponent from Pages Router to App Router. The file is at src/components/MyComponent.tsx.

name: migration-migrate-component description: "Use when a component needs migration to the target architecture or framework version." user-invocable: true argument-hint: "[component-file]" allowed-tools: Read, Write, Edit, Bash, Glob, Grep

Migrate a Pages Router component/page to App Router following docs/ARCHITECTURE.md sections 5 and 6.

Component: $ARGUMENTS

Steps

  1. Read docs/ARCHITECTURE.md sections 5 and 6.

  2. Analyze the component/page:

    • Count lines (JSX, logic)
    • List: props, state, effects, data fetching methods
    • Check for getServerSideProps, getStaticProps, getStaticPaths
    • Check for useRouter from next/router
    • Check for Head component usage
    • Map who imports this component

  3. Convert routing:

    • pages/xxx.tsx -> app/xxx/page.tsx
    • pages/xxx/[id].tsx -> app/xxx/[id]/page.tsx
    • pages/api/xxx.ts -> app/api/xxx/route.ts (or Server Action)

  4. Convert data fetching:

    • getServerSideProps -> async Server Component (service + adapter)
    • getStaticProps -> async Server Component + revalidate
    • getStaticPaths -> generateStaticParams()
    • Client-side useEffect + fetch -> React Query hook

  5. Determine Server vs Client:

    • Data fetching only? -> Server Component
    • Has hooks, events, browser APIs? -> Client Component
    • Mixed? -> Split into Server page + Client component

  6. Convert imports:

    • useRouter from next/router -> useRouter + usePathname + useSearchParams from next/navigation
    • Head -> metadata export or generateMetadata()

  7. Create siblings:

    • loading.tsx -- skeleton matching page structure
    • error.tsx -- error boundary ('use client' required)

  8. Type all props.

  9. Decompose if > 200 lines.

  10. Validate:

npx tsc --noEmit
npx next build
npx vitest run --passWithNoTests

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/migrate-pages-router-component-to-app-router-mm5t8bcd/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/migrate-pages-router-component-to-app-router-mm5t8bcd' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/migrate-pages-router-component-to-app-router-mm5t8bcd/download' --output '.skill-downloads/migrate-pages-router-component-to-app-router-mm5t8bcd/SKILL.md.part' && mv '.skill-downloads/migrate-pages-router-component-to-app-router-mm5t8bcd/SKILL.md.part' '.skill-downloads/migrate-pages-router-component-to-app-router-mm5t8bcd/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Write, Edit, Bash, Glob, Grep

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/migrate-pages-router-component-to-app-router-mm5t8bcd/SKILL.md' && test -s '.skill-downloads/migrate-pages-router-component-to-app-router-mm5t8bcd/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/migration-migrate-component' && cp -R '.skill-downloads/migrate-pages-router-component-to-app-router-mm5t8bcd' '.claude/skills/migration-migrate-component'

Cursor
test -f '.skill-downloads/migrate-pages-router-component-to-app-router-mm5t8bcd/SKILL.md' && test -s '.skill-downloads/migrate-pages-router-component-to-app-router-mm5t8bcd/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/migration-migrate-component' && cp -R '.skill-downloads/migrate-pages-router-component-to-app-router-mm5t8bcd' '.cursor/skills/migration-migrate-component'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/migrate-pages-router-component-to-app-router-mm5t8bcd'

openskills read 'migrate-pages-router-component-to-app-router-mm5t8bcd'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/migrate-pages-router-component-to-app-router-mm5t8bcd/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot