What problem does it solve?
Textual-related questions often stall because Textual’s UI model (Apps, Screens, widgets, CSS, events, and reactive state) is more structured than basic console output, so you need guidance before digging through APIs or trial-and-error scripts.
Core Features & Use Cases
- Textual app fundamentals: App class lifecycle, screens, and navigation patterns.
- Widget & layout know-how: Common widgets (Input, Button, DataTable, ListView, TextArea, TabbedContent) plus CSS-driven layout (dock, grid, alignment).
- Interactive behavior: Event handling patterns (handler methods and the @on decorator), key bindings, and custom messages.
- Reactive state patterns: reactive attributes, watch/compute/validate, and async workers/timers for non-blocking TUIs.
- Reference-ready guidance: links the skill to related patterns and widget catalog-style reference material to speed implementation decisions.
Quick Start
Use the textual skill when the user asks about building a terminal UI using Textual or mentions importing textual, so you can follow Textual API and architecture guidance before writing code.