What is the primary benefit of the m05-type-driven skill?

The primary benefit is shifting error detection from runtime to compile-time, allowing the Rust compiler to catch logic errors before the code even runs.

When should I trigger this skill in Claude?

Trigger this skill when designing complex state machines, handling sensitive domain data (like emails or IDs), or building APIs where you want to prevent user error.

Does this skill help with Rust performance?

Yes, many of these patterns like Newtypes and ZSTs (Zero-Sized Types) are zero-cost abstractions that provide safety without any runtime overhead.

How does this skill handle state machines?

It implements the Type State pattern, which uses distinct types for different states so that methods are only available when an object is in the correct state.

Rust Type-Driven Design

Name: Rust Type-Driven Design
Author: lywa1998

bylywa1998

API Development

Leverages the Rust type system to encode invariants and make invalid states unrepresentable at compile-time.

About

This skill empowers Claude to apply advanced Rust architectural patterns that shift error detection from runtime to compile-time. It provides structured guidance on implementing the Newtype pattern for domain safety, Type State patterns for robust state machine transitions, and Marker Traits for capability flags. By utilizing these patterns, developers can build highly reliable APIs where the compiler serves as the primary validator, significantly reducing bugs related to primitive obsession, invalid state transitions, and uninitialized data.

Key Features

Creates Newtype wrappers to prevent primitive obsession and ensure domain safety
Implements the Type State pattern to enforce valid state transitions
Utilizes PhantomData and Marker Traits for type-level metadata and variance
0 GitHub stars
Identifies and refactors anti-patterns like boolean flags and public fields with invariants
Provides templates for the Builder pattern to ensure gradual, validated object construction

Use Cases

Designing safe API interfaces that prevent users from calling methods out of sequence
Creating domain-specific value objects to replace raw strings or numeric types
Refactoring complex runtime state checks into compile-time Type State transitions

About

Key Features

Creates Newtype wrappers to prevent primitive obsession and ensure domain safety
Implements the Type State pattern to enforce valid state transitions
Utilizes PhantomData and Marker Traits for type-level metadata and variance
0 GitHub stars
Identifies and refactors anti-patterns like boolean flags and public fields with invariants
Provides templates for the Builder pattern to ensure gradual, validated object construction

Use Cases

Designing safe API interfaces that prevent users from calling methods out of sequence
Creating domain-specific value objects to replace raw strings or numeric types
Refactoring complex runtime state checks into compile-time Type State transitions