Menú
Use the Rust compiler (rustc, cargo) to compile and test code in a way that reduces AI tokens consumption.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Creates professional conventional commit messages based on git changes. Use when user asks to commit, create a commit message, or wants to save changes to git.
Use when working with htmxology — the type-safe HTMX routing framework for Rust/Axum. Covers Route enums, Controller trait, RoutingController composition, template route helpers, as_htmx_attribute(), HtmxRequest detection (classic vs HTMX), Response envelope, out-of-band updates, DisplayDelegate, and ControllerRouter integration. Use when adding routes, creating controllers, building templates with route helpers, or handling HTMX vs classic requests.
This skill should be used when users need help with htmx development, including implementing AJAX interactions, understanding htmx attributes (hx-get, hx-post, hx-swap, hx-target, hx-trigger), debugging htmx behavior, building hypermedia-driven applications, or following htmx best practices. Use when users ask about htmx patterns, server-side HTML responses, or transitioning from SPA frameworks to htmx. (user)
| name | rust-development |
| description | Use the Rust compiler (rustc, cargo) to compile and test code in a way that reduces AI tokens consumption. |
This skill optimizes Rust compilation workflows to minimize token consumption while maintaining full visibility into errors and warnings.
For most development tasks use the rust lsp (rust-analyzer) for real-time feedback. When you need to compile or run tests, use the following patterns to capture only relevant output while discarding verbose messages.
Rust compiler output can be extremely verbose, especially for successful builds or when downloading dependencies. Redirect stdout to /dev/null while preserving stderr for actual errors and warnings.
cargo check 2>&1 >/dev/null | head -100
Use cargo check instead of cargo build when you only need to verify code compiles. It skips code generation and is significantly faster.
cargo build 2>&1 >/dev/null | head -100
For release builds:
cargo build --release 2>&1 >/dev/null | head -100
cargo clippy 2>&1 >/dev/null | head -100
Always run clippy after making changes. All warnings must be addressed.
cargo test 2>&1 >/dev/null | head -150
For a specific test:
cargo test test_name 2>&1 >/dev/null | head -100
For a specific crate in a workspace:
cargo test -p crate-name 2>&1 >/dev/null | head -100
cargo fmt --all
Always run after editing Rust files. No output redirection needed as it produces minimal output.
For large workspaces, target specific crates to reduce compilation scope:
# Check a specific crate
cargo check -p crate-name 2>&1 >/dev/null | head -100
# Build a specific binary
cargo build --bin binary-name 2>&1 >/dev/null | head -100
# Run clippy on a specific crate
cargo clippy -p crate-name 2>&1 >/dev/null | head -100
When errors occur, you may need more context. Use these patterns:
# Get more error lines if truncated
cargo check 2>&1 >/dev/null | head -200
# See full error for a specific issue
cargo check 2>&1 >/dev/null | grep -A 20 "error\[E"
# Count total errors
cargo check 2>&1 >/dev/null | grep -c "^error"
cargo fmt --allcargo check -p <crate> 2>&1 >/dev/null | head -100cargo clippy 2>&1 >/dev/null | head -100cargo test -p <crate> 2>&1 >/dev/null | head -150head -100 or head -150 captures errors while avoiding token bloat2>&1 >/dev/null redirects stderr to the pipe while discarding stdout, ensuring only errors and warnings are captured