creating-fraktor-modules

To generate a module skeleton with no_std and std separation, specify the target crate, type name, and desired core/std layer. The skill produces a ready-to-compile template satisfying no_std/std separation, test layout, and FQCN import conventions.

Enforcing one-file-one-type and FQCN imports during scaffolding requires applying project lint rules to new modules. This skill automatically generates compliant skeletons across actor, utils, remote, cluster, streams, and persistence crates to reduce setup time and human error.

Setting up file structures for Fraktor-rs persistence and streams modules involves generating boilerplate that adheres to test placement and import conventions. This skill creates ready-to-implement skeletons matching existing patterns when adding new types or starting a new module.

Yes, adding new types to existing remote and cluster crates is supported during module creation. The skill generates compliant type skeletons, applies correct no_std and std layer separation, and includes test scaffolding and wiring patterns across these crates.

Auto-generating test scaffolding and wiring patterns for Fraktor-rs modules is a core feature of this skill. It produces boilerplate across core and std layers that aligns with project lint rules, ensuring correct test placement and file structure.

Newly created Fraktor-rs modules may fail to compile if boilerplate scaffolding violates no_std/std separation, test placement, or FQCN import conventions. This skill generates consistent module skeletons aligned with project lint rules to prevent such human errors.