メニュー
Develop, review, and explore Rust code with strict adherence to Pragmatic Rust Guidelines. Use when the user mentions Rust, .rs files, Cargo, clippy, rustdoc, or requests Rust architecture, implementation, or review.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | rust-development |
| version | 0.12.0 |
| description | Develop, review, and explore Rust code with strict adherence to Pragmatic Rust Guidelines. Use when the user mentions Rust, .rs files, Cargo, clippy, rustdoc, or requests Rust architecture, implementation, or review. |
| depends_on | {"rust-architect":"0.x","rust-code-reviewer":"0.x","rust-code-explorer":"0.x","rust-developer":"0.x"} |
This skill coordinates Rust development workflows and enforces Rust coding standards and best practices when creating or modifying Rust code.
When asked about generating new code or making code changes to existing code, make
sure that edits are conformant to the Rust guidelines at .claude/skills/rust-development/guidelines.txt if the language to generate is Rust.
Key areas to enforce:
Only add a compliance comment when the user explicitly asks for a compliance annotation or a compliance-focused review. If requested, add:
// Rust guideline compliant {date}
where {date} is the guideline date/version.
Invoke these agents via Agent Runner using .claude/agents/registry.yaml. This keeps Rust delegation registry-enforced and version-audited instead of bypassing the installed agent registry.
rust-architect: Architecture and implementation blueprintsrust-code-reviewer: High-confidence Rust code reviewsrust-code-explorer: Feature tracing and architecture mappingrust-developer: Rust implementation and refactoringTask tool template:
<invoke name="Task">
<parameter name="subagent_type">rust-architect | rust-code-reviewer | rust-code-explorer | rust-developer</parameter>
<parameter name="description">Short description of the Rust work</parameter>
<parameter name="prompt">Detailed Rust task. Require the agent to return fenced JSON using its documented {success,data,error} envelope.</parameter>
</invoke>
This skill activates automatically when:
The detailed guidelines are maintained in .claude/skills/rust-development/guidelines.txt.
Set up a repo-local just task runner with a root Justfile, optional .just/ helper scripts, and curated help, build, fmt, lint, test, and ci recipes. Use when a repo needs just, a Justfile, .just helpers, or when the user mentions task automation, "just build", "just lint", "just fmt", or dropping in a just system.
Create or harden CLIs intended primarily for AI or system consumption and secondarily for humans. Use when designing or implementing a JSON-first CLI with an MCP-ready contract seam, where every command supports machine output, errors are typed and actionable, mutating commands are auditable via corresponding read commands, and external integrations need simulator-backed testing. Do not use for human-first shell utilities, one-off scripts, or text-only CLIs.
Design stateful simulators for AI-facing CLIs that integrate with devices, networks, services, or databases. Use when a CLI needs realistic simulator-backed testing, configurable fault injection, persistent state, and a swappable adapter boundary so the same business logic runs against live and simulated backends. Do not use for shallow mocks, stateless test doubles, or CLIs with no external integration.
Critically review an existing CLI, MCP wrapper, or CLI plan for AI-first contract quality. Use when evaluating whether a CLI is JSON-first, has an MCP-ready contract seam without JSON reshaping, auditably models state changes, uses stateful simulator-backed testing for external integrations, and returns typed actionable errors. Do not use for general style review or human-first shell UX review.
Run CI quality gates with optional auto-fix and PR creation.
Run Codex tasks via the ai_cli Task Tool runner.