How does the automated migration workflow function?

It uses a /migrate command that triggers a sequence of sub-agents: a planner creates a strategy, an implementer writes the code, and a reviewer validates the changes before they are committed.

Can it handle UI styling and design systems?

Yes, it is pre-configured to apply Crowi's specific theme and design system using Tailwind CSS v4 and shadcn/ui components during the template-to-React conversion.

Which files does this skill target during migration?

The skill specifically monitors and processes legacy routes in lib/routes/, Swig views in lib/views/, and existing client components to ensure a complete architectural move.

What is the primary purpose of the Crowi Migration skill?

It automates the transition of the Crowi Wiki codebase from its legacy stack (Express/Swig) to a modern architecture using Next.js, Fastify, and ts-rest.

Does it support type safety during the migration process?

Yes, it focuses on implementing ts-rest contracts and TypeScript 5.x strict mode to ensure end-to-end type safety across the new API and web applications.

Crowi 2.0 Migration Assistant

Name: Crowi 2.0 Migration Assistant
Author: crowi

bycrowi

•

1,098

API Development

Automates the structural migration of Crowi from legacy Express/Swig to a modern Next.js and ts-rest architecture.

About

The Crowi Migration skill streamlines the complex transition of the Crowi Markdown Wiki codebase to its 2.0 architecture. It facilitates the conversion of Express routes into type-safe ts-rest contracts and Fastify handlers, while transforming Swig templates into modern React components using Next.js 16 and Tailwind CSS. By utilizing specialized sub-agents for planning, implementation, and review, it ensures a consistent and high-quality refactoring process that adheres to Crowi's specific design patterns, Turborepo structure, and strict TypeScript requirements.

Key Features

Integrates with Turborepo and pnpm for managing monorepo workspace updates
1,098 GitHub stars
Enforces Crowi-specific design tokens and styling using Tailwind CSS v4 and shadcn/ui
Converts legacy Express routes to type-safe ts-rest API contracts and Fastify handlers
Transforms Swig HTML templates into modern Next.js 16 pages and React 19 components
Automates the multi-stage migration workflow including planning, implementation, and review

Use Cases

Refactoring legacy wiki routes to a modern API-first architecture using ts-rest
Upgrading project structure to a Turborepo-based monorepo with strict TypeScript typing
Migrating server-side rendered Swig views to a client-side or server-component React environment

About

Key Features

Integrates with Turborepo and pnpm for managing monorepo workspace updates
1,098 GitHub stars
Enforces Crowi-specific design tokens and styling using Tailwind CSS v4 and shadcn/ui
Converts legacy Express routes to type-safe ts-rest API contracts and Fastify handlers
Transforms Swig HTML templates into modern Next.js 16 pages and React 19 components
Automates the multi-stage migration workflow including planning, implementation, and review

Use Cases

Refactoring legacy wiki routes to a modern API-first architecture using ts-rest
Upgrading project structure to a Turborepo-based monorepo with strict TypeScript typing
Migrating server-side rendered Swig views to a client-side or server-component React environment