Agent skill

Rust Patterns

by affaan-m in affaan-m/ECC

Patrones idiomáticos de Rust, ownership, manejo de errores, traits, concurrencia y buenas prácticas para construir aplicaciones seguras y eficientes.

MITAuto-check passed

Install Rust Patterns

skills CLI
$ npx skills add affaan-m/ECC --skill rust-patterns -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install affaan-m/ECC rust-patterns --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/docs/es/skills/rust-patterns .claude/skills/rust-patterns && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
rust-patterns
GitHub stars
274k
Token cost
~3.5k tokens
SKILL.md length
428 words
Files
1
Skills in repo
657
Repo updated
First seen
Licence
MIT

At a glance

Patrones idiomáticos de Rust, ownership, manejo de errores, traits, concurrencia y buenas prácticas para construir aplicaciones seguras y eficientes.

  • SKILL.md covers Cuándo Usar, Cómo Funciona, Principios Fundamentales and Manejo de Errores, plus 7 more sections
  • Calls cargo

What it does

Rust Patterns is an agent skill from affaan-m/ECC. Patrones idiomáticos de Rust, ownership, manejo de errores, traits, concurrencia y buenas prácticas para construir aplicaciones seguras y eficientes.

Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Rust. The repository describes itself as: The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond. The licence is MIT.

Example prompts

  • “Use the rust-patterns skill to patrone idiomáticos de Rust, ownership, manejo de errores, traits, concurrencia y buenas prácticas para construir…”
  • “/rust-patterns”

What it can do on your machine

Read from SKILL.md and the folder at commit ef648e0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • cargo

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Rust Patterns loads about 3.5k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 428 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~41
When it runs · the whole SKILL.md, loaded when a task matches
~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from affaan-m/ECC at commit ef648e0, republished under its MIT licence (© affaan-m). 428 words, ~3,478 tokens.

Download SKILL.mdSave it as .claude/skills/rust-patterns/SKILL.md (or your agent's skills folder).
name
rust-patterns
description
Patrones idiomáticos de Rust, ownership, manejo de errores, traits, concurrencia y buenas prácticas para construir aplicaciones seguras y eficientes.
origin
ECC

Patrones de Desarrollo Rust

Patrones idiomáticos y buenas prácticas de Rust para construir aplicaciones seguras, eficientes y mantenibles.

Cuándo Usar

  • Escribir código Rust nuevo
  • Revisar código Rust
  • Refactorizar código Rust existente
  • Diseñar la estructura de crates y la organización de módulos

Cómo Funciona

Este skill refuerza las convenciones idiomáticas de Rust en seis áreas clave: ownership y borrowing para prevenir data races en tiempo de compilación, propagación de errores con Result/? usando thiserror para bibliotecas y anyhow para aplicaciones, enums y pattern matching exhaustivo para hacer imposibles los estados inválidos, traits y genéricos para abstracciones de costo cero, concurrencia segura con Arc<Mutex<T>>, canales y async/await, y superficies pub mínimas organizadas por dominio.

Principios Fundamentales

1. Ownership y Borrowing

El sistema de ownership de Rust previene data races y bugs de memoria en tiempo de compilación.

rust
// Bien: Pasar referencias cuando no se necesita el ownership
fn process(data: &[u8]) -> usize {
    data.len()
}

// Bien: Tomar ownership solo cuando se necesita almacenar o consumir
fn store(data: Vec<u8>) -> Record {
    Record { payload: data }
}

// Mal: Clonar innecesariamente para evitar el borrow checker
fn process_bad(data: &Vec<u8>) -> usize {
    let cloned = data.clone(); // Costoso — solo tomar prestado
    cloned.len()
}
Usar Cow para Ownership Flexible
rust
use std::borrow::Cow;

fn normalize(input: &str) -> Cow<'_, str> {
    if input.contains(' ') {
        Cow::Owned(input.replace(' ', "_"))
    } else {
        Cow::Borrowed(input) // Costo cero cuando no se necesita mutación
    }
}

Manejo de Errores

Usar Result y ? — Nunca unwrap() en Producción
rust
// Bien: Propagar errores con contexto
use anyhow::{Context, Result};

fn load_config(path: &str) -> Result<Config> {
    let content = std::fs::read_to_string(path)
        .with_context(|| format!("failed to read config from {path}"))?;
    let config: Config = toml::from_str(&content)
        .with_context(|| format!("failed to parse config from {path}"))?;
    Ok(config)
}

// Mal: Causa panic en caso de error
fn load_config_bad(path: &str) -> Config {
    let content = std::fs::read_to_string(path).unwrap(); // ¡Panic!
    toml::from_str(&content).unwrap()
}
Errores de Biblioteca con thiserror, Errores de Aplicación con anyhow
rust
// Código de biblioteca: errores estructurados y tipados
use thiserror::Error;

#[derive(Debug, Error)]
pub enum StorageError {
    #[error("record not found: {id}")]
    NotFound { id: String },
    #[error("connection failed")]
    Connection(#[from] std::io::Error),
    #[error("invalid data: {0}")]
    InvalidData(String),
}

// Código de aplicación: manejo de errores flexible
use anyhow::{bail, Result};

fn run() -> Result<()> {
    let config = load_config("app.toml")?;
    if config.workers == 0 {
        bail!("worker count must be > 0");
    }
    Ok(())
}
Combinadores de Option en Lugar de Matching Anidado
rust
// Bien: Cadena de combinadores
fn find_user_email(users: &[User], id: u64) -> Option<String> {
    users.iter()
        .find(|u| u.id == id)
        .map(|u| u.email.clone())
}

// Mal: Matching profundamente anidado
fn find_user_email_bad(users: &[User], id: u64) -> Option<String> {
    match users.iter().find(|u| u.id == id) {
        Some(user) => match &user.email {
            email => Some(email.clone()),
        },
        None => None,
    }
}

Enums y Pattern Matching

Modelar Estados con Enums
rust
// Bien: Los estados imposibles son irrepresentables
enum ConnectionState {
    Disconnected,
    Connecting { attempt: u32 },
    Connected { session_id: String },
    Failed { reason: String, retries: u32 },
}

fn handle(state: &ConnectionState) {
    match state {
        ConnectionState::Disconnected => connect(),
        ConnectionState::Connecting { attempt } if *attempt > 3 => abort(),
        ConnectionState::Connecting { .. } => wait(),
        ConnectionState::Connected { session_id } => use_session(session_id),
        ConnectionState::Failed { retries, .. } if *retries < 5 => retry(),
        ConnectionState::Failed { reason, .. } => log_failure(reason),
    }
}
Matching Exhaustivo — Sin Comodín en Lógica de Negocio
rust
// Bien: Manejar cada variante explícitamente
match command {
    Command::Start => start_service(),
    Command::Stop => stop_service(),
    Command::Restart => restart_service(),
    // Agregar una nueva variante fuerza su manejo aquí
}

// Mal: El comodín oculta nuevas variantes
match command {
    Command::Start => start_service(),
    _ => {} // Ignora silenciosamente Stop, Restart y variantes futuras
}

Traits y Genéricos

Aceptar Genéricos, Retornar Tipos Concretos
rust
// Bien: Entrada genérica, salida concreta
fn read_all(reader: &mut impl Read) -> std::io::Result<Vec<u8>> {
    let mut buf = Vec::new();
    reader.read_to_end(&mut buf)?;
    Ok(buf)
}

// Bien: Bounds de traits para múltiples restricciones
fn process<T: Display + Send + 'static>(item: T) -> String {
    format!("processed: {item}")
}
Trait Objects para Dispatch Dinámico
rust
// Usar cuando se necesitan colecciones heterogéneas o sistemas de plugins
trait Handler: Send + Sync {
    fn handle(&self, request: &Request) -> Response;
}

struct Router {
    handlers: Vec<Box<dyn Handler>>,
}

// Usar genéricos cuando se necesita rendimiento (monomorfización)
fn fast_process<H: Handler>(handler: &H, request: &Request) -> Response {
    handler.handle(request)
}
Patrón Newtype para Seguridad de Tipos
rust
// Bien: Tipos distintos previenen mezclar argumentos
struct UserId(u64);
struct OrderId(u64);

fn get_order(user: UserId, order: OrderId) -> Result<Order> {
    // No se pueden intercambiar accidentalmente user ID y order ID
    todo!()
}

// Mal: Fácil intercambiar argumentos
fn get_order_bad(user_id: u64, order_id: u64) -> Result<Order> {
    todo!()
}

Structs y Modelado de Datos

Patrón Builder para Construcción Compleja
rust
struct ServerConfig {
    host: String,
    port: u16,
    max_connections: usize,
}

impl ServerConfig {
    fn builder(host: impl Into<String>, port: u16) -> ServerConfigBuilder {
        ServerConfigBuilder { host: host.into(), port, max_connections: 100 }
    }
}

struct ServerConfigBuilder { host: String, port: u16, max_connections: usize }

impl ServerConfigBuilder {
    fn max_connections(mut self, n: usize) -> Self { self.max_connections = n; self }
    fn build(self) -> ServerConfig {
        ServerConfig { host: self.host, port: self.port, max_connections: self.max_connections }
    }
}

// Uso: ServerConfig::builder("localhost", 8080).max_connections(200).build()

Iteradores y Closures

Preferir Cadenas de Iteradores sobre Bucles Manuales
rust
// Bien: Declarativo, lazy, composable
let active_emails: Vec<String> = users.iter()
    .filter(|u| u.is_active)
    .map(|u| u.email.clone())
    .collect();

// Mal: Acumulación imperativa
let mut active_emails = Vec::new();
for user in &users {
    if user.is_active {
        active_emails.push(user.email.clone());
    }
}
Usar collect() con Anotación de Tipo
rust
// Recolectar en diferentes tipos
let names: Vec<_> = items.iter().map(|i| &i.name).collect();
let lookup: HashMap<_, _> = items.iter().map(|i| (i.id, i)).collect();
let combined: String = parts.iter().copied().collect();

// Recolectar Results — cortocircuita al primer error
let parsed: Result<Vec<i32>, _> = strings.iter().map(|s| s.parse()).collect();

Concurrencia

Arc<Mutex<T>> para Estado Mutable Compartido
rust
use std::sync::{Arc, Mutex};

let counter = Arc::new(Mutex::new(0));
let handles: Vec<_> = (0..10).map(|_| {
    let counter = Arc::clone(&counter);
    std::thread::spawn(move || {
        let mut num = counter.lock().expect("mutex poisoned");
        *num += 1;
    })
}).collect();

for handle in handles {
    handle.join().expect("worker thread panicked");
}
Canales para Paso de Mensajes
rust
use std::sync::mpsc;

let (tx, rx) = mpsc::sync_channel(16); // Canal acotado con backpressure

for i in 0..5 {
    let tx = tx.clone();
    std::thread::spawn(move || {
        tx.send(format!("message {i}")).expect("receiver disconnected");
    });
}
drop(tx); // Cerrar el sender para que el iterador rx termine

for msg in rx {
    println!("{msg}");
}
Async con Tokio
rust
use tokio::time::Duration;

async fn fetch_with_timeout(url: &str) -> Result<String> {
    let response = tokio::time::timeout(
        Duration::from_secs(5),
        reqwest::get(url),
    )
    .await
    .context("request timed out")?
    .context("request failed")?;

    response.text().await.context("failed to read body")
}

// Lanzar tareas concurrentes
async fn fetch_all(urls: Vec<String>) -> Vec<Result<String>> {
    let handles: Vec<_> = urls.into_iter()
        .map(|url| tokio::spawn(async move {
            fetch_with_timeout(&url).await
        }))
        .collect();

    let mut results = Vec::with_capacity(handles.len());
    for handle in handles {
        results.push(handle.await.unwrap_or_else(|e| panic!("spawned task panicked: {e}")));
    }
    results
}

Código Unsafe

Cuándo Unsafe Es Aceptable
rust
// Aceptable: Frontera FFI con invariantes documentados (Rust 2024+)
/// # Safety
/// `ptr` must be a valid, aligned pointer to an initialized `Widget`.
unsafe fn widget_from_raw<'a>(ptr: *const Widget) -> &'a Widget {
    // SAFETY: el llamador garantiza que ptr es válido y alineado
    unsafe { &*ptr }
}

// Aceptable: Ruta crítica de rendimiento con prueba de corrección
// SAFETY: index is always < len due to the loop bound
unsafe { slice.get_unchecked(index) }
Cuándo Unsafe NO Es Aceptable
rust
// Mal: Usar unsafe para evadir el borrow checker
// Mal: Usar unsafe por conveniencia
// Mal: Usar unsafe sin un comentario Safety
// Mal: Hacer transmute entre tipos no relacionados
Show full SKILL.md (174 more words)Show less

Sistema de Módulos y Estructura de Crates

Organizar por Dominio, No por Tipo
text
my_app/
├── src/
│   ├── main.rs
│   ├── lib.rs
│   ├── auth/          # Módulo de dominio
│   │   ├── mod.rs
│   │   ├── token.rs
│   │   └── middleware.rs
│   ├── orders/        # Módulo de dominio
│   │   ├── mod.rs
│   │   ├── model.rs
│   │   └── service.rs
│   └── db/            # Infraestructura
│       ├── mod.rs
│       └── pool.rs
├── tests/             # Pruebas de integración
├── benches/           # Benchmarks
└── Cargo.toml
Visibilidad — Exponer el Mínimo
rust
// Bien: pub(crate) para compartir internamente
pub(crate) fn validate_input(input: &str) -> bool {
    !input.is_empty()
}

// Bien: Re-exportar la API pública desde lib.rs
pub mod auth;
pub use auth::AuthMiddleware;

// Mal: Hacer todo pub
pub fn internal_helper() {} // Debería ser pub(crate) o privado

Integración con Herramientas

Comandos Esenciales
bash
# Construir y verificar
cargo build
cargo check              # Verificación de tipos rápida sin codegen
cargo clippy             # Lints y sugerencias
cargo fmt                # Formatear código

# Pruebas
cargo test
cargo test -- --nocapture    # Mostrar salida de println
cargo test --lib             # Solo pruebas unitarias
cargo test --test integration # Solo pruebas de integración

# Dependencias
cargo audit              # Auditoría de seguridad
cargo tree               # Árbol de dependencias
cargo update             # Actualizar dependencias

# Rendimiento
cargo bench              # Ejecutar benchmarks

Referencia Rápida: Modismos Rust

ModismoDescripción
Tomar prestado, no clonarPasar &T en lugar de clonar a menos que se necesite el ownership
Hacer estados ilegales irrepresentablesUsar enums para modelar solo estados válidos
? en lugar de unwrap()Propagar errores, nunca causar panic en biblioteca/producción
Parsear, no validarConvertir datos no estructurados a structs tipados en la frontera
Newtype para seguridad de tiposEnvolver primitivos en newtypes para prevenir intercambio de argumentos
Preferir iteradores sobre buclesLas cadenas declarativas son más claras y frecuentemente más rápidas
#[must_use] en ResultsAsegurar que los llamadores manejen los valores de retorno
Cow para ownership flexibleEvitar asignaciones cuando el borrowing es suficiente
Matching exhaustivoSin comodín _ para enums críticos de negocio
Superficie pub mínimaUsar pub(crate) para APIs internas

Anti-Patrones a Evitar

rust
// Mal: .unwrap() en código de producción
let value = map.get("key").unwrap();

// Mal: .clone() para satisfacer el borrow checker sin entender por qué
let data = expensive_data.clone();
process(&original, &data);

// Mal: Usar String cuando &str es suficiente
fn greet(name: String) { /* debería ser &str */ }

// Mal: Box<dyn Error> en bibliotecas (usar thiserror en su lugar)
fn parse(input: &str) -> Result<Data, Box<dyn std::error::Error>> { todo!() }

// Mal: Ignorar advertencias must_use
let _ = validate(input); // Descartando silenciosamente un Result

// Mal: Bloquear en contexto async
async fn bad_async() {
    std::thread::sleep(Duration::from_secs(1)); // ¡Bloquea el executor!
    // Usar: tokio::time::sleep(Duration::from_secs(1)).await;
}

Recuerda: Si compila, probablemente es correcto — pero solo si evitas unwrap(), minimizas unsafe y dejas que el sistema de tipos trabaje para ti.

© affaan-m, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in docs/es/skills/rust-patterns of affaan-m/ECC.

Open the folder on GitHubat commit ef648e0

Compare with similar skills

Rust Patterns next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Rust Patterns compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Rust Patterns this skillaffaan-m/ECC274k—~3.5kAutomated safety check: PassMIT
Update V8 Versionopeninterpreter/openinterpreter69k2 repos~845Automated safety check: PassApache-2.0
Firecrawl Page Scrape Integrationfirecrawl/firecrawl189k1 repos~944Automated safety check: PassISC
Migrate Core Code to Submodulestinyhumansai/openhuman41k—~2.6kAutomated safety check: PassGPL-3.0
Rust TDD Workflowrtk-ai/rtk83k—~753Automated safety check: NotesApache-2.0
Rust Best Practicesfarm-fe/farm5.6k3 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Update V8 Version

    openinterpreter/openinterpreter

    Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.

    69k GitHub starsUsed in 2 repos~845 tokens
    DevOps & CloudAuto-check passed
  • Adds Firecrawl's /scrape endpoint to application code to pull markdown, HTML, links, screenshots or structured data from a single known URL.

    189k GitHub starsUsed in 1 repo~944 tokens
    Data & AnalyticsAuto-check passed
  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

    41k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Enforces red-green-refactor for Rust work, with idiomatic test patterns, a naming convention and a pre-commit gate of cargo fmt, clippy and test.

    83k GitHub stars~753 tokensUpdated today
    Testing & QAAuto-check: notes
  • Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.

    5.6k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated 3 days ago
    DevelopmentAuto-check: notes

More from affaan-m/ECC

All 657 skills in this repo
  • Skill Stocktake

    affaan-m/ECC

    Audits your installed Claude skills and commands for quality, with a quick mode for recently changed skills and a full mode that evaluates all of them through subagents.

    274k GitHub starsUsed in 5 repos~1.9k tokens
    Auto-check passed
  • Videodb

    affaan-m/ECC

    Ingest, index, search, edit, and monitor video and audio with the VideoDB Python SDK — upload from files, URLs, or RTSP feeds, build spoken and scene indexes with timestamped search and playable…

    274k GitHub starsUsed in 3 repos~3.5k tokens
    Auto-check: notes
  • Rules Distillation

    affaan-m/ECC

    Scans installed skills for principles that recur across them and proposes rule-file changes: append, revise, add a section, create a file or leave as covered.

    274k GitHub starsUsed in 2 repos~2.3k tokens
    Auto-check passed
  • Builds DRAFT counterparty agreements from one markdown template and a small JSON spec per party, with clauses picked by the party's role.

    274k GitHub stars~2.9k tokensUpdated 2 days ago
    Auto-check passed
  • Measures whether agents actually follow a skill, rule or agent definition by generating scenarios at three strictness levels and scoring tool-call traces.

    274k GitHub starsUsed in 1 repo~623 tokens
    Auto-check passed
  • Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.

    274k GitHub stars~3.5k tokensUpdated 2 days ago
    Auto-check passed

Works with

Questions about Rust Patterns

What does Rust Patterns do?

Patrones idiomáticos de Rust, ownership, manejo de errores, traits, concurrencia y buenas prácticas para construir aplicaciones seguras y eficientes. Rust Patterns is an agent skill from affaan-m/ECC. Patrones idiomáticos de Rust, ownership, manejo de errores, traits, concurrencia y buenas prácticas para construir aplicaciones seguras y eficientes.

How do I install Rust Patterns in Claude Code?

Run `npx skills add affaan-m/ECC --skill rust-patterns -a claude-code`. Or copy the skill folder (docs/es/skills/rust-patterns in affaan-m/ECC) into .claude/skills/rust-patterns in your project. Claude Code loads it when a task matches its description.

How do I install Rust Patterns in Codex?

Run `npx skills add affaan-m/ECC --skill rust-patterns -a codex`. Or copy the skill folder (docs/es/skills/rust-patterns in affaan-m/ECC) into .agents/skills/rust-patterns in your project. Codex loads it when a task matches its description.

Can I use Rust Patterns in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add affaan-m/ECC --skill rust-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rust-patterns, .gemini/skills/rust-patterns, .github/skills/rust-patterns and .opencode/skills/rust-patterns in your project.

What does Rust Patterns need to run?

Going by SKILL.md and its folder, Rust Patterns needs the command-line tools its instructions call (cargo).

Does Rust Patterns access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Rust Patterns safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Rust Patterns use?

Rust Patterns is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Rust Patterns use?

About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Rust Patterns?

Skills that share tags, products or a category with Rust Patterns: Update V8 Version (openinterpreter/openinterpreter, 69k stars), Firecrawl Page Scrape Integration (firecrawl/firecrawl, 189k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 41k stars) and Rust TDD Workflow (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Rust Patterns?

affaan-m (a GitHub user) maintains it in affaan-m/ECC, which has 274,360 GitHub stars. The repository holds 657 skills in this directory. The repository was last updated on October 5, 2026.

Source: affaan-m/ECC on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.