domain-fintech

Enforce rust_decimal::Decimal, Arc<T>, and event sourcing in Rust FinTech applications.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/AlexKVal/rust-skills-for-cursor --skill domain-fintech-alexkval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-fintech
Source: https://github.com/AlexKVal/rust-skills-for-cursor/tree/main/skills/domain-fintech
Command: npx skills add https://github.com/AlexKVal/rust-skills-for-cursor --skill domain-fintech-alexkval

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

FinTech domain constraints for Rust apps to ensure precise monetary handling, auditable workflows, and thread-safe designs across async boundaries.

Core Features & Use Cases

  • Enforces decimal-based money math using rust_decimal::Decimal to avoid floating-point errors.
  • Promotes immutable transactions and event sourcing for reproducible audits.
  • Guides safe sharing of data with Arc<T> over Rc and across threads.

Quick Start

Install and configure the FinTech domain guidance and apply to your Rust project to align with domain constraints.

Frequently Asked Questions about domain-fintech

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle precise decimal arithmetic for financial calculations in Rust?

To handle precise decimal arithmetic in Rust, enforce rust_decimal::Decimal for monetary values. This prevents floating-point errors during financial calculations and ensures accurate, auditable money math across fintech applications.

Why should I use Arc<T> instead of Rc for sharing financial data across async boundaries?

Use Arc<T> instead of Rc for sharing financial data across async boundaries to ensure thread safety. Arc<T> enables safe, concurrent access to shared data structures across multiple threads in Rust async environments.

What's the best way to implement immutable transaction modeling with event sourcing in Rust?

The best way to implement immutable transaction modeling with event sourcing in Rust is to promote immutable transactions for reproducible audits. This approach ensures every state change is captured as an immutable event, creating an auditable workflow.

Does this fintech Rust guidance enforce specific patterns for audit trails?

Yes, this fintech Rust guidance enforces specific patterns for audit trails by applying immutable event sourcing and transaction modeling. It ensures reproducible audits by requiring precise decimal arithmetic and immutable event logs for all financial operations.

Can I use floating-point types for monetary values in a Rust fintech application?

No, you should not use floating-point types for monetary values in a Rust fintech application. The guidance enforces rust_decimal::Decimal to avoid floating-point errors and maintain the precision required for financial calculations and auditability.