skills.rest
crowi
crowiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

crowi-migration

Automate Crowi 2.0 migration from Express/Swig to Next.js and ts-rest.

1.1k|164|Updated Aug 18, 2014
Search Tags:#architecture#migration#nextjs#express#crowi#swig#ts-rest
One-click install
npx skills add https://github.com/crowi/crowi --skill crowi-migration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: crowi-migration
Source: https://github.com/crowi/crowi/tree/main/.claude/skills/migration
Command: npx skills add https://github.com/crowi/crowi --skill crowi-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Crowi 2.0 migration workflow from Express/Swig to Next.js + ts-rest, automating the upgrade process to reduce manual work and human error during major architectural changes.

Core Features & Use Cases

  • Automated migration planning and execution across the legacy codebase and the new architecture (apps/crowi-api, apps/crowi-web, packages, and lib folders).
  • Mapping and transforming old Express/Swig patterns (routes, views) to Fastify + ts-rest endpoints and Next.js components, with validation guided by the specified file globs.
  • Use case: upgrade Crowi v1.x to Crowi 2.0 by applying consistent changes to routes, templates, and models while preserving behavior and data structures.

Quick Start

Initiate the migration workflow by applying the migration plan to Express/Swig sources across lib/routes, lib/views, and client/components.

Frequently Asked Questions about crowi-migration

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

FAQPage Schema
How do I migrate an Express and Swig codebase to Next.js and ts-rest?▼

To migrate Express and Swig to Next.js and ts-rest, apply an automated migration plan that maps legacy routes, views, and models to Fastify endpoints and Next.js components, validating consistency against specified file globs.

What is the best way to upgrade Crowi v1.x to Crowi 2.0 architecture?▼

Upgrading Crowi v1.x to 2.0 requires an end-to-end migration workflow applying consistent architectural changes across apps/crowi-api, apps/crowi-web, and packages while preserving existing behavior and data structures.

How does automated migration pattern mapping work for legacy templates?▼

Automated pattern mapping identifies old Express and Swig patterns in lib/routes and lib/views, generates migration steps, and transforms them into Next.js components and Fastify endpoints.

Can I use this migration workflow for both backend routes and frontend components?▼

This migration workflow targets both backend and frontend, transforming Express routes into Fastify and ts-rest endpoints while converting Swig templates into Next.js components.

What limitations should I expect when mapping old patterns to new equivalents?▼

When mapping old patterns to new equivalents, limitations include preserving behavior and data structures across apps/crowi-api, apps/crowi-web, and packages, with consistency validated strictly against defined file globs.

Related Skills

Explore More Software Engineering Skills→
h-4vokh-4vok

startup-triage

Trace CLI-to-runtime startup paths in diagram-tours and diagnose loading issues.

Community
Advanced
monobaselabsmonobaselabs

pre-commit

Automate typecheck, test, and build steps across monorepo workspaces before commits.

Official
Advanced
abhiunixabhiunix
1

api-endpoint-scaffolder

Scaffold REST API endpoints with route handlers, validation schemas, and test stubs.

Community
Intermediate
MaxcogarMaxcogar

api-endpoint-mapper

Map API endpoints across codebases to reveal backend definitions and frontend calls.

Community
Advanced