컬렉션 rust

Rust 시스템 워크플로우·엔지니어링 신뢰성 AI 도구 모음 | AI Agent Skills

Claude Code, Cursor, Windsurf용 rust systems reliability AI Agent Skills 모음입니다. 개발자 워크플로 자동화에 초점을 둡니다.

이 Rust 컬렉션은 시스템 레벨 개발 워크플로우에 초점을 맞춥니다. 신뢰할 수 있는 도구 구성, 성능 튜닝, 신뢰성 검증, 릴리스 파이프라인 자동화를 실무적으로 지원합니다. 서버 순위가 아니라 정확성·관측 가능성·운영 안정성을 높이는 엔지니어링 역량을 강조하며, MCP 호환 통합은 필요 시 보조 기능으로만 다룹니다. 핵심 목표는 결국 신뢰성과 성능을 동시에 갖춘 소프트웨어 전달입니다.

Primary Install Bridge

Pick One Skill, Then Take the Install Path

This collection should not trap users in comparison mode or pretend to install the whole collection. Its job is to narrow the shortlist to one skill, then send the next click into installation, validation, and rollout. Installation happens on the skill path.

Step 1 / Primary Path

Step 1: Open the installation docs

Move from Rust discovery into the install flow, validation checklist, and first command path before comparing anything else.

Open the Install Path

Best-Fit Next Paths

The Next Click Should Keep Narrowing, Not Reset Back To A Generic Directory

Once the install path is clear, move into the solution, CLI, or editorial surface that best matches this collection. That keeps platform, framework, and operations demand narrowing into a more verifiable high-intent journey.

P1 solution

Process Automation Solution

A solution page for teams turning SOPs, handoffs, and operations into repeatable AI-assisted execution paths.

Operational intent deserves a stronger bridge than generic tooling lists can provide.

P1 solution

Data Extraction Solution

A solution page for ETL, structured output, reporting pipelines, and data-heavy automation work.

Data-heavy search demand is easier to recover through focused solution pages than through generic directories.

Editorial Proof & Trust Signals

Why This Collection Deserves Priority Attention

Reviewed on 2026-04-17 against Rust workflow fit, installation clarity, operator handoff, and systems engineering usefulness. This page is now positioned as an install-first Rust entry point instead of a broad language roundup.

We prioritize this page because Rust-intent users usually need a shortlist they can install, validate, and carry into real reliability and release loops quickly.

Trust Signals

- Entries are chosen for practical Rust workflow value such as reliability checks, performance-sensitive delivery, release automation, and operational clarity.
- Selection favors tools with public documentation and clear setup paths that teams can validate before wider rollout.
- The page is curated for repeatable systems engineering, not for vague language keyword coverage or generic repository popularity.

Grouping Logic

- Lead with tools that can enter a Rust-centered workflow without adding heavy setup ambiguity.
- Keep the shortlist compact enough for quick comparison while still covering reliability, release, review, and performance support.
- Use installation as the bridge from Rust discovery into validated daily execution.

Maintenance & Review

Last Reviewed: 2026-04-17
Cadence: Re-check when install flow, maintainer posture, or Rust workflow relevance changes upstream; otherwise review monthly.
Maintained By: Killer-Skills editorial review within the recovery-focused authority queue.
Verification: Validate installability, operator clarity, workflow fit, and maintainer trust before retaining or adding an entry.

Execution Examples

How These Skills Work Together In Practice

Install one Rust workflow tool first

Use this page when you want one Rust companion that can enter real systems work without turning evaluation into another endless toolchain comparison.

1. Open the installation docs before opening more Rust-related repositories.
2. Choose one tool that best supports reliability, release, review, or performance-sensitive work.
3. Install it and verify the CLI write path, sync behavior, and first operator checkpoint.
4. Only after the base path works, expand the setup across the wider Rust workflow.

Tighten a Rust release loop

Treat the collection as an editorial filter when you need Rust-adjacent tools that improve engineering confidence without overcomplicating the stack.

1. Check whether the tool has stable ownership and visible install guidance.
2. Review CLI behavior so operators know what will be written and synced.
3. Use one validated path before scaling it to more crates, services, or teammates.
4. Document the chosen Rust workflow baseline after the first clean rollout.

After Installation

Supporting Moves After The Install Path Is Clear

Step 2

Step 2: Check CLI write and sync behavior

Confirm what the CLI writes, how sync behaves, and what operators should validate after the install path is clear.

Step 3

Step 3: Cross-check with trusted tools

Use the official trusted collection to sanity-check workflow choices before you standardize a team stack.

declutter

wildcard

caro: fast Rust CLI that turns natural‑language tasks into a safe POSIX command. Built for macOS (MLX/Metal) with a built‑in model; supports vLLM/Ollama/LM Studio. JSON‑only output, safety checks, confirmation, multi‑step goals, devcontainer included.

★ 27

⑂ 0

인공지능

fix-department

Get all cops in a gem to 100% corpus conformance. Assesses, triages, and fixes all diverging cops in a target gem using worktree-isolated teammates.

★ 1

⑂ 0

개발자

fix-repo

Improve a specific repos corpus conformance by fixing its top diverging cops in parallel using worktree-isolated teammates.

★ 1

⑂ 0

개발자

triage

Rank cops by FP+FN from the corpus oracle to find the next batch to fix

★ 1

⑂ 0

개발자

mag123c

Session start - check progress, suggest next task

★ 55

⑂ 0

개발자

wrap

mag123c

Ultra-fast token & cost tracker for LLM Token Usage (e.g. Claude Code)

★ 60

⑂ 0

개발자

github-release

decentpaste

Create a GitHub release with auto-generated release notes from commits since the last tag. Uses conventional commits to categorize changes into Features, Bug Fixes, and maintenance sections.

★ 156

⑂ 0

보안

triage

Rank cops by FP+FN from the corpus oracle to find the next batch to fix

★ 1

⑂ 0

개발자

openlark-code-standards

foxzool

OpenLark 项目代码规范检查技能。用于快速审查仓库内的架构一致性、API 实现套路、参数校验、命名与导出规范，并输出可执行检查清单与证据路径。

★ 66

⑂ 0

개발자

Related Authority Collections

If This Page Is Close, Keep Narrowing With Adjacent Authority Pages

Do not reset back to the generic directory. Move sideways through these adjacent high-intent collections to narrow the shortlist toward the install path that best matches your team.

P1 collection

DevOps Workflow Tools to Install First

An operations-first collection for platform teams choosing release, incident, and automation helpers.

Operational intent is high value and should be routed into curated workflow picks instead of generic tool sprawl.

P1 collection

Agent Framework Tools to Install First

A framework and SDK collection for teams building agent foundations, not just browsing vendor names.

Framework intent strengthens the site's product judgment and reduces the mirror-site posture.

P2 collection

Community Skills to Install First

A community-tested collection for builders who want reusable skills without falling back to unfiltered repository browsing.

Community demand can still look authoritative when it is filtered through explicit curation and rollout logic.

P1 collection

TypeScript Workflow Tools to Install First

A typed-development collection that helps product teams shortlist TypeScript workflow tools with clear next steps.

TypeScript intent is strong enough to support a dedicated authority page instead of another mixed language roundup.

Installation Questions

Answer These Three Questions Before You Install

This collection should not keep users browsing forever. These three questions explain how to shortlist, install, and validate the next step.

이 컬렉션들은 어떤 워크플로를 위해 만들어졌나요?

워크플로 자동화, 프로세스 자동화, 문서 작업, 데이터 워크플로 및 재사용 가능한 스킬 스택을 중심으로 구성되어 있습니다.

컬렉션과 메인 스킬 디렉터리의 차이점은?

스킬 디렉터리는 직접 검색과 필터링에 적합하고, 컬렉션은 완전한 워크플로를 위한 보완적 스킬 묶음을 찾는 데 적합합니다.

이 컬렉션들을 Claude Code나 Cursor에 설치할 수 있나요?

네. 이 컬렉션의 스킬들은 일반적으로 Claude Code, Cursor, Windsurf 및 기타 지원 환경에서 통합 설치 흐름으로 작동합니다.

Additional Recovery Paths

Use These Additional Paths If You Need One More Step To Narrow The Decision

These are the supporting surfaces for this collection after the install direction is clear and the primary next paths have already narrowed the decision.

P1 solution

Agent Workflows Solution

A scenario page for users who already know the workflow problem they need to solve.

High-intent solution pages are safer recovery surfaces than broad skill detail expansion.

P1 solution

Workflow Automation Solution

A use-case page for users searching for repeatable automation patterns instead of one-off tools.

Workflow automation demand is easier to satisfy with curated intent clusters than with flat directory coverage.