M14 Mental Model

This is your go-to reference when Rust's ownership system feels like it's fighting you. It breaks down the core mental models you need, like treating ownership as a unique key handover and understanding why multiple readers or one writer is the rule. The visualization tables showing stack and heap relationships are genuinely helpful, and the "coming from other languages" section cuts through common misconceptions fast. Best used when you're staring at borrow checker errors and need to step back from the syntax to understand what safety guarantee you're violating. The trace up and trace down sections connect it to other m-series skills nicely, making it a hub for learning rather than just a reference card.

skills.sh installs: 3.5K
GitHub stars: 1.6K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add actionbook/rust-skills --skill m14-mental-model --agent claude-code

Installs into .claude/skills of the current project.

Files

Mental Models

Layer 2: Design Choices

Core Question

What's the right way to think about this Rust concept?

When learning or explaining Rust:

What's the correct mental model?
What misconceptions should be avoided?
What analogies help understanding?

Key Mental Models

Concept	Mental Model	Analogy
Ownership	Unique key	Only one person has the house key
Move	Key handover	Giving away your key
`&T`	Lending for reading	Lending a book
`&mut T`	Exclusive editing	Only you can edit the doc
Lifetime `'a`	Valid scope	"Ticket valid until..."
`Box<T>`	Heap pointer	Remote control to TV
`Rc<T>`	Shared ownership	Multiple remotes, last turns off
`Arc<T>`	Thread-safe Rc	Remotes from any room

Coming From Other Languages

From	Key Shift
Java/C#	Values are owned, not references by default
C/C++	Compiler enforces safety rules
Python/Go	No GC, deterministic destruction
Functional	Mutability is safe via ownership
JavaScript	No null, use Option instead