tui-troubleshooting
Use this skill when a terminal UI freezes, hangs, shows a blank screen, corrupts terminal state, leaves raw mode stuck, stops responding to input, garbles output, breaks colors/cursor state, fails over SSH/tmux/screen, behaves differently on Windows/ConPTY, or needs deep root-cause analysis for subtle terminal failure modes. PROACTIVELY activate for: TUI freeze, terminal hang, blank TUI, raw mode stuck, stdin paused, no input events, alternate screen stuck, mouse mode stuck, bracketed paste markers, garbled terminal output, corrupted cursor/colors, partial renders, resize races, terminal state cleanup bugs, npm run tui froze, and debugging terminal gotchas. Provides: freeze/hang diagnosis, terminal recovery, startup and cleanup lifecycle checks, platform triage, and fix patterns.
What this skill does
# TUI Troubleshooting: Freezes, Hangs, Blank Screens, and Terminal State Corruption Use this skill when the user reports that a TUI "froze", "hung", "blanked the terminal", "stopped accepting input", "left the terminal broken", or "works in one terminal but not another". Treat these reports as terminal lifecycle failures until proven otherwise. ## First response rule Do not give a shallow checklist. Establish the failure class, inspect startup and cleanup order, and look for a concrete lifecycle bug: 1. Does the app enter raw mode, alternate screen, mouse, focus, or bracketed paste? 2. Is every mode restored on normal exit, Ctrl-C, exception, panic, rejected promise, and early return? 3. Is stdin flowing after terminal setup? 4. Does the app render and flush at least one frame before waiting on async work or input? 5. Can logs, stderr, background tasks, or child processes write into the same terminal surface? 6. Does the bug reproduce only in tmux, SSH, Windows/ConPTY, CI, or a non-TTY pipe? ## High-probability freeze causes Prioritize these before exotic terminal protocol issues: - **Raw mode without restore.** Echo is disabled and line editing is gone, making the shell look frozen after a crash or early return. - **Paused stdin never resumed.** In Node, `process.stdin.pause()` followed by raw mode without `resume()` prevents `data` events; the UI may wait forever. - **Missing first render.** The app enters alternate screen/raw mode, starts an async status check, and never flushes an initial frame, so users see a blank screen. - **Blocking startup work.** Synchronous file/network/process calls run before the first draw and starve the event loop or render loop. - **Input mode mismatch.** The code waits for line-oriented input while stdin is raw, or waits for raw key events while stdin is cooked or paused. - **Cleanup mode leak.** Alternate screen, mouse reporting, focus events, or bracketed paste remain enabled after exit. ## Minimal diagnostic posture Ask for or inspect: - Language/framework and terminal library. - Startup sequence from process start through first render. - Cleanup/guard/finally/defer/Drop/atexit/signal handlers. - Whether stdin/stdout/stderr are TTYs. - Whether failure occurs locally, over SSH, in tmux/screen/Zellij, on Windows, or in CI. - Raw terminal symptoms: echo off, cursor hidden, blank alternate screen, paste wrappers, mouse clicks swallowed, garbled sequences. ## Recovery commands for users When a terminal is stuck, tell the user how to recover before deeper debugging: ```sh stty sane reset printf '\033[?1049l\033[?25h\033[?1000l\033[?1002l\033[?1003l\033[?1006l\033[?2004l\033[?1004l\033[0m' ``` On Windows PowerShell, closing the tab is sometimes the fastest recovery when a child process left ConPTY in a bad state. ## Fix pattern to prefer Every TUI should use one lifecycle owner: 1. Verify TTY or choose non-TUI mode. 2. Install cleanup guards first. 3. Enter alternate screen/raw mode and optional mouse/paste/focus modes. 4. Resume/ref stdin if raw key events are needed. 5. Render and flush an initial frame immediately. 6. Start async work after the first frame. 7. Route logs away from the controlled terminal surface. 8. Restore modes in reverse order exactly once. ## Reference files - `references/freeze-hang-diagnosis.md` - Root causes, symptoms, diagnostics, fix sketches, and prevention patterns for startup and runtime hangs. - `references/terminal-state-corruption.md` - Garbled display, wrong colors, cursor bugs, partial renders, interleaved writes, and resize/render races. - `references/diagnostic-playbook.md` - Decision trees with concrete commands for freezes, stuck terminal state, no input, SSH/tmux, Windows, and garbled output.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.