Individual skill
migrate-nextjs
Migrate a Next.js app (App or Pages Router) to pracht: pages, layouts, middleware, API routes, data fetching, metadata, and React to Preact. Use for "migrate from Next.js", "convert my Next app", "port from next to pracht", "switch from next".
skills/migrate-nextjs/SKILL.md
Source commit e7c088a615e0bc16659d7a307fe92910ae6bd546
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 108
- Repository last updated
- Nov 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- cloudflare-workers Repository topic
- framework Repository topic
- full-stack Repository topic
- llms-txt Repository topic
- mcp Repository topic
- preact Repository topic
- ssg Repository topic
- ssr Repository topic
- data Derived category
- engineering Derived category
- engineering-web Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Migrate Next.js to pracht
Migrate in phases: setup → shells → routes → client components → API →
middleware → manifest → patterns → cleanup. Read each Next.js source file
before converting it; never infer from the filename. Prefer the simplest
pracht equivalent, and when a Next.js feature has no equivalent, say so and
propose an alternative instead of inventing one.
MCP: if `pracht dev-mcp` is registered, prefer its `inspect_*`, `generate_*`, `doctor`, and `verify` tools to the CLI.
## Step 0: Assess the source
Read `next.config.*` and `package.json` (React/Next versions, deps), then map
the tree: `app/` (App Router), `pages/` (Pages Router), `middleware.ts`,