General-purpose router for repo-local Next.js migration and target-architecture work. Use when the request is broad, spans multiple areas, or needs the right combination of migration mapping, foundation, architecture, endpoint, component, business-logic, design, data-fetching, forms, and testing rules.
Use this skill as the entry point for broad Next.js migration or target-architecture work in this repository.
Baseline
Assume Next.js App Router + TypeScript as the default migration target.
Treat this repository's skills/ directory as the source of truth for repo-local Next.js migration conventions.
If the repository is not yet a Next.js App Router codebase, use this skill to plan and guide the migration target, not to pretend the current implementation already matches the target shape.
Load the smallest useful combination of sibling skills instead of reading every skill.
Prefer server-first rendering, thin endpoints, explicit domain boundaries, and accessible UI by default.
Skill Selection Matrix
Need a repo-specific current-to-target mapping, migration order, or file-to-route placement decision -> read ../nextjs-migration-map/SKILL.md
Need initial folder layout, src/ boundaries, or config bootstrap -> read ../nextjs-foundation/SKILL.md
관련 스킬
Need to choose SSG, ISR, or SSR for public pages, articles, careers, or admin surfaces -> read ../nextjs-rendering-strategy/SKILL.md
Need module boundaries, dependency direction, or feature slicing -> read ../nextjs-architecture-patterns/SKILL.md
Need naming, file structure, imports, types, comments, or review rules -> read ../nextjs-code-convention/SKILL.md
Need app/api/**/route.ts, webhook, DTO, status code, or contract guidance -> read ../nextjs-endpoint-rules/SKILL.md
Need server/client component split, composition, or reusable UI structure -> read ../nextjs-component-patterns/SKILL.md
Need use-case, service, repository, validation, or domain logic boundaries -> read ../nextjs-business-logic/SKILL.md
Need visual language, tokens, layout rhythm, states, or design QA -> read ../nextjs-design-system/SKILL.md
Need caching, suspense, revalidation, or fetch ownership -> read ../nextjs-data-fetching/SKILL.md
Need forms, mutations, optimistic UI, or server actions -> read ../nextjs-forms-and-mutations/SKILL.md
Need unit/integration/e2e scope, regression protection, or release checks -> read ../nextjs-testing-and-quality/SKILL.md
Default Working Order
Read migration-map first when translating current repo files into Next.js routes, modules, and rollout phases.
Read foundation if the feature touches project shape or new modules.
Read rendering-strategy when page freshness, SEO, or caching mode is part of the task.
Read architecture before moving business rules across boundaries.
Read the area-specific skill for the concrete task.
Read testing-and-quality before claiming completion.
Delivery Rules
Keep the implementation aligned with the selected sibling skills.
Do not introduce new layers unless the existing skills justify the boundary.
Prefer explicit DTOs, typed props, small helpers, and reviewable diffs.
If a task is mostly one area, switch from this router skill to the specialized skill and continue there.
Reference Map
Read ../nextjs-migration-map/references/page-migration-matrix.md for the current-page to target-route matrix.
Read references/skill-map.md when you need the full invocation map or example combinations.