ts2moonbit-migration

Port TypeScript modules to MoonBit while preserving the JavaScript API contract.

320|3|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/mizchi/skills --skill ts2moonbit-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ts2moonbit-migration
Source: https://github.com/mizchi/skills/tree/main/lang/ts2moonbit-migration
Command: npx skills add https://github.com/mizchi/skills --skill ts2moonbit-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Port a TypeScript module, library, npm package, or Node service to MoonBit while keeping the same JavaScript API contract, enabling seamless porting with preserved downstream compatibility.

Core Features & Use Cases

  • Orchestrates a MoonBit port workflow by composing three lower-level skills—moonbit-js-binding, translate-programming-language, and moonbit-practice—to preserve the public API across languages and runtimes.
  • Provides a structured migration playbook that yields a JS artifact with the same surface and typings (.d.ts), including a build/publish loop and parity checks.
  • Suitable for migrating TS libraries, Node services, npm packages, or Cloudflare Workers to MoonBit without altering existing consumer behavior.

Quick Start

Prepare your TS project and run the MoonBit migration workflow to generate an indistinguishable JS artifact.

Frequently Asked Questions about ts2moonbit-migration

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

FAQPage Schema
How do I port a TypeScript npm package to MoonBit while keeping the same JavaScript API?

Porting a TypeScript npm package to MoonBit involves orchestrating binding layers to preserve the public API contract. This workflow enforces a boundary adapter and phase 0 contract capture, yielding a JS artifact with the same surface and .d.ts typings for seamless downstream compatibility.

What is the best way to migrate a Node service to MoonBit without breaking existing consumers?

Migrating a Node service to MoonBit safely requires a structured migration playbook with parity checks. By enforcing an idiomatic core and a build/publish loop, it generates a JS artifact with the same surface, preventing alterations to existing consumer behavior.

Can I migrate a Cloudflare Workers TypeScript project to MoonBit and maintain JS typings?

Yes, you can migrate TypeScript Cloudflare Workers to MoonBit. The migration process provides a structured playbook that yields a JS artifact with the same surface and .d.ts typings, ensuring the public API contract remains intact across runtimes.

How does the MoonBit migration workflow preserve TypeScript API contracts?

The MoonBit migration workflow preserves TypeScript API contracts by composing three binding layers—moonbit-js-binding, translate-programming-language, and moonbit-practice. It enforces parity through a boundary adapter and phase 0 contract capture during compilation and publishing.

What do I need to prepare before migrating a TypeScript library to MoonBit?

Before migrating a TypeScript library to MoonBit, you need to prepare your TS project. The migration process then runs a structured workflow to capture the API contract and generate an indistinguishable JS artifact through a build/publish loop with parity checks.