ALT Card 1 of 4 (Title Hook with Illustration): Google Open Source banner for "Introducing the Elephant-Goldfish Model Plugin for Design-Driven AI Coding" featuring the official minimalist split mark logo with a blue elephant profile and an orange goldfish profile. By the Elephant-Goldfish Model (EGM) Team: Brian Suchy, Jim Quinn, Elise Ewing, and Dave Rensin (Google). Subheadline: Pure AI coding speed without structured design auto-scales mistakes. Meet the open source framework keeping human judgment in the loop. Highlights: (1) Separates long-horizon design (Elephants) from stateless validation (Goldfish); (2) Used daily by thousands of Google engineers in production; (3) Apache 2.0 plugin: Markdown rules and subagent personas. Core principle quote: "Design is the new code — human judgment is the only artifact that truly matters."

ALT Card 2 of 4 (The 3-Phase EGM Lifecycle — From "No-Code" Brainstorming to Stateless Spec Validation): Stacked breakdown of the 3 co-design phases automated by the plugin: (1) Phase 01 (egm-brainstorm) — Long-Horizon "No-Code" Session: Growing the Elephant. Load system context and adhere to a strict "No Code" rule where the AI interviews you to co-design features, debate trade-offs, and challenge assumptions. (2) Phase 02 (egm-draft) — Executable Markdown Blueprint: Drafting with the Elephant. Iteratively draft a Markdown design spec covering problem definition, architecture, alternatives, and exact files to change. (3) Phase 03 (egm-review) — Zero-Context Adversarial Critics: The Goldfish Protocol. Spawn fresh, stateless Goldfish subagents with zero blind spots to probe the spec for ambiguity and logical gaps.

ALT Card 3 of 4 (Inside Phase 3 — How Stateless AI Reviewers Stress-Test Your Design Spec): Top cards contrast The Elephant (Long-Horizon Context-Rich Architect holding end-to-end architectural vision, project memory, and micro-decisions with zero code written) vs. The Goldfish (Zero-Context Stateless Skeptical Critic starting fresh with zero shared blind spots or sunk-cost bias to interrogate the Markdown spec objectively). Bottom terminal (egm-review — 3-Step Goldfish Validation Sequence): Step 1 Comprehension Check (naive reader summarizes spec back; flags ambiguous architecture or intent); Step 2 Antagonistic Review (skeptical personas probe edge cases; surfaces hidden dependencies and logical gaps); Step 3 Implementation Readiness (strict Go/No-Go gate verifying file paths, data structures, and signatures); Output: Validated Markdown Spec.

ALT Card 4 of 4 (X/Twitter Action Card — Explore the Open Source EGM Plugin & Rules on GitHub): Top box lists What is in the Apache 2.0 GitHub Repository: Authors Brian Suchy, Jim Quinn, Elise Ewing, and Dave Rensin (EGM Team); Repository github.com/google/elephant-goldfish-model (Apache 2.0); Included customizable Markdown rules, subagent personas, and workflows; Built for Google Antigravity (more IDEs upcoming). Middle box lists How to Get Started & Contribute: (1) Install the EGM plugin in Antigravity to automate Phases 1–3; (2) Customize validation rules and antagonistic Goldfish reviewer personas; (3) Shift from code micromanager to executive architectural reviewer. Bottom call to action: Read the Blog Post & Explore the GitHub Repo at https://goo.gle/elephant-goldfish-plugin (first reply below). Footer: @GoogleOSS.