Encode Rust type-system invariants to prevent invalid runtime states.
npx skills add https://github.com/simorgh3196/tsuzulint --skill m05-type-driven
Please help me install this Agent Skill. Skill: m05-type-driven Source: https://github.com/simorgh3196/tsuzulint/tree/main/.agents/skills/m05-type-driven Command: npx skills add https://github.com/simorgh3196/tsuzulint --skill m05-type-driven
This Skill helps developers prevent invalid runtime states by encoding invariants in the Rust type system, enabling compile-time guarantees that certain states can only exist when preconditions are met.
Create a small Rust module that defines a newtype around a primitive (e.g., UserId), implements a simple Type State flow (e.g., Unregistered -> Registered), and experiments with PhantomData and marker traits to encode invariants. Then wire a minimal builder to demonstrate gradual construction.
High-intent search queries and answers about installing and using this skill.
To prevent invalid state transitions in Rust at compile time, encode your invariants using the type-state pattern, modeling distinct states as separate types so the compiler rejects invalid transitions.
The best way to enforce domain semantics on primitive values in Rust is the newtype pattern, wrapping primitives in dedicated structs to guarantee type safety and prevent invalid runtime data.
PhantomData works by using phantom type parameters to encode additional compile-time constraints in Rust, enforcing invariants and relationships between types without incurring any runtime cost.
To build a type-safe builder pattern in Rust, progressively construct complex objects using type-state steps and marker traits, ensuring required fields are initialized before compilation succeeds.
Yes, you can use marker traits in Rust API design to express capabilities and allowed operations through trait bounds, ensuring certain functions are only callable on types that meet specific criteria.
Use sealed traits and zero-sized types in Rust when you need to limit external implementations of your APIs and leverage zero-sized markers for safety and clarity without runtime overhead.
dojoengineAnalyze Rust codebases to enumerate modules, structs, traits, enums, and functions via LSP symbols.
NickCrewDevelops TypeScript type-safe applications using advanced typing techniques and constructs.
newkubGuide Rust programming best practices for project structure, error handling, and concurrency.
RambleRainbowRefactor Rust code to idiomatic patterns with anyhow and thiserror.
