coding-standards

Enforce no_std constraints and overflow-safe arithmetic in Rust pallets by applying coding standards that prohibit unsafe operations, mandate checked math, and bound storage growth with MaxEncodedLen to ensure deterministic wasm runtime execution.

Handle wasm_bindgen serialization and error mapping by restricting boundary interfaces to safe primitives and string/JSON formats, preventing incorrect bigint transfers and ensuring raw RPC errors are mapped cleanly for frontend users.

Maintain strict TypeScript typing and React best practices by enforcing strict mode, stable identifiers, and disciplined BigInt handling rules across Next.js and PAPI frontend modifications to prevent runtime type errors.

FRAME pallet development requires Japanese-first documentation, strict naming conventions, and specific import ordering to reduce ambiguity during code reviews and ensure consistent engineering conventions across the project.

Generate Rust pallet changes and TypeScript calls following cross-language coding conventions by prompting the AI to apply naming rules, Japanese doc comments, checked arithmetic, and wasm boundary error mapping, then listing exactly which rules were applied.

Deterministic logging constraints for wasm are needed in Substrate runtime development because non-deterministic logging can cause consensus failures, making strict coding standards essential to prevent runtime execution divergences across nodes.