slt-migration

Migrate ratatui, cursive, or textual TUI code to SuperLightTUI v0.20 APIs.

174|6|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/subinium/SuperLightTUI --skill slt-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slt-migration
Source: https://github.com/subinium/SuperLightTUI/tree/main/.agents/skills/slt-migration
Command: npx skills add https://github.com/subinium/SuperLightTUI --skill slt-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you migrate an existing Rust (ratatui/tui or similar) or Python (textual) TUI codebase into SuperLightTUI v0.20 without getting stuck on API differences and broken widget/event mappings.

Core Features & Use Cases

  • Direct API mapping for SLT v0.20: Translate common ratatui widgets, run loop patterns, layout constraints, state patterns, and event handling into SLT equivalents.
  • Version-specific safety: Warns against v0.20-removed APIs and guides you to the correct replacements.
  • Cross-framework mindset shift: Covers the closure-based immediate-mode model versus ratatui’s draw loop, cursive’s callbacks, and textual’s reactive/class-based UI.

Quick Start

Ask your AI: "Migrate my ratatui or cursive (or textual) TUI code to SuperLightTUI v0.20 and map each widget, state pattern, layout constraint, and event handler to the correct SLT v0.20 API."

Frequently Asked Questions about slt-migration

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

FAQPage Schema
How do I port my ratatui TUI code to SuperLightTUI v0.20?

Porting ratatui code to SuperLightTUI v0.20 involves translating your draw loop, widgets, layout constraints, and state patterns into SLT equivalents using immediate-mode Context methods and builders to ensure correct API mapping.

How do I convert textual Python reactive classes into immediate-mode Rust TUI code?

Converting textual Python reactive classes into immediate-mode Rust TUI code requires mapping your class-based UI and reactive state into SLT v0.20 closure-based models and Context methods, replacing the reactive event system with immediate-mode interaction semantics.

What is the best way to migrate cursive callbacks to SuperLightTUI?

Migrating cursive callbacks to SuperLightTUI requires translating callback-based event handling into SLT v0.20 closure-based immediate-mode patterns, updating state threading and input event logic to match the new API structure.

Does SuperLightTUI v0.20 still support the APIs I use in ratatui or cursive?

SuperLightTUI v0.20 removed certain older APIs, so direct equivalents may not exist for every ratatui or cursive component, requiring adoption of immediate-mode Context methods and builders to replace removed functionality safely.

Why does my TUI migration break when targeting SuperLightTUI v0.20?

Your TUI migration breaks when targeting SuperLightTUI v0.20 if you attempt to use removed APIs or fail to translate retained-mode draw loops and callbacks into the required immediate-mode interaction semantics and SLT Context methods.