rust-architect

Generate Rust workspace architecture documentation with ADRs and guardrails.

18|3|Updated Nov 13, 2025
One-click install
npx skills add https://github.com/nanlong/rust-architect --skill rust-architect-nanlong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-architect
Source: https://github.com/nanlong/rust-architect/tree/main/skills/rust-architect
Command: npx skills add https://github.com/nanlong/rust-architect --skill rust-architect-nanlong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Rust Project Architect provides comprehensive architecture documentation and governance artifacts (ADRs, guardrails, handoff materials) to enable Director and Implementor AI to design, review, and hand off Rust systems with confidence.

Core Features & Use Cases

  • Automated multi-crate workspace architecture generation with domain models and ownership strategies.
  • Architecture Decision Records (ADRs) and guardrails to enforce Rust best practices.
  • Handoff-ready documentation and collaboration artifacts for AI-driven delivery.
  • Use Case: Start a new web service or CLI toolkit in Rust and receive a complete doc package including architecture overview, ADRs, and guardrails.

Quick Start

Instruct the Architect to generate a complete Rust workspace documentation package for a new multi-crate project.

Frequently Asked Questions about rust-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate architecture documentation for a multi-crate Rust workspace?

Generate Rust workspace architecture documentation by instructing the architect to output a complete package covering domain models, ownership strategies, and async patterns. This yields an architecture overview, ADRs, and guardrails for multi-crate projects.

What are Rust architecture guardrails and when do I need them?

Rust architecture guardrails are governance artifacts that enforce best practices for ownership models and async patterns. You need them when designing complex Rust systems to ensure AI agents and developers adhere to defined architectural constraints during implementation.

Can I use this to create handoff materials for AI-driven Rust development?

Yes, you can create handoff-ready documentation for AI-driven Rust development. It generates collaboration artifacts specifically designed to support Director and Implementor AI agents in reviewing and building complex systems with confidence.

Does this work for designing both Rust web services and CLI toolkits?

Yes, this works for designing both Rust web services and CLI toolkits. It applies to multi-crate Rust workspaces and backend components, generating comprehensive documentation packages that govern architecture across these specific application types.

What is the best way to manage architecture decisions for a Rust backend system?

The best way to manage architecture decisions for a Rust backend system is by generating Architecture Decision Records (ADRs). ADRs document choices for ownership models and async patterns, providing governance and review context for AI-driven delivery.