Rust Pro Max logo

Rust Pro Max

Organization
vurakit
rust-pro-max

Rust development intelligence. 14 domains, 11 stacks, 300+ entries. Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check Rust code. Domains: pattern, crate, error, perf, test, concurrency, traits, arch, idiom, anti, tooling, module, unsafe. Stacks: web-axum, web-actix, web-rocket, web-warp, cli, grpc, database, async-runtime, auth, wasm, embedded. Integrations: arch_system generator.

Overview

Publishervurakit
Repositoryagentup
Skill namerust-pro-max
Stars
56
Forks
14
Bundled files
29
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 29 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by vurakit on GitHub. Read the source before you install it.

Installation

Install the Rust Pro Max AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/vurakit/agentup/tree/main/skills/rust
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/vurakit/agentup.git /tmp/agentup
mkdir -p .claude/skills
cp -r /tmp/agentup/skills/rust .claude/skills/rust-pro-max
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Rust Pro Max in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Rust Pro Max on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Rust Pro Max is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Rust Pro Max - Backend Generator

When User Requests Rust Work

Follow this workflow for every Rust-related task:

1. Analyze Requirements

Extract from the user's request:

  • Project type: REST API, CLI, microservice, library, WebAssembly, Embedded
  • Domain: web, database, gRPC, messaging
  • Scale: small project, enterprise, library

Default Stack (always use unless user specifies otherwise)

ComponentDefaultCrate
DatabasePostgreSQLsqlx (async, compile-time checked)
Router/WebAxumaxum + tokio
SerdeJSON Serializationserde + serde_json
TracingLoggingtracing + tracing-subscriber
ConfigENV limits/Configfigment or dotenvy
Error HandlingGeneralthiserror (lib) / anyhow (app)
DeployDocker ComposeDockerfile + docker-compose.yml

Project structure: Domain-driven layout:

src/main.rs
src/lib.rs
src/config/      — env config & setup
src/domain/      — structs + traits
src/handlers/    — HTTP handlers (Axum)
src/services/    — business logic
src/repository/  — SQLx queries and DB access
migrations/      — SQL migration files

2. Generate Architecture System (REQUIRED for new projects)

bash
python3 skills/rust/scripts/search.py "<project description>" --arch-system -p "ProjectName"

This gives you: architecture, crates, error strategy, patterns, structure, testing approach.

3. Supplement with Domain Searches

Based on the project needs, search relevant domains:

bash
# Patterns for the task
python3 skills/rust/scripts/search.py "builder pattern newtype" --domain pattern

# Crates recommendations
python3 skills/rust/scripts/search.py "web api authentication" --domain crate

# Concurrency patterns
python3 skills/rust/scripts/search.py "tokio channel pipeline" --domain concurrency

# Performance tips
python3 skills/rust/scripts/search.py "zero copy clone" --domain perf

# Testing patterns
python3 skills/rust/scripts/search.py "mocking traits" --domain test

4. Stack Guidelines

If using a specific framework/stack:

bash
python3 skills/rust/scripts/search.py "middleware authentication" --stack web-axum
python3 skills/rust/scripts/search.py "clap subcommands config" --stack cli
python3 skills/rust/scripts/search.py "connection pool sqlx" --stack database

5. Implement

Apply all recommendations from the search results:

  • Use recommended architecture and project structure
  • Apply patterns (Builder, Newtype, Typestate, etc.)
  • Follow error handling strategy (thiserror vs anyhow)
  • Implement proper concurrency patterns with tokio
  • Add tests using proper mocking and standard #[test]

6. Always Generate Docker Files

Every web project MUST include these files:

Dockerfile (multi-stage build):

dockerfile
# Builder stage
FROM rust:1.80-alpine AS builder
WORKDIR /app
RUN apk add --no-cache musl-dev
COPY Cargo.toml Cargo.lock ./
# Dummy build to cache dependencies
RUN mkdir src && echo "fn main() {}" > src/main.rs && cargo build --release && rm -rf src
COPY src ./src
COPY migrations ./migrations
RUN cargo build --release

# Runtime stage
FROM alpine:3.20
RUN apk add --no-cache ca-certificates tzdata
COPY --from=builder /app/target/release/app /usr/local/bin/app
COPY migrations /app/migrations
WORKDIR /app
EXPOSE 8080
CMD ["app"]

Pre-Delivery Checklist

Before delivering Rust code, verify:

  • cargo check passes
  • cargo clippy -- -D warnings catches no issues
  • cargo test passes
  • No .unwrap() or .expect() used in production paths (use ? operator)
  • Appropriate borrowing vs owning used where applicable
  • Types are separated into DTOs vs Domain models
  • Error domains handled via Enums with #[derive(Error)] (thiserror)
  • Asynchronous bounds correctly handled

Quick Domain Reference

DomainWhen to Search
patternNeed a design pattern (builder, typestate, newtype)
crateChoosing a library/crate for a use case
errorError handling strategy, anyhow vs thiserror
perfPerformance optimization, zero-copy, allocations
testTesting approach, property testing, mocking
concurrencyTokio, Async-std, channels, atomics
traitsTrait design, bounds, associated types
archProject structure, hexagonal, workspaces
idiomRust conventions, naming, style
antiAvoiding common mistakes, lifetime misuse
toolingRust tools, cargo, clippy, fmt
moduleModules, visibility, workspaces
unsafeFFI, unsafe Rust guidelines

Resources

  • scripts/: BM25 search engine, architecture system generator
  • data/: 14 domains and 11 stacks with curated Rust entries

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Rust Pro Max AI skill do?

Rust development intelligence. 14 domains, 11 stacks, 300+ entries. Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check Rust code. Domains: pattern, crate, error, perf, test, concurrency, traits, arch, idiom, anti, tooling, module, unsafe. Stacks: web-axum, web-actix, web-rocket, web-warp, cli, grpc, database, async-runtime, auth, wasm, embedded. Integrations: arch_system generator.

Why use Rust Pro Max on TypingMind?

Because you install it once and use it with any model. Rust Pro Max is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Rust Pro Max in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/vurakit/agentup/tree/main/skills/rust. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Rust Pro Max?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Rust Pro Max?

As many as you like. As long as a model supports skills, you can use Rust Pro Max with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Rust Pro Max AI skill free?

Yes. It is published on GitHub by vurakit under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇