Loading...
Loading...
Found 879 Skills
Rust event-driven system programming best practices for async runtimes, channels, sockets, terminals, and concurrency. This skill should be used when writing, reviewing, or refactoring Rust applications with async I/O, multi-threading, terminal interfaces, or network communication. Triggers on tasks involving tokio, async/await, channels, sockets, TTY handling, signals, and streaming I/O.
Use when building IoT applications, sensor networks, or edge devices in Rust. Covers telemetry, protocol buffers, protobuf, CoAP, BLE, Bluetooth, serial communication, GPIO, edge computing, OTA update, firmware, data pipeline, MQTT with rumqttc, offline-first store-and-forward, exponential backoff retry, power management, TLS security, and telemetry publishing.
Use when Rust async programming with tokio, async/await, and futures. Use when writing asynchronous Rust code.
Plan and build production-ready Rust CLI tools using clap for argument parsing, with subcommands, config file support, colored output, and proper error handling. Uses interview-driven planning to clarify commands, input/output formats, and distribution strategy before writing any code.
Use when establishing credibility, overcoming skepticism, or building long-term customer relationships
End-to-end pipeline: find engineering candidates, verify LinkedIn URLs via Crustdata, find emails (Crustdata + GitHub commits), write personalized outreach, create Gmail drafts. Use when someone wants to go from "I need candidates for role X" to ready-to-send drafts. Trigger on: "source and email candidates", "find engineers and draft outreach", "build a candidate pipeline", "find people for [role] and set up emails", "automate candidate outreach", "run the full sourcing pipeline", or any variation where the goal is both finding candidates AND reaching out. Covers the entire loop — use individual skills (engineering-candidate-finder, contact-email-enricher, candidate-copy-drafter) only when the user wants just one part of the pipeline.
Performs comprehensive Rust security review for safe/unsafe boundary issues, memory safety in unsafe blocks, concurrency hazards, panic-induced DoS, FFI safety, and async runtime mistakes. Use when auditing Rust crates, services, or libraries — particularly those with `unsafe`, FFI, or concurrent code.
Embedded Rust skill for bare-metal microcontroller development. Use when using probe-rs or cargo-embed for flashing and debugging, setting up defmt logging, using the RTIC framework, configuring cortex-m-rt startup, writing no_std + no_main firmware, or choosing between panic-halt and panic-semihosting. Activates on queries about embedded Rust, probe-rs, cargo-embed, defmt, RTIC, cortex-m-rt, no_std embedded, or panic handling in embedded Rust.
In new high-stakes engagements (clients, partners, employers), front-load extraordinary output in week 1 to build trust deposits that enable operating with slack afterward. Ordinary performance in week 1 forces you to keep proving yourself for months. Most counter-intuitive when applied to long contracts where pacing seems wise.
Use when users need Rust quantitative SDK or TQSDK Rust capabilities: real-time market data/quote/market depth/K-line/tick, product/contract list, main continuous contract/continuous contract, option chain, contract specification, metadata/direct query, historical data download/cache/CSV/Greeks, trading account/order placement/order cancellation/order status, TargetPosTask/risk control/multi-account/strategy execution, low-latency trading desk, stream/fan-out, replay/backtest/live-sim-replay; also applicable when agents need real-time or historical quantitative data, transaction execution substrate, or trading desk capabilities, even if TQSDK is not explicitly mentioned.
Rust 言語リファレンス。 別名: rustlang, rs (拡張子)、Rust-lang。 TRPL (The Rust Programming Language)、Rust by Example、Reference、 Cargo Book、rustc Book、rustdoc Book、Rustonomicon (Unsafe Rust)、 Edition Guide、Standard Library、Error Index。 所有権、ライフタイム、トレイト、async / await、エラーハンドリング、マクロ。
Start a new learning episode in the self-learning memory system with proper context. Use this skill when beginning a new task that should be tracked for learning from execution patterns.