Moving Your Architectural Standards into AntiGravity
During my first few days working with AntiGravity and the Coda MCP, I found myself correcting the same basic mistakes time after time.
As a expert, I have specific ideas about data architecture. I prefer ForEach() over FormulaMap(), WithName() over Let(), and Format() over long Concatenate() chains. My display columns are always named Name with unique values, my core tables always carry the DB prefix, and I follow a strict "one table, one page" rule to keep docs human-friendly. Without specific instructions, the AI ignores all of this — defaulting to generalised patterns that blend spreadsheet logic with conventions that have no place in a well-structured Coda doc.
For those who assume agents are more magic than craft: they are not. An agent is a set of textual instructions you write — sometimes with AI assistance — that shape how the model you use, behaves. The more precisely those instructions reflect your thinking, the more useful the agent becomes.
I draw on years of blogging and client work to populate my file, and I update it regularly. Each update is triggered by something specific: a pattern the agent mishandled, or a rule I had been applying intuitively but never written down. Over time the file becomes a cumulative record…
