functional-rust-generator

Generate Rust projects enforcing Data→Calculations→Actions with zero panics and unwraps.

1|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/lprior-repo/claude-skills --skill functional-rust-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: functional-rust-generator
Source: https://github.com/lprior-repo/claude-skills/tree/main/functional-rust-generator
Command: npx skills add https://github.com/lprior-repo/claude-skills --skill functional-rust-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Functional-first Rust architecture guidance and tooling that enforces zero panics, zero unwraps, and zero mutability, while delivering clippy-friendly, testable code across Data→Calculations→Actions boundaries.

Core Features & Use Cases

  • Data-first modeling using newtypes and enums to represent domain concepts
  • Pure calculations that are deterministic and side-effect-free
  • Minimal shell-facing actions with explicit state transitions and robust error handling
  • Enforced no-unwrap/no-panic in core code through domain errors and proper propagation
  • Clippy-friendly patterns and verified test compilation to ensure reliable builds

Quick Start

Run the generator to scaffold or refactor a Rust project toward the Data→Calculations→Actions pattern, enforcing zero panics and clippy-friendly discipline.

Frequently Asked Questions about functional-rust-generator

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

FAQPage Schema
How do I enforce a no-panic, no-unwrap policy in my Rust project?

You structure Rust code into Data→Calculations→Actions boundaries, replacing unwraps with domain errors via thiserror and ensuring pure, side-effect-free calculations to eliminate panics.

What is the Data Calculations Actions pattern in functional Rust architecture?

The Data→Calculations→Actions pattern separates Rust code into trusted boundary types, deterministic pure calculations, and minimal shell-facing I/O actions to ensure type-driven, testable domain modeling.

How do I structure Rust domain modeling without primitive booleans?

To model Rust domains without primitive booleans, use type-driven newtypes and enums to represent domain concepts, enforcing explicit state transitions and trusted boundary types for compile-time safety.

Does this functional Rust approach work with clippy lints?

Yes, this functional Rust approach integrates clippy-aware defaults and verified test compilation, ensuring reliable, zero-mutability builds that satisfy strict clippy lints without conflicts.

How do I handle Rust errors without unwrap or panic in core code?

To handle Rust errors without unwrap or panic, express domain errors via thiserror and propagate them through pure calculation pipelines, restricting mutability and I/O to the shell boundary.