메뉴
Terminal feature and gap-map maintenance guidance. Use when documenting missing parser/core/host/input/policy/host support, closing TODOs, classifying modern terminal features, or deciding whether a protocol belongs in scope.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Core terminal grid/state guidance for this repository. Use when changing ketraterm-core grid mutation, cursor movement, scrollback, resize/reflow, clusters, tab stops, margins, modes, width policy, pen attributes, or TerminalBuffer behavior.
Terminal emulator feature implementation workflow for this Kotlin repository. Use when adding or changing terminal protocols, parser/core/host behavior, modes, SGR, OSC, CSI, DCS, Unicode, input, rendering contracts, or feature-gap documentation.
Input encoder guidance for this Kotlin terminal repository. Use when adding or changing ketraterm-input keyboard, paste, focus, mouse, host-output, or input mode-bit behavior.
Integration adapter guidance for mapping ketraterm-parser TerminalCommandSink semantics to ketraterm-core TerminalBuffer. Use when changing HostCommandAdapter, parser-to-core wiring, module dependencies, coordinate conversion, or explicit TODO gap handling.
Naming conventions and file layout policy for JVM Terminal (KetraTerm) codebase. Use when creating new classes, renaming files, adding public APIs, application components, or internal adapters.
Parser FSM and protocol dispatch guidance for this terminal emulator. Use when touching ByteClass, AnsiStateMachine, ActionEngine, ParserState, CSI/ESC/OSC/DCS handling, SGR dispatch, charset mapping, UTF-8 recovery, or TerminalParser full byte-stream behavior.
| name | terminal-gap-map |
| description | Terminal feature and gap-map maintenance guidance. Use when documenting missing parser/core/host/input/policy/host support, closing TODOs, classifying modern terminal features, or deciding whether a protocol belongs in scope. |
Use this skill when updating docs/terminal-feature-map.md or docs/terminal-feature-gap-map.md, or deciding how
to classify terminal support.
TODO(parser), TODO(core), TODO(host),
TODO(input), TODO(host), or TODO(policy).DONE(...) only when the claimed scope has implementation and
tests.The target is a modern, secure, state-of-the-art terminal pipeline, not literal full xterm.
Prioritize:
Policy-gate risky response/host-affecting features such as OSC 52 clipboard, DCS query responses, window manipulation, and desktop notifications.