feat(vinext): add vinext plugin to marketplace

[amondnet]

Summary

• Add vinext plugin for migrating Next.js projects to the Vite-based Next.js reimplementation
• Plugin includes a migrate-to-vinext skill with compatibility scanning, package replacement, Vite config generation, ESM conversion, and deployment setup
• Register vinext in marketplace.json (category: framework) and README.md
• Configure release-please-config.json for independent vinext component versioning

Test plan

• Verify plugins/vinext/.claude-plugin/plugin.json manifest is valid (claude plugin validate plugins/vinext)
• Confirm vinext entry appears correctly in .claude-plugin/marketplace.json
• Check README renders the Vinext section under Framework plugins
• Verify release-please config picks up plugins/vinext as a separate component

---

Summary by cubic

Adds the vinext plugin to the marketplace to migrate Next.js projects to the Vite-based reimplementation. Includes a migrate-to-vinext skill for compatibility checks, package swap, vite config, ESM conversion, and Cloudflare Workers/Nitro deploy setup.

• New Features
  • Added vinext plugin with migrate-to-vinext skill (compat scan, package replacement, vite config, ESM, Cloudflare Workers/Nitro deploy).
  • Registered vinext in .claude-plugin/marketplace.json and README; added plugin manifest with Cloudflare author metadata and skills-lock.json.
  • Enabled independent vinext releases via release-please-config.json and included skill docs with compatibility, config examples, and troubleshooting references.

^{Written for commit 6abc555. Summary will update on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
claude-code-plugins	Ready	Preview, Comment	Mar 31, 2026 3:55pm

[cubic-dev-ai]

No issues found across 9 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

Architecture diagram

sequenceDiagram
    participant User
    participant Agent as Claude / CLI
    participant Registry as Marketplace (.json)
    participant Skill as vinext Skill (Prompt/Docs)
    participant Project as User Next.js Project
    participant VinextCLI as vinext CLI (npx)
    participant CF as Cloudflare / Nitro

    Note over User,CF: NEW: Vinext Migration Workflow

    User->>Agent: "Migrate my project to vinext"
    Agent->>Registry: NEW: Lookup 'vinext' plugin
    Registry-->>Agent: Metadata & source path
    Agent->>Skill: NEW: Load 'migrate-to-vinext' skill

    rect rgb(240, 240, 240)
        Note over Agent,Project: Phase 1: Compatibility Check
        Agent->>Project: Detect package manager & router (app/pages)
        Agent->>VinextCLI: NEW: Run 'vinext check'
        VinextCLI->>Project: Scan for Next.js features
        VinextCLI-->>Agent: Compatibility report & score
    end

    alt NEW: Automated Migration (init)
        Agent->>VinextCLI: NEW: Run 'vinext init'
        VinextCLI->>Project: CHANGED: Add "type": "module" (ESM)
        VinextCLI->>Project: CHANGED: Rename .js configs to .cjs
        VinextCLI->>Project: NEW: Generate vite.config.ts
    else Manual Migration
        Agent->>Project: Replace 'next' with 'vinext' in package.json
        Agent->>Project: Update scripts (next dev -> vinext dev)
    end

    Note over Agent,Project: Phase 2: Verification
    Agent->>VinextCLI: NEW: Run 'vinext dev'
    VinextCLI->>Project: Start Vite-based HMR server
    Project-->>Agent: Dev server ready

    opt NEW: Deployment Setup
        Agent->>VinextCLI: NEW: Run 'vinext deploy'
        VinextCLI->>Project: NEW: Generate wrangler.jsonc
        VinextCLI->>CF: Deploy to Cloudflare Workers
    end

    Agent-->>User: Migration complete confirmation

Loading

[gemini-code-assist]

Code Review

This pull request introduces the vinext plugin, which facilitates the migration of Next.js projects to a Vite-based reimplementation. The changes include adding the plugin to the marketplace, updating the README, and providing comprehensive documentation and skills for the migration process. Feedback was provided regarding a missing author field in the plugin configuration and corrections to version references for Vite and Next.js in the documentation.