ai-orchestrator

Use when writing, editing, polishing, or reviewing public-facing prose such as external emails, blog posts, website copy, social posts, newsletters, proposals, bios, press notes, or customer-facing docs; especially when the user says use my tone, match my tone, sound like me, use my voice, avoid AI-sounding writing, ChatGPT style, AI tells, em dashes, formulaic phrasing, corporate filler, or generic polished copy.

Audit a web UI with browser automation, chrome-devtools, viewport sweeps, screenshots, and axe accessibility evidence

Non-destructive visual upgrade of an existing React/web UI. Separates sacred logic from replaceable styling, applies all changes through a single load-last gold.css override so one import removal reverts everything, and gates completion on a functionality checklist. Use for "redesign this ui", "visual overhaul", "make this look designed". Do not use for backend work, logic changes, new features, or bug fixes.

API-first Android Google Play release workflow. Use when releasing, uploading, staging, or preparing an Android build for Play Console, including Capacitor apps, versionCode bumps, signed AAB creation, Play Developer Publishing API uploads, tracks, rollout, listings, store images, tester lists, and Play-console browser fallback flows.

Checkpointed browser workflow for first-time Apple App Store Connect and Google Play Console app setup. Use for creating new app records, Play Content rating, Data safety, app-content declarations, app access credentials, ASC app records, privacy nutrition labels, agreements/tax prompts, Resolution Center review replies, and console-only setup for a new white-label brand.

API-first iOS App Store/TestFlight release workflow. Use when releasing, uploading, submitting, or preparing an iOS build for TestFlight or App Store Connect, including Capacitor apps, version bumps, altool upload, ASC API build processing, export compliance, TestFlight group attachment, metadata, screenshots, or submit-for-review steps.

Verify @contracts subpaths stay in sync across the three alias sites the packaged DMG depends on.

Keep documentation aligned with the current codebase; flag drift between docs and reality.

Find the highest-signal recurring error in local logs, trace it, and propose a verified fix.

Act as a first-time user following the README, surface the first hidden setup assumption.

Find flaky tests, fix their root cause, and prove stability with repeated runs.

Spawn multiple children to review code from different quality dimensions

Spawn children to debate a technical decision from opposing viewpoints

Spawn multiple children to research a topic from different angles

Analyze and synthesize results from multiple child instances

Spawn multiple children to verify implementation meets requirements from different angles

Test an Android app on a leased worker emulator or physical device using mobile-mcp and adb evidence