midnight-dapp

Validate DApp project structure and configuration for Midnight Network development

Interactive debugging for wallet, transaction, and proof issues in Midnight DApps

Use this agent when the user asks about Midnight DApp architecture, design patterns, or trade-offs. Routes architectural questions to appropriate skills and provides trade-off analysis. <example> Context: User is starting a new Midnight DApp project user: "How should I structure my DApp for a private voting system?" assistant: "I'll use the dapp-architect agent to design the architecture for your privacy-preserving voting DApp." <commentary> The user needs architectural guidance for a new DApp. The dapp-architect agent provides design patterns, component structure recommendations, and routes to relevant skills. </commentary> </example> <example> Context: User is deciding between implementation approaches user: "Should I cache contract state locally or always fetch from the chain? What are the trade-offs?" assistant: "Let me use the dapp-architect agent to analyze the trade-offs between caching and live fetching for your use case." <commentary> Trade-off analysis between approaches is a core dapp-architect capability. The agent considers privacy implications, performance, and consistency. </commentary> </example> <example> Context: User wants UX guidance for ZK proof workflows user: "How should I show proof generation progress to users? It takes several seconds and I don't want them to think it's broken." assistant: "I'll use the dapp-architect agent to recommend UX patterns for proof generation feedback." <commentary> DApp UX patterns around ZK proofs are a specialized area the dapp-architect handles, routing to proof-handling and transaction-flows skills. </commentary> </example> <example> Context: User is migrating from Ethereum development patterns user: "I'm coming from Ethereum - how do I handle transaction failures in Midnight? Is it similar to try/catch with ethers.js?" assistant: "Let me use the dapp-architect agent to explain Midnight's transaction model and how it differs from Ethereum patterns." <commentary> Migration questions from other Web3 platforms are common. The agent provides familiar comparisons while highlighting Midnight-specific privacy considerations. </commentary> </example>

Use when implementing error handling in Midnight DApps, displaying errors to users, handling proof generation failures, managing transaction rejections, or dealing with network disconnections.

Use when building witness data for ZK proofs, showing proof generation progress to users, implementing disclosure consent flows, handling proof timeouts and retries, or explaining privacy guarantees.

Use when reading public ledger state, implementing reactive UI that updates with chain state, caching state for performance, or understanding public vs private state in Midnight DApps.

Use when writing unit tests for Midnight contract interaction code, integration testing without ZK proofs, E2E testing with Playwright or Cypress, or setting up CI/CD pipelines for Midnight DApps.

Use when submitting transactions to Midnight contracts, tracking transaction status, implementing retry logic, building responsive UIs during proof generation, or understanding the build-prove-submit-confirm flow.

Use when setting up Lace wallet connection, handling multiple user accounts, switching between testnet and mainnet, troubleshooting wallet issues, or migrating from MetaMask/Web3 patterns.