dojo-debug

The dojo-debug skill provides a comprehensive diagnostic framework for developers building onchain applications with the Dojo engine. It is designed for engineers encountering technical roadblocks within the Dojo.js stack, specifically when dealing with Torii indexers, Starknet provider interactions, and complex entity subscription logic. This skill assists in identifying root causes for common development friction, such as broken WebSocket connections, CORS policy violations, and unexpected entity state discrepancies.

• Advanced Torii troubleshooting including health check commands, log analysis, and CORS configuration validation.

• Debugging entity synchronization, specifically addressing 'entity not found' errors, filter constraints, and subscription lifecycle management.

• Type safety verification and schema mapping for Cairo contracts, ensuring TypeScript types generated via the Dojo ABI remain consistent with the onchain state.

• Diagnostic tools for managing transaction lifecycle, nonce tracking, and balance verification for burner accounts.

• Performance optimization patterns, including the use of gRPC for query efficiency, paginated requests, and state management techniques to reduce component re-renders.

• Integration support for Dojo hooks like useDojoStore and SDK initialization patterns.

• Input expectations include error logs, observed behavior, and current configuration snippets, such as manifest details or Torii URLs.

• Outputs typically consist of debugging code snippets, CLI diagnostic commands, configuration adjustments, and systematic verification steps to isolate the issue.

• Users should be aware that this skill is strictly for development and testing environments; it does not handle production-grade security auditing.

• Always verify your manifest version and ABI compatibility before applying code-level fixes, as most synchronization issues stem from out-of-date local type definitions compared to the deployed world state.