terminal-standards

Included with Lifetime

$97 forever

This skill should be used when the user asks about ANSI, VT100, VT220, ECMA-48, ISO 6429, xterm control sequences, terminal capability detection, terminfo, environment variables, alternate screen protocols, SGR colors, OSC, CSI, DCS, terminal graphics, Windows virtual terminal processing, ConPTY, tmux/screen, SSH, or escape-sequence compatibility. PROACTIVELY activate for: escape sequences, terminal standards, capability negotiation, raw ANSI output, xterm protocols, alternate screen, color support, OSC 8 links, OSC 52 clipboard, Kitty/iTerm2 protocols, sixel, and cross-terminal fallback design. Provides: safe protocol rules, negotiation checklists, compatibility warnings, and reference tables.

Design

What this skill does


# Terminal Standards, Escape Sequences, and Capability Negotiation

Use this skill when code emits or parses terminal control sequences, depends on terminal features, or must behave across emulators, multiplexers, and Windows console hosts.

## Standards hierarchy

Think in layers:

1. **Baseline:** printable text, carriage return, newline, backspace, tab.
2. **ECMA-48 / ANSI / ISO 6429:** CSI controls and SGR attributes.
3. **DEC VT lineage:** cursor movement, alternate keypad modes, device status patterns, private modes.
4. **xterm conventions:** alternate screen, mouse modes, focus events, bracketed paste, OSC extensions.
5. **Modern emulator extensions:** Kitty keyboard/graphics, iTerm2 images, sixel, OSC 8 hyperlinks, OSC 52 clipboard, theme queries.
6. **Platform host behavior:** Windows virtual terminal processing, ConPTY, tmux/screen filtering, SSH latency.

The further down this stack you go, the more you need detection, fallbacks, and cleanup.

## Safer defaults

- Prefer framework abstractions and terminfo/capability libraries over hard-coded control sequences.
- Reset styles deliberately; do not rely on terminal defaults after complex SGR output.
- Treat unknown responses, missing responses, and blocked queries as normal.
- Never require clipboard, images, focus events, or extended keyboard protocols for core functionality.
- When enabling a mode, register a cleanup path before continuing.

## Common sequences and caveats

| Feature | Typical sequence | Caveat |
|--|--|--|
| Alternate screen | `CSI ? 1049 h` / `CSI ? 1049 l` | May be disabled or mediated by multiplexers. Cleanup is mandatory. |
| SGR reset | `CSI 0 m` | Reset before exit and after errors. |
| Truecolor | `CSI 38;2;R;G;B m` / `CSI 48;2;R;G;B m` | Downsample to 256/16/no-color when needed. |
| Bracketed paste | `CSI ? 2004 h` / `CSI ? 2004 l` | Parse paste boundaries; disable on exit. |
| SGR mouse | `CSI ? 1006 h` plus tracking modes | Requires parser and coordinate validation. |
| Focus events | `CSI ? 1004 h` | Treat as advisory; may not arrive. |
| OSC 8 links | `OSC 8 ; ; URI ST` | Provide visible URL fallback. |
| OSC 52 clipboard | OSC 52 | Often blocked by terminals, multiplexers, SSH policies, or security settings. |
| DCS passthrough | `DCS ... ST` | Used by multiplexers and some protocols; highly environment-dependent. |
| Terminal title | `OSC 0/2` | Restore or avoid changing titles unexpectedly. |
| Palette queries/changes | OSC 4/10/11 variants | Useful but fragmented; restore changes and time out queries. |

See `references/escape-sequence-field-guide.md` for detailed tables.

## Capability negotiation checklist

- Is stdout a TTY? If not, avoid cursor controls and interactive modes by default.
- Is `TERM` meaningful? Handle `dumb`, empty, and unknown values.
- Is the app inside tmux/screen? Assume some protocols are filtered or need passthrough.
- Is Windows VT processing enabled for classic console APIs?
- Does the library expose color level detection? Prefer it over ad hoc environment parsing.
- Are user overrides available: `--color`, `--no-color`, `--plain`, `--ascii`, `--no-mouse`?
- Are query timeouts bounded so the app does not hang waiting for terminal replies?

## Cleanup contract

If enabling raw mode, alternate screen, mouse tracking, bracketed paste, focus events, cursor hiding, or keyboard protocols, verify cleanup on normal quit, Ctrl-C, panic, exception, fatal error, failed partial initialization, and test assertion failures.

## Reference files

- `references/escape-sequence-field-guide.md` - ANSI/VT/xterm controls and cautions.
- `references/capability-negotiation.md` - Detection and fallback patterns across terminals.

Files: 3

Size: 15.4 KB

Complexity: 36/100

Category: Design

Source: https://github.com/josiahsiegel/claude-plugin-marketplace/tree/main/plugins/tui-master/skills/terminal-standards

Related in Design

contribute

Included

Local-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".

Designscripts

architectural-analysis

Included

User-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).

Designscripts

mcp

Included

Model 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.

Designscripts

react-native-skia

Included

Design, 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.

Designscripts

plaid

Included

Product 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".

Designscripts

nextjs-framer-motion-animations

Included

Adds 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.

Designscripts