Point it at your native iOS repo and it scaffolds a complete XCUITest E2E UI-test suite for you — discovers your screens (SwiftUI + UIKit), plans the accessibilityIdentifier tagging, and generates a base test case, ready-to-run per-screen specs, server-side error-state specs, and the scheme/test-plan steps. Zero config.
Point it at your web repo and it scaffolds a complete Playwright E2E UI-test suite for you — auto-detects your router (Nuxt / Next / Vue Router / React Router), discovers your routes, plans the data-testid tagging, and generates ready-to-run mock-backed and real-backend specs, a playwright.config, and a login setup project. Zero config.
Point it at your React Native repo and it scaffolds a complete Maestro E2E UI-test suite for you — auto-detects your navigator, discovers your screens, plans the testID tagging, and generates ready-to-run Maestro flows with happy-path and server-side error-state coverage, a login subflow, and mock-control helpers. Zero config.
An opinionated Expo + Supabase + EAS workflow for shipping a small app to both stores; schema/RLS design, auth, native modules, universal links, and store submission, in the order that avoids cloud-builder-only failures.
Systematic QA of CLI tools and pipelines across multiple real workspaces using SFDPOT heuristics. Executes structured test flows, evaluates consistency oracles, collects evidence, and produces a structured bug report with P1/P2/P3 priorities and a release readiness verdict.
I'm a full-stack engineer who's shipped and maintained Next.js (App Router), React, and TypeScript apps under real production load. I kept watching AI write code that looked done - then leaked NEXT_PUBLIC_ secrets, swallowed errors, and skipped every state but "success." Shipwright distills the senior-engineer checklist I reach for when things break at 2 a.m. - secrets, auth, input validation, caching, and the unhappy paths - so your AI ships production-grade code, not demos.
Assess Expo release readiness with evidence-based priorities.