migrate-stitches

Migrate Stitches.js code to Stitches RSC by replacing package names and configuring Next.js or Vite build plugins.

2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/artmsilva/stitches-rsc --skill migrate-stitches
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-stitches
Source: https://github.com/artmsilva/stitches-rsc/tree/main/.claude/plugins/stitches-rsc-dev/skills/migrate-stitches
Command: npx skills add https://github.com/artmsilva/stitches-rsc --skill migrate-stitches

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Migrating from Stitches.js to Stitches RSC can be tricky due to API compatibility, the need for a build plugin, and import path changes. This guide provides a concise migration path that aligns code, configurations, and tooling for a smooth transition.

Core Features & Use Cases

  • Guidance to replace @stitches/react with @stitches-rsc/react and @stitches/core with @stitches-rsc/core.
  • Instructions for integrating Next.js or Vite build plugins to enable CSS extraction at build time.
  • Steps to verify migration and ensure styles render correctly with RSC.

Quick Start

Follow the step-by-step migration guide to replace packages, update imports, and configure the build plugin.

Frequently Asked Questions about migrate-stitches

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Stitches.js to Stitches RSC?

To migrate Stitches.js to Stitches RSC, replace @stitches/react with @stitches-rsc/react and @stitches/core with @stitches-rsc/core, then integrate a build plugin for CSS extraction. Update imports and remove runtime CSS where appropriate.

Do I need a build plugin to use Stitches RSC with Next.js or Vite?

Yes, Stitches RSC requires a build plugin like vite-plugin or next-plugin to enable CSS extraction at build time. You must configure the appropriate plugin for your Next.js or Vite setup during the migration process.

What are the limitations when migrating to Stitches RSC?

Stitches RSC migration has limitations around dynamic values and getCssText usage. Additionally, the process enforces token and layer conventions, requiring you to adapt code that previously relied on runtime CSS generation.

Can I use Stitches RSC if my project uses @stitches/core instead of @stitches/react?

Yes, the migration covers projects upgrading from both @stitches/react and @stitches/core. You replace @stitches/core with @stitches-rsc/core and update your import paths accordingly to ensure compatibility.

Why does my Stitches RSC migration require updating import paths?

Import paths must be updated because Stitches RSC uses a different package structure than Stitches.js. Replacing package names ensures the build plugin can correctly extract CSS and render styles in React Server Components.

What's the best way to verify styles render correctly after migrating to Stitches RSC?

After migrating to Stitches RSC, verify styles render correctly by checking that the build plugin extracts CSS properly and tokens and layers follow conventions. Ensure runtime CSS is removed and dynamic values are adapted to fit limitations.