rawkintrevo

QA a Mapache preview with the runner-owned browser QA command, status checks, console logs, screenshots, and structured reports.

Host an app or API behind the Mapache preview gateway.

Work from or create GitHub issues with repository context, labels, clarification, and implementation flow.

Build static web output where the Mapache preview canvas can serve it.

Run or compose Mapache browser QA tests from checked-in e2e/qa case manifests using Chrome DevTools. Use when the user explicitly asks for QA testing, smoke testing, browser testing, end-to-end testing, or a named QA case, and when issue-workflow changes frontend behavior and requires QA before PR completion.

Use when the user provides a GitHub issue number and wants Codex to complete the whole implementation workflow: update local main from remote, read the issue and comments, create an issue-named branch, implement and test the change, compose and run QA for frontend changes, commit, push, open a pull request, return to main, and comment or label the issue when blocked or waiting on user action.

Route agents through the Mapache developer wiki before non-trivial implementation work.

Enforce Mapache wiki update requirements after changes that affect architecture, runtime, deployment, or workflow behavior.

Plan a tightly scoped new app from a product idea or from a URL used as inspiration. Use when the user wants Codex to clarify a V1 app concept, constrain scope, define a React/Vite/Firebase architecture, plan Stripe pricing, Resend lifecycle emails, analytics, SEO, legal pages, testing, deployment, and create GitHub issues for the implementation tasks. Also use when the user asks to clone an app in the sense of using its copy, messaging, pricing, or flows as a guide rather than copying it exactly.

Convert app plans, design docs, product briefs, or launch checklists into implementation-ready GitHub issues. Use when Codex needs to create coding issues, human setup issues, labels, milestones, dependencies, acceptance criteria, test notes, env var placeholder tasks, parallel workstreams, or copy-ready issue bodies for building a scoped app.

Plan, configure, implement, verify, and operate Firebase for React/Vite web apps. Use when Codex needs to handle Firebase Hosting, Auth, Firestore, Security Rules, Cloud Functions for Firebase, Local Emulator Suite, Firebase CLI, Google Analytics, Remote Config, A/B Testing, env config, GitHub Actions deploys, launch checklists, or human Firebase setup tasks.

Plan, implement, verify, and operate Resend lifecycle email for web apps. Use when Codex needs to handle Resend API keys, verified sending domains, DNS records, SDK setup, transactional email sending, templates, lifecycle email plans, webhooks, unsubscribe/compliance notes, testing, logging, or human Resend Dashboard setup tasks.

Plan, implement, audit, and launch SEO for web apps and marketing sites. Use when Codex needs to handle foundational SEO, metadata, keywords, robots.txt, sitemap.xml, canonical URLs, structured data, Open Graph/Twitter previews, preview images, social sharing, technical SEO, AI/LLM visibility, entity/topic clusters, E-E-A-T proof, multichannel visibility, SEO launch QA, or docs for SEO operations.

Plan, implement, verify, and operate Stripe SaaS billing. Use when Codex needs to handle Stripe Checkout, subscriptions, products, prices, customer portal, webhooks, entitlements, test-mode verification, Stripe CLI workflows, billing docs, secret management, or human Stripe Dashboard setup tasks for a web app.

Use for Firebase operations in the Gofannon Mk III project, including scoped deploys, Functions and gcloud log inspection, emulator startup and troubleshooting, Firestore/Storage/Remote Config rule deploys, project switching, and Firebase CLI recovery steps.

Use when the user says "next task" or asks to continue the app implementation plan from app_plan.md/task_list.md. Select the next incomplete task, implement it, mark it complete, test, commit, and report the next task.

Use after code edits, bug fixes, or feature additions in the Gofannon Mk III web app to verify the change end-to-end with a localhost browser flow, automatic test authentication when safe, frontend console capture, Firebase or emulator backend log review, screenshots, cleanup, and a pass/fail report.