Skills type-driven-design-rust
📦

type-driven-design-rust

Content revision r1 Safe ⚙️ External commands🌐 Network access

Design Safer Rust APIs with Types

Rust APIs can allow invalid states or swapped values when invariants stay in runtime logic. This skill shows how to encode invariants with newtypes, typestate, builders, phantom types, and session types.

Supports: Claude Codex Code(CC)
🥉 77 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "type-driven-design-rust" from https://skillstore.io/skills/emillindfors-type-driven-design.md and its manifest at https://skillstore.io/api/skills/emillindfors-type-driven-design/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/emillindfors-type-driven-design.md Signed manifest GET /api/skills/emillindfors-type-driven-design/manifest Signed lockfile GET /api/skills/emillindfors-type-driven-design/lockfile

Test it

Using "type-driven-design-rust". I need to stop UserId and OrderId from being mixed in service calls.

Expected outcome:

  • The skill recommends separate newtype wrappers around the shared identifier representation.
  • It explains constructors, accessors, and function signatures that reject the wrong identifier type.
  • It notes where conversions and display behavior should be implemented.

Using "type-driven-design-rust". My request builder allows POST requests without a body.

Expected outcome:

  • The skill maps the builder into method and body states.
  • It makes send available only for valid state combinations.
  • It explains why invalid request sequences fail during compilation.

Using "type-driven-design-rust". I want to model a database session with authentication and transactions.

Expected outcome:

  • The skill identifies session states and allowed transitions.
  • It separates methods by state so unauthenticated sessions cannot start transactions.
  • It describes the ergonomics and complexity trade-offs of this design.

Security Audit

Safe
v4 • 7/6/2026 Open versioned report

All static findings were adjudicated as false positives. The backtick detections are Markdown code fences, the URLs are examples or documentation links, and the reconnaissance matches are benign Rust type-design text.

1
Files scanned
799
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (33)
SKILL.md:38-46 SKILL.md:46-50 SKILL.md:50-64 SKILL.md:64-70 SKILL.md:70-96 SKILL.md:96-100 SKILL.md:100-129 SKILL.md:129-133 SKILL.md:133-155 SKILL.md:155-159 SKILL.md:159-182 SKILL.md:182-192 SKILL.md:192-211 SKILL.md:211-215 SKILL.md:215-285 SKILL.md:285-289 SKILL.md:289-372 SKILL.md:372-378 SKILL.md:378-423 SKILL.md:423-427 SKILL.md:427-516 SKILL.md:516-522 SKILL.md:522-578 SKILL.md:578-584 SKILL.md:584-664 SKILL.md:664-670 SKILL.md:670-687 SKILL.md:687-691 SKILL.md:691-706 SKILL.md:706-710 SKILL.md:710-733 SKILL.md:733-742 SKILL.md:742-747
🌐 Network access (6)
SKILL.md:357 SKILL.md:362 SKILL.md:776 SKILL.md:777 SKILL.md:778 SKILL.md:779
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/emillindfors-type-driven-design/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/emillindfors-type-driven-design/security.svg)](https://skillstore.io/skills/emillindfors-type-driven-design?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/emillindfors-type-driven-design?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/emillindfors-type-driven-design/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/emillindfors-type-driven-design.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

EmilLindfors. (2026). type-driven-design-rust security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/emillindfors-type-driven-design/audits/4

BibTeX citation

@techreport{emillindfors-emillindfors-type-driven-design-2026, author = {EmilLindfors}, title = {type-driven-design-rust security audit report (audit version 4)}, institution = {Skillstore}, year = {2026}, number = {4}, url = {https://skillstore.io/skills/emillindfors-type-driven-design/audits/4}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "type-driven-design-rust security audit report (audit version 4)" version: "unspecified" type: report authors: - name: "EmilLindfors" date-released: "2026-07-06" url: "https://skillstore.io/skills/emillindfors-type-driven-design/audits/4" identifiers: - type: other value: "skillstore:emillindfors-type-driven-design:audit:4" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
74
Spec Compliance

What You Can Build

Prevent API Misuse

Design library APIs that make invalid method order and missing required values impossible to compile.

Model Domain Invariants

Represent identifiers, units, and validated values with distinct types instead of shared primitive values.

Teach Safer Rust Patterns

Explain type-level techniques with before-and-after examples that show compile-time guarantees.

Try These Prompts

Model a Newtype 
I have [value type] used for [domain meaning]. Show a Rust newtype design that prevents value mix-ups, with constructors and usage examples.
Add Typestate to a Workflow 
Refactor this Rust workflow into a typestate API. The states are [states], and the allowed transitions are [transitions]. Explain the compile-time guarantees.
Build a Compile-Time Builder 
Design a Rust builder for [configuration object] where [required fields] must be set before build is available. Include optional fields and trade-offs.
Design a Session Protocol 
Create a session-type design for [protocol]. The protocol must enforce [authentication, transaction, cleanup, or other steps] at compile time.

Best Practices

  • Start with invariants that cause real bugs when they are only checked at runtime.
  • Keep marker types and constructors small so the public API stays readable.
  • Explain compile-time failures clearly so callers understand how to reach valid states.

Avoid

  • Do not use typestate for every boolean or minor validation rule.
  • Do not expose unchecked constructors that bypass the invariant encoded by the type.
  • Do not hide complex generic errors from users without examples or type aliases.

Frequently Asked Questions

What Rust patterns does this skill cover?
It covers newtypes, typestate, compile-time builders, phantom types, session types, and type-level invariants.
Can it help refactor an existing Rust API?
Yes. Provide the current API, invalid states, and desired transitions, then ask for a type-driven redesign.
Does the skill execute Rust code?
No. It provides design guidance and examples, but it does not compile or run code by itself.
When should I avoid type-driven design?
Avoid it when states are highly dynamic or when the added generic complexity outweighs the safety benefit.
Is this useful for beginners?
Yes. The skill starts with simple newtype examples before moving to typestate and session types.
How should I use it with Claude, Codex, or Claude Code?
Share your Rust API goal, invariants, and invalid operations. Ask for a design that makes those invalid operations unrepresentable.

Developer Details

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/EmilLindfors/claude-marketplace/tree/main/plugins/rust-modern-patterns/skills/type-driven-design

Ref

a06681402992ceae98ba04d54cfd4ab004862696

Maintenance freshness

7/18/2026

Usage

5 downloads · 150 views

File structure

📄 SKILL.md