Run any Skill in Manus with one click

rust-solid-hexagonal

Stars9

Forks0

UpdatedApril 10, 2026 at 04:13

Applies SOLID and hexagonal architecture in Rust: traits as ports, implementations in adapters, dependency inversion. Use when designing maverick-core/domain versus adapters, adding persistence or transport, or when the user mentions SOLID, ports, adapters, or coupling.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

antonygiomarxdev

antonygiomarxdev/maverick

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	rust-solid-hexagonal
description	Applies SOLID and hexagonal architecture in Rust: traits as ports, implementations in adapters, dependency inversion. Use when designing maverick-core/domain versus adapters, adding persistence or transport, or when the user mentions SOLID, ports, adapters, or coupling.

Rust — SOLID and hexagonal

SOLID mapped to Rust

Principle	In Rust
SRP	Focused crates/modules/`impl`; cohesive use-case types
OCP	New `enum` variants or new `impl Trait for Struct`
LSP	Trait impls honor docs; no surprising panics in “total” methods
ISP	Several small traits under `ports/`, not one huge persistence trait
DIP	Core defines traits; infrastructure implements them

Layout in this kind of monorepo

Domain / core: entities, rules, repository and transport traits.
Adapters: sqlite, udp, … — only here do drivers and external schema strings appear.
Runtime / binary: wires concrete implementations into the core.

Checklist when adding a capability

Does core import any I/O crate? → hide it behind a trait.
Does the trait force adapters to know too much internal detail? → split the trait (ISP).
Does an adapter change break domain tests? → domain tests should use fakes or test doubles for traits, not real SQLite.

More from this repository

same repository

rust-best-practices

antonygiomarxdev/maverick

Idiomatic Rust and engineering hygiene: Clippy, Option/Result patterns, ownership in APIs, iterators, unsafe discipline, async Send boundaries, and public API docs. Use when writing or reviewing Rust, onboarding idioms, or when the user asks for Rust best practices, idioms, or lint hygiene.

2026-04-109

rust-clean-code

antonygiomarxdev/maverick

Clean-code guidance for Rust: function size, modules, error handling, naming, and tests. Use during refactors, readability reviews, or when the user asks for cleaner or more maintainable code without a specific architecture topic.

2026-04-109

rust-linter-configuration

antonygiomarxdev/maverick

Documents Maverick Rust lint and format setup: rustfmt.toml, Clippy flags in CI, cargo aliases, and policy for allow/expect attributes. Use when configuring editors, fixing CI lint failures, adding clippy.toml or rustfmt options, or when the user mentions linters, rustfmt, Clippy, or -D warnings.

2026-04-109

rust-no-magic-values

antonygiomarxdev/maverick

Applies common production Rust practices to remove magic literals: named consts, enums, newtypes, and centralized schema strings. Use when writing or reviewing Rust, when the user mentions magic strings/numbers, duplicated literals, or when designing core versus adapter layers.

2026-04-109

name	rust-solid-hexagonal
description	Applies SOLID and hexagonal architecture in Rust: traits as ports, implementations in adapters, dependency inversion. Use when designing maverick-core/domain versus adapters, adding persistence or transport, or when the user mentions SOLID, ports, adapters, or coupling.

Rust — SOLID and hexagonal

SOLID mapped to Rust

Principle	In Rust
SRP	Focused crates/modules/`impl`; cohesive use-case types
OCP	New `enum` variants or new `impl Trait for Struct`
LSP	Trait impls honor docs; no surprising panics in “total” methods
ISP	Several small traits under `ports/`, not one huge persistence trait
DIP	Core defines traits; infrastructure implements them

Layout in this kind of monorepo

Domain / core: entities, rules, repository and transport traits.
Adapters: sqlite, udp, … — only here do drivers and external schema strings appear.
Runtime / binary: wires concrete implementations into the core.

Checklist when adding a capability

Does core import any I/O crate? → hide it behind a trait.
Does the trait force adapters to know too much internal detail? → split the trait (ISP).
Does an adapter change break domain tests? → domain tests should use fakes or test doubles for traits, not real SQLite.