← ClaudeAtlas

rust-cli-application-designlisted

Design, implement, review, or refactor a portable Rust command-line application across grammar, runtime architecture, domain boundaries, paths, configuration, output, errors, completions, and tests. Use when the overall CLI contract or several cross-cutting command concerns are in scope. Do not use for adding or changing exactly one command in an established CLI or for non-CLI Rust.
genaptic/skillsets · ★ 1 · Web & Frontend · score 70
Install: claude install-skill genaptic/skillsets
## Outcome Produce a repository-aligned CLI design or change whose user-visible grammar is intentional, whose runtime and domain boundaries are clear, whose filesystem and output behavior is safe for scripts and humans, and whose verification evidence matches what actually ran. ## Compatibility Portable across Claude Code, Codex, and OpenCode. Use the target repository's Rust toolchain, MSRV, edition, lockfile, feature, target, and CI policy; Edition 2024 examples require Rust 1.85 or newer. The workflow may use current primary documentation when network access is allowed, but must continue with an explicit freshness gap when it is not. Native-client compatibility remains unverified until a dated report records the client version and exact source commit. ## Use this skill when - Designing a new Rust CLI or restructuring its parser, application runtime, command dispatch, domain boundary, configuration, or output model. - Reviewing or refactoring several commands for consistent grammar, errors, paths, logging, completions, automation output, or cross-platform behavior. - Establishing a testable CLI contract across help, exit status, stdout/stderr, filesystem effects, configuration precedence, and end-to-end behavior. ## Do not use this skill when - The task is to add or change exactly one command in an existing CLI with an established design; use `rust-cli-command-development`. - The task is a generic Rust library, service, GUI, or build-system change without a C