workspace-architecture

Organize Cargo workspaces for Leptos, Axum, and SQLx projects.

Updated May 26, 2026
One-click install
npx skills add https://github.com/adelabdelgawad/rust-fullstack-agents --skill workspace-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workspace-architecture
Source: https://github.com/adelabdelgawad/rust-fullstack-agents/tree/main/plugins/rusty/skills/workspace-architecture
Command: npx skills add https://github.com/adelabdelgawad/rust-fullstack-agents --skill workspace-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structure Cargo workspaces for Leptos+Axum+SQLx projects, enabling consistent patterns, automated triggers, and centralized dependency management across crates.

Core Features & Use Cases

  • Virtual workspace root pattern to centralize dependencies and avoid per-crate duplication.
  • Member inheritance of workspace dependencies to keep pins consistent across crates.
  • Clear guidance on when to use a workspace (server-only code, multiple binaries, or shared domain types).

Quick Start

Scaffold a workspace with a virtual root and shared dependency pins for Leptos, Axum, and SQLx.

Frequently Asked Questions about workspace-architecture

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

FAQPage Schema
How do I structure a Cargo workspace for a Leptos, Axum, and SQLx project?

A Cargo workspace for Leptos, Axum, and SQLx uses a virtual root pattern to centralize dependency versions, allowing member crates to inherit shared pins and ensure consistent builds across the project.

When do I need a Cargo workspace for Rust full-stack web applications?

You need a Cargo workspace when structuring server-only code, building multiple binaries, or sharing domain types across crates, which allows centralized dependency management and consistent feature rules.

How do I centralize dependency versions across multiple Rust crates?

Centralize dependency versions by defining them in a virtual workspace root and configuring member crates to inherit workspace dependencies, which keeps pins consistent and avoids per-crate duplication.

Does member inheritance of workspace dependencies work with Leptos and Axum?

Member inheritance of workspace dependencies works with Leptos and Axum by allowing member crates to reference shared dependency pins defined in the virtual workspace root, ensuring consistent versions and additive feature rules.

What is the best way to scaffold a Rust workspace with shared dependency pins?

Scaffold a Rust workspace with shared dependency pins by creating a virtual workspace root, declaring dependencies centrally, and configuring member inheritance to automate version consistency across crates.

Why use a virtual workspace root pattern for Rust projects?

Use a virtual workspace root pattern for Rust projects to centralize dependencies and avoid per-crate duplication, ensuring all member crates inherit consistent pins and additive feature rules during builds.