content/skills/tech-stack-skills/rust-cli-tui-developer/SKILL.md
Expert guidance for building Rust CLI and TUI applications using clap, inquire, and ratatui. Use this skill when creating command-line tools, argument parsers, interactive terminal prompts, or rich terminal UIs in Rust — prefer it over generic Rust advice for any CLI/TUI task.
npx skillsauth add bahayonghang/my-claude-code-settings rust-cli-tui-developerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Execute the Rust CLI/TUI development task described in $ARGUMENTS.
$ARGUMENTS is empty, report an error requesting a description of the desired terminal application.$SKILL_DIR/references/CLI_TUI_GUIDE.md for architectural patterns, library specifics (clap, inquire, ratatui), and common Cargo configurations.Generated Rust code implementing the requested CLI or TUI functionality.
User Request: "Create a basic CLI that accepts a config file path using clap."
Response Strategy: Generate a main.rs using clap::Parser with a config argument, following the patterns in the guide.
cargo add commands were used (e.g., clap --features derive).development
Use only when the user explicitly asks for swarm, subagents, parallel agents, dynamic workflow, multi-agent orchestration, 多智能体编排, or when the task truly needs coordinated research plus implementation plus review plus verification packets. Do not use for ordinary code review, planning-only work, single-line bugfixes, routine audits, or migrations unless orchestration is requested or at least two independent workflow dimensions are present.
development
Run a code quality review focused on maintainability, structure, abstraction quality, file growth, branching complexity, boundary cleanliness, and refactoring opportunities. Use when the user asks for code quality review, code review, maintainability review, architecture quality review, PR code quality feedback, 代码质量审查, 代码质量 review, 可维护性审查, 架构质量审查, or review comments about code structure. Do not use for pure security review, formatting-only review, performance profiling, or implementation tasks unless the user also asks for a code quality review.
development
Plan-first brainstorming workflow that turns an idea into an approved Markdown implementation plan by default. Use when the user wants to brainstorm, design, scope, or plan a feature/spec before implementation. Spark explores project context, asks only blocking questions, writes the plan under the project root's .plannings/YYYY-MM-DD-feature-slug.md path, self-reviews it, and waits for user approval. Create an HTML or visual plan/spec only when the user explicitly asks for HTML, browser-viewable, or visual output; save the paired .html beside the Markdown plan.
development
Run a code quality review focused on maintainability, structure, abstraction quality, file growth, branching complexity, boundary cleanliness, and refactoring opportunities. Use when the user asks for code quality review, code review, maintainability review, architecture quality review, PR code quality feedback, 代码质量审查, 代码质量 review, 可维护性审查, 架构质量审查, or review comments about code structure. Do not use for pure security review, formatting-only review, performance profiling, or implementation tasks unless the user also asks for a code quality review.