Add Vite to Next.js migration skill#160
Open
policyengine[bot] wants to merge 1 commit into
Open
Conversation
Captures patterns from 2025-year-in-review migration (PR #3): - Vite + react-router-dom → Next.js 16 App Router - YAML → JSON data conversion - Filesystem-based routing with dynamic routes - Tailwind 4 setup differences - Environment variable migration (VITE_ → NEXT_PUBLIC_) - Client vs Server Component patterns Helps future Claude sessions migrate legacy PolicyEngine tools to current Next.js standards. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Captures migration patterns learned from
PolicyEngine/2025-year-in-reviewPR #3, where we migrated from Vite + react-router-dom to Next.js 16 App Router.What's included
New skill:
skills/frontend/vite-to-nextjs-migration-skill/SKILL.mdCovers:
?rawimport)@tailwindcss/postcssWhy this helps
Several legacy PolicyEngine tools still use Vite. This skill provides a systematic migration checklist so future Claude sessions can update them to match current standards (Next.js App Router + Tailwind 4 + ui-kit).
🤖 Generated with Claude Code