claude

tailrocks-rust-skills

Strict Rust engineering workflows covering Axum, GraphQL, gRPC, TUI design, project baselines, review, refactoring, and remediation.

1 on GitHubv0.29.0Apache-2.0updated 22 days ago

Not in a marketplace yet, so it loads for one session with --plugin-dir.

Plugin tailrocks-rust-skills in tailrocks/tailrocks-rust-skills. Commands read from the repo's manifest — 21 days ago.

What it installs

Skills (16)

  • tailrocks-axum-best-practices

    Apply Axum policy when in-scope work builds or changes HTTP adapters, routers, handlers, extractors, Tower layers, lifecycle, or transport tests. Use tailrocks-axum-review for findings and tailrocks-axum-refactor when HTTP behavior stays unchanged. User builds or changes Axum HTTP adapters in author

  • tailrocks-axum-refactor

    Use only when the user explicitly requests this skill. Restructure Axum adapters or Tower composition while preserving HTTP behavior. Require an independent oracle. Use tailrocks-axum-best-practices when transport behavior changes.

  • tailrocks-axum-review

    Use only when the user explicitly requests this skill. Review Axum HTTP adapters, extractors, Tower policy, lifecycle, and transport tests without editing. Use tailrocks-axum-best-practices for behavior changes and tailrocks-axum-refactor for approved restructuring.

  • tailrocks-graphql-best-practices

    Apply public GraphQL API policy when in-scope work evolves schema, Juniper resolvers, SDL, pagination, or generated clients. Use tailrocks-graphql-review for read-only findings. This skill is not for cross-service communication. That is gRPC. User evolves the public GraphQL API in authorized work.

  • tailrocks-graphql-review

    Use only when the user explicitly requests this skill. Review a GraphQL diff or audit a public API surface without editing. Report verified schema, Juniper, SDL-gate, and generated-client findings. Use tailrocks-graphql-best-practices for evolution.

  • tailrocks-grpc-best-practices

    Apply cross-service gRPC policy when in-scope work evolves proto or Buf contracts, tonic/prost services, status mapping, deadlines, streaming, health, or wire tests. Use tailrocks-grpc-review for findings. This skill is not for public APIs. Those are GraphQL. User evolves a cross-service gRPC contra

  • tailrocks-grpc-review

    Use only when the user explicitly requests this skill. Review a gRPC diff or audit a cross-service surface without editing. Report verified proto, Buf, tonic/prost, status, deadline, operations, and wire-test findings. Use tailrocks-grpc-best-practices for evolution.

  • tailrocks-rust-best-practices

    Apply Rust correctness contracts when in-scope work writes Rust behavior. Covers ownership, failure, unsafe, tests, and performance. Use tailrocks-rust-review for findings and tailrocks-rust-refactor for behavior-preserving restructuring. User adds or changes Rust behavior in authorized work.

  • tailrocks-rust-project-audit

    Use only when the user explicitly requests this skill. Audit an existing Rust workspace against the strict project baseline and report exact gaps without changing files or installing tools. Use tailrocks-rust-project-remediate only when the user approves fixes.

  • tailrocks-rust-project-remediate

    Use only when the user explicitly requests this skill. Remediate user-approved gaps in an existing Rust workspace baseline while keeping every intermediate state buildable. Use tailrocks-rust-project-audit to discover or report gaps. This skill requires explicit approved scope.

  • tailrocks-rust-project-setup

    Use only when the user explicitly requests this skill. Scaffold a strict Rust workspace with layout, toolchains, lints, mise, dependency policy, and test gates. For existing projects, use tailrocks-rust-project-audit to report gaps or tailrocks-rust-project-remediate for approved fixes.

  • tailrocks-rust-refactor

    Use only when the user explicitly requests this skill. Restructure Rust code while preserving observable behavior and public contracts. Require a preservation oracle and approved scope. Use tailrocks-rust-best-practices when behavior changes and tailrocks-rust-review for read-only findings.

  • tailrocks-rust-review

    Use only when the user explicitly requests this skill. Review Rust source, APIs, unsafe code, tests, and performance evidence read-only. Report verified findings. Never edit. Use tailrocks-rust-best-practices for new behavior and tailrocks-rust-refactor for approved restructuring.

  • tailrocks-rust-toolchain

    Apply the Tailrocks Rust toolchain policy to every Rust task: latest stable Rust, mbx (Mr. Boxington) as the Cargo provider through mise, and the committed mise.toml and rust-toolchain.toml baseline in each clone. Use for any Rust build, test, or project work. Any Rust build, test, or project work s

  • tailrocks-tui-design-audit

    Use only when the user explicitly requests this skill. Audit a ratatui gallery, golden-frame package, or shipped terminal screen against its blessed contract. Read-only. It never designs, fixes, blesses, writes goldens, commits, or changes taste policy.

  • tailrocks-tui-design

    Apply terminal visual-design policy when in-scope work touches ratatui screens, terminal UX, fixture galleries, or golden frames. Selection alone never authorizes blessing, golden freeze, capture, or mutation. User designs ratatui terminal screens in authorized work.

View source on GitHub

Maintain tailrocks-rust-skills?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted