multiversx-clarification-expert

To resolve ambiguous MultiversX requirements, identify vague requests and ask targeted clarifying questions about scope, risk, and technical profiles before development begins to prevent wasted effort from incorrect assumptions.

To clarify scope for a MultiversX auditing task, ask targeted questions regarding threat models, invariants, token standards, data storage configurations, and acceptable trade-offs to ensure precise security implementations.

Handling vague MultiversX security requests involves avoiding generic implementations and instead asking specific questions about threat models and invariants to propose sensible defaults with explained technical trade-offs.

Yes, you can batch related clarifying questions for MultiversX token standards and data storage configurations, which ensures clarity and reduces friction by guiding users through critical decisions efficiently.

Yes, the clarification process proposes sensible default options for MultiversX development configurations while explaining the technical trade-offs, ensuring developers understand the implications of each critical decision.