Domain Fintech

actionbook/rust-skills

This one maps fintech domain constraints directly to Rust design decisions. It's built around the core truth that you can't use f64 for money, ever, and shows you how immutability, precision, and audit trails flow down from regulatory requirements into concrete patterns like rust_decimal newtypes and Arc for transaction records. The trace-down tables connect "need immutable transaction records" to specific ownership choices and crate selections. Most valuable when you're starting a payment system or trading platform and need to see why certain architectural choices aren't optional in finance. The currency type example and common mistakes section will save you from the classic blunders.

skills.sh installs

3K

GitHub stars

1.6K

last updated

Aug 21, 2026

RULE: Never use f64 for money
WHY: Floating point loses precision
RUST: Use rust_decimal::Decimal

RULE: All transactions must be immutable and traceable
WHY: Regulatory compliance, dispute resolution
RUST: Arc<T> for sharing, event sourcing pattern

RULE: Money can't disappear or appear
WHY: Double-entry accounting principles
RUST: Transaction types with validated totals

"Need immutable transaction records"
    ↓ m09-domain: Model as Value Objects
    ↓ m01-ownership: Use Arc for shared immutable data

Sponsors

Promote your product hereReach 125k+ visitors monthlyPromote your product hereReach 125k+ visitors monthlyAgent CaffeineSponsoredClose your lid, come back to finished workSnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthlyWaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthlyknobsSponsoredSee your site on any phone, any day, in any language