console-ux-designlisted

Create or improve usable command-line and console commands or apps, including Laravel Artisan, Symfony Console, and similar frameworks. Use for command structure, signatures, help, prompts, progress, errors, output, machine formats, automation behavior, and implementation-ready CLI UX. Do not use for web, mobile, native GUI, shell scripting without UX changes, terminal themes, full-screen TUIs, or report-only audits.
ValentinNikolaev/agent-skills · ★ 0 · Web & Frontend · score 70

Install: claude install-skill ValentinNikolaev/agent-skills

## Generated Codex skill — do not edit manually This complete skill and its bundled resources are generated from `agent-plugins/skills/console-ux-design/SKILL.md`. Manual changes in this directory will be overwritten the next time the generator runs. Edit the canonical skill instead. # Console UX Design Design a predictable console interface for people at a terminal and callers in automation. ## Stay inside the console boundary - Create or improve ordinary commands, subcommands, and line-oriented console applications. - Treat Laravel Artisan, Symfony Console, and similar frameworks as examples, not as universal APIs. - Analyze an existing command when that analysis leads to a redesign or implementation-ready change. - Do not turn a report-only audit into a redesign. Do not cover web, mobile, native GUI, terminal-emulator themes, or full-screen terminal user interfaces. - Do not treat shell implementation alone as UX work. Activate only when the command's contract or user experience changes. ## Establish the operating context Before designing, determine: - the user's task, domain vocabulary, command frequency, and cost of mistakes; - novice, expert, and automation journeys; - current command names, signatures, help, output, exit codes, compatibility promises, and tests; - supported platforms, shells, console framework, terminal widths, locales, and character encodings; - TTY and redirected behavior