We hear that "AI will write the code." So I put it to the ultimate test. I tasked an AI Agent with porting my legacy Windows strategy game to a modern .NET MAUI app on iOS, Android, and Windows. But I added one strict rule: I will not write a single line of code.

No quick fixes, no "I'll just tweak this function." If the UI broke, I had to write a Spec, not a patch. In this session, I will show you why this was the hardest thing I have ever done—and why it is the future of software engineering.

We will move from the failure of "Vibe Coding" (where the agent hallucinated spaghetti code) to the discipline of Spec-Driven Development. You will see how I architected a system where the Agent didn't just read errors—it "looked" at the app. I implemented an automation suite that captured screenshots on failure, creating a visual feedback loop that allowed the Agent to see UI glitches and fix them autonomously.

We will cover:

The "Handcuffs" Experiment: The agony of resisting the urge to code, and how it forced me to become a better Architect.

The "Steering Document": Replacing prompts with a living Constitution that prevented context drift.

Multimodal Debugging: How I built a pipeline where the Agent runs UI automation tests, analyzes the resulting screenshots, and self-corrects visual bugs.

The Result: A live demo of a game shipped 100% by AI, governed 100% by a human.

Target Audience: Developers, Architects, and Engineering Managers who are skeptical about AI's ability to handle complex, real-world engineering tasks.

Preferred Session Duration: 45–60 Minutes.

Technical Requirements:
Stable Internet connection (Critical for live AI Agent interaction).
Projector (HDMI/USB-C) for code and mobile emulator display.
Audio output (The demo includes game sound effects).
Theme Alignment: Fits tracks related to AI Engineering, .NET MAUI / Cross-Platform, and Software Architecture.

Key Takeaways
Discipline Over Syntax: Why the inability to write code forces you to master Architecture and Specification.

Visual Agents: How to implement Multimodal Testing (Logs + Screenshots) to let agents solve UI problems.

The "Steering" Methodology: Master the art of Spec-Driven Development by replacing vague prompts with a living "Steering Document" (Constitution) that prevents context drift and hallucination.