coding-guidelines
Use when asking about Rust code style or best practices. Keywords: naming, formatting, comment, clippy, rustfmt, lint, code…
Visualize Rust project dependencies as ASCII art. Triggers on: /deps-viz, dependency graph, show dependencies, visualize deps, 依赖图, 依赖可视化, 显示依赖
Claude Code
$ npx -y skills add actionbook/rust-skills --skill rust-deps-visualizer --agent claude-code
Codex
$ npx skills add actionbook/rust-skills --skill rust-deps-visualizer -a codex -y
Cursor
$ npx skills add actionbook/rust-skills --skill rust-deps-visualizer -a cursor -y
Gemini CLI
$ npx skills add actionbook/rust-skills --skill rust-deps-visualizer -a gemini-cli -y
GitHub Copilot
$ npx skills add actionbook/rust-skills --skill rust-deps-visualizer -a github-copilot -y
OpenCode
$ npx skills add actionbook/rust-skills --skill rust-deps-visualizer -a opencode -y
Windsurf
$ npx skills add actionbook/rust-skills --skill rust-deps-visualizer -a windsurf -y
name: rust-deps-visualizer description: "Visualize Rust project dependencies as ASCII art. Triggers on: /deps-viz, dependency graph, show dependencies, visualize deps, 依赖图, 依赖可视化, 显示依赖" argument-hint: "[--depth N] [--features]" allowed-tools: ["Bash", "Read", "Glob"]
Generate ASCII art visualizations of your Rust project's dependency tree.
/rust-deps-visualizer [--depth N] [--features]
**Options:**
my-project v0.1.0 ├── tokio v1.49.0 │ ├── pin-project-lite v0.2.x │ └── bytes v1.x ├── serde v1.0.x │ └── serde_derive v1.0.x └── anyhow v1.x
my-project v0.1.0 ├── tokio v1.49.0 [rt, rt-multi-thread, macros, fs, io-util] │ ├── pin-project-lite v0.2.x │ └── bytes v1.x ├── serde v1.0.x [derive] │ └── serde_derive v1.0.x (proc-macro) └── anyhow v1.x [std]
**Step 1:** Parse Cargo.toml for direct dependencies
cargo metadata --format-version=1 --no-deps 2>/dev/null
**Step 2:** Get full dependency tree
cargo tree --depth=${DEPTH:-3} ${FEATURES:+--features} 2>/dev/null**Step 3:** Format as ASCII art tree
Use these box-drawing characters:
my-project v0.1.0 │ ├─[Runtime]───────────────────── │ ├── tokio v1.49.0 │ └── async-trait v0.1.x │ ├─[Serialization]─────────────── │ ├── serde v1.0.x │ └── serde_json v1.x │ └─[Development]───────────────── ├── criterion v0.5.x └── proptest v1.x
my-project v0.1.0
├── tokio v1.49.0 ████████████ 2.1 MB
├── serde v1.0.x ███████ 1.2 MB
├── regex v1.x █████ 890 KB
└── anyhow v1.x ██ 120 KB
─────────────────
Total: 4.3 MB1. Check for Cargo.toml in current directory 2. Run `cargo tree` with specified options 3. Parse output and generate ASCII visualization 4. Optionally categorize by purpose (runtime, dev, build)
| When | See | |------|-----| | Crate selection advice | m11-ecosystem | | Workspace management | m11-ecosystem | | Feature flag decisions | m11-ecosystem |
Use when asking about Rust code style or best practices. Keywords: naming, formatting, comment, clippy, rustfmt, lint, code…
Internal support skill for actionbook MCP selectors used by Rust documentation research workflows. Use only when another…
Internal support skill for agent-browser CLI workflows used by rust-learner, docs-researcher, and crate-researcher. Use only when…
Internal command support for dynamic Rust crate skill management. Use only when explicitly invoked by /sync-crate-skills,…
Internal maintenance support for checking and fixing generated Rust skill documentation references. Use only when explicitly…
Use when building CLI tools. Keywords: CLI, command line, terminal, clap, structopt, argument parsing, subcommand, interactive,…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.