qa

Provide a pre-shipment QA checklist for Scaffold-ETH 2 dApps.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/mashharuki/flare-sample --skill qa-mashharuki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/mashharuki/flare-sample/tree/main/.claude/skills/eth-qa
Command: npx skills add https://github.com/mashharuki/flare-sample --skill qa-mashharuki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured pre-release QA checklist tailored to Scaffold-ETH 2 builds to catch common production issues such as broken wallet flows, incorrect RPC configuration, unverified contracts, default template branding, and mobile deep-link failures before shipping.

Core Features & Use Cases

  • Wallet Flow Validation: Ensures a prominent Connect Wallet button and correct four-state button progression (Connect → Switch Network → Approve → Action).
  • UX & Branding Cleanup: Detects leftover Scaffold-ETH defaults in footer, title, README, and favicon that harm user trust.
  • Technical Checks: Verifies pollingInterval and RPC overrides, confirms environment variables on hosting, validates address input components, and enforces contract verification on explorers.
  • Mobile & Deep Linking: Tests WalletConnect/RainbowKit behavior and ensures transactions fire before deep linking to wallet apps.
  • Use Case: Hand this checklist to an independent reviewer after build completion to produce a pass/fail audit for production readiness.

Quick Start

Open the built dApp in a browser with no wallet connected and perform a full reviewer pass verifying the Connect button, four-state button flow, branding removal, RPC and polling settings, contract verification, address input handling, and mobile deep-link behavior.

Frequently Asked Questions about qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a pre-ship QA checklist for a Scaffold-ETH 2 dApp?

Pre-ship QA for a Scaffold-ETH 2 dApp involves opening the built frontend with no wallet connected and verifying wallet flows, branding cleanup, RPC overrides, contract verification, and mobile deep-link behavior to produce a pass/fail audit.

What is the correct wallet connect button flow for Ethereum dApps?

The correct wallet connect flow requires a prominent button following a four-state progression: Connect, Switch Network, Approve, and Action. This sequence validates network switching and approval sequencing before final execution.

How do I test mobile deep-link transaction sequencing with WalletConnect?

Testing mobile deep-link transaction sequencing involves verifying WalletConnect or RainbowKit behavior to ensure transactions fire correctly before deep linking redirects users back to mobile wallet apps for signing.

Does Scaffold-ETH 2 require contract verification on block explorers before shipping?

Yes, pre-shipment QA requires contract verification on block explorers. You must also verify polling intervals, environment variables on hosting, and RPC override correctness to ensure production readiness.

What default template branding do I need to remove from a Scaffold-ETH 2 dApp?

You need to remove leftover Scaffold-ETH defaults from the footer, title, README, and favicon. Detecting and cleaning these template elements is required to prevent harming user trust before deployment.

Why does my dApp RPC configuration fail during network switching?

RPC configuration fails during network switching if polling intervals and environment variables are incorrect on your hosting platform. Pre-ship QA validates these RPC overrides and address input components to prevent failures.