What problem does it solve? Developers working on the pythinker-code terminal UI need to know where new features belong, how the coordinator/controller architecture is organized, and which visual and interaction rules dialogs must follow, without reading the entire codebase. ## Core Features & Use Cases - Architecture orientation: Explains the PythinkerTUI coordinator, controllers (session events, streaming render, replay, auth), and the components directory layout. - Feature routing: Maps each feature type (slash commands, dialogs, tool renderers, config options, themes) to its correct source directory and test location. - Dialog design spec: Bundles DESIGN.md, the normative visual and keyboard-interaction spec for selectors, toggle lists, input fields, and tab bars. - Use Case: When adding a new provider selector dialog, follow the skill to place it in components/dialogs/, reuse SearchableList, and pass the DESIGN.md checklist before submitting. ## Quick Start Ask the agent to add a new slash command with a searchable selector dialog to the pythinker-code TUI following the write-tui skill.
