algorand-typescript

To fix Algorand TypeScript PuyaTs compiler errors, you must enforce correct AVM types like uint64, bytes, and biguint. The skill prevents compilation issues by restricting JavaScript numbers and guiding proper type usage across smart contract development scenarios.

You need to use clone() in PuyaTs smart contracts during both reads and writes for complex AVM types. Applying clone() semantics prevents runtime issues and ensures correct value semantics when interacting with Algorand smart contract storage patterns.

The best way to handle GlobalState and BoxMap storage patterns in Algorand TypeScript is to apply safe read and write rules. Structured guidance ensures proper storage access, preventing incorrect state modifications and common runtime mistakes in PuyaTs.

To structure inner transactions and group transactions in Algorand TypeScript, follow best practices for method selectors and transaction patterns. The skill provides specific guidance to ensure correct inner transaction handling and prevent execution failures in PuyaTs.

Your PuyaTs smart contract fails because AVM constraints require specific types instead of standard JavaScript numbers. This skill enforces a strict no JavaScript numbers rule, promoting correct AVM value semantics to prevent compiler errors and runtime issues.