vite-advanced▌
yonatangross/orchestkit · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Advanced configuration for Vite 8 (Rolldown-powered, stable Mar 2026) with Environment API from Vite 7.
Vite Advanced Patterns
Advanced configuration for Vite 8 (Rolldown-powered, stable Mar 2026) with Environment API from Vite 7.
Vite 8: Rolldown-Powered Builds (Default)
Vite 8 replaces esbuild+Rollup with Rolldown (Rust-based unified bundler), delivering 7.7x faster builds and 50% less memory. This is now the default for all new projects.
npm install vite@8 # Direct upgrade
Key improvements:
| Metric | Vite 7 | Vite 8 | Improvement |
|---|---|---|---|
| Build time (Linear) | 46s | 6s | 7.7x faster |
| Dev server startup | ~3s | ~1s | 3x faster |
| HMR updates | ~100ms | ~60ms | 40% faster |
| Memory usage | ~800MB | ~400MB | 50% reduction |
Breaking changes from Vite 7:
build.rollupOptions→build.rolldownOptions(auto-converted with deprecation warning)transformWithEsbuild→transformWithOxc- Plugin
transform()returning JS must addmoduleType: 'js'to return value manualChunksobject form removed — use function form oradvancedChunks'system'/'amd'output formats no longer supported- Lightning CSS is now standard (replaces esbuild for CSS minification)
- Browser target bump: Chrome 107→111, Firefox 104→114, Safari 16.0→16.4
advancedChunks (Replaces manualChunks)
Vite 8 introduces declarative chunk grouping with priority control and size constraints:
export default defineConfig({
build: {
rolldownOptions: {
output: {
advancedChunks: {
groups: [
{ name: 'react-vendor', test: /[\\/]node_modules[\\/](react|react-dom)[\\/]/, priority: 20 },
{ name: 'ui-vendor', test: /[\\/]node_modules[\\/]@radix-ui[\\/]/, priority: 15, minShareCount: 2 },
{ name: 'vendor', test: /[\\/]node_modules[\\/]/, priority: 10, maxSize: 500000 },
],
},
},
},
},
})
Load Read("${CLAUDE_SKILL_DIR}/references/vite8-rolldown.md") for full migration options, benchmarks, advancedChunks syntax, Oxc benefits, and migration checklist.
Environment API (from Vite 7, stable)
Multi-environment support (client/SSR/edge) is first-class:
export default defineConfig({
environments: {
client: { build: { outDir: 'dist/client' } },
ssr: { build: { outDir: 'dist/server', ssr: true } },
},
});
Load Read("${CLAUDE_SKILL_DIR}/references/environment-api.md") for full configuration, per-environment plugins, Builder API, and buildApp hook.
Plugin Development
Hooks for config, transform, resolveId, load, virtual modules, HMR, and environment-aware transforms.
Load Read("${CLAUDE_SKILL_DIR}/references/plugin-development.md") for plugin structure, hook execution order, and advanced patterns.
SSR Configuration
Middleware mode for dev, separate client/server builds for prod, streaming SSR support.
Load Read("${CLAUDE_SKILL_DIR}/references/ssr-configuration.md") for entry points, dev/prod server setup, and streaming patterns.
Build Optimization
Chunk splitting with advancedChunks (Vite 8, preferred) or manualChunks (Vite 7 legacy), tree shaking, minification, and bundle analysis.
Load Read("${CLAUDE_SKILL_DIR}/references/chunk-optimization.md") for chunk strategies, build targets, and optimization checklist.
Quick Reference
| Feature | Vite 8 Status |
|---|---|
| Rolldown bundler | Default (replaces esbuild+Rollup) |
| Environment API | Stable (from Vite 7) |
| ESM-only distribution | Default |
| Node.js requirement | 20.19+ or 22.12+ |
advancedChunks |
New (replaces manualChunks) |
buildApp hook |
Stable (for multi-env plugins) |
createBuilder |
Multi-env builds |
| Oxc integration | Parsing 3x faster than SWC |
Key Decisions
| Decision | Recommendation |
|---|---|
| New projects | Vite 8 (default) |
| Existing production apps | Evaluate Vite 8, use rolldown-vite for gradual migration |
| Multi-env builds | Environment API (environments config) |
| Plugin scope | Use this.environment for env-aware plugins |
| SSR | Middleware mode for dev, separate builds for prod |
| Chunks | advancedChunks for Vite 8, manualChunks for Vite 7 compat |
Related Skills
biome-linting- Fast linting alongside Viteork:react-server-components-framework- SSR integrationedge-computing-patterns- Edge environment buildsork:storybook-testing- Component testing with Vitest
References
Load on demand with Read("${CLAUDE_SKILL_DIR}/references/<file>"):
| File | Content |
|---|---|
vite8-rolldown.md |
Rolldown migration, benchmarks, advancedChunks, Oxc benefits |
environment-api.md |
Multi-environment builds, Builder API, per-env plugins |
plugin-development.md |
Plugin hooks, virtual modules, HMR, env-aware transforms |
ssr-configuration.md |
Entry points, dev/prod servers, streaming SSR |
library-mode.md |
Building publishable npm packages |
chunk-optimization.md |
advancedChunks, manualChunks, tree shaking, bundle analysis |
How to use vite-advanced on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add vite-advanced
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches vite-advanced from GitHub repository yonatangross/orchestkit and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate vite-advanced. Access the skill through slash commands (e.g., /vite-advanced) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★66 reviews- ★★★★★James Patel· Dec 28, 2024
vite-advanced fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Dhruvi Jain· Dec 24, 2024
Keeps context tight: vite-advanced is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Hassan Park· Dec 20, 2024
vite-advanced is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Kiara Kim· Dec 12, 2024
Keeps context tight: vite-advanced is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Aarav Mensah· Dec 8, 2024
vite-advanced has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Kofi Khanna· Nov 27, 2024
vite-advanced fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Aarav Kim· Nov 23, 2024
Useful defaults in vite-advanced — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ishan Gupta· Nov 19, 2024
vite-advanced has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Oshnikdeep· Nov 15, 2024
Registry listing for vite-advanced matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Kaira Robinson· Nov 11, 2024
vite-advanced reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 66