Google Antigravity

{
  "video": "/adom/antigravity/render/first-ai-pcb/videos/first-argon-ai-pcb.mp4",
  "title": "My first AI PCB: Gemini 4 Argon designs a PCB in Antigravity",
  "poster": "/adom/antigravity/render/first-ai-pcb/videos/first-argon-ai-pcb.jpg",
  "captions": "WEBVTT\n\n00:00:05.513 --> 00:00:13.900\nGemini 4 Argon, Google's newest model, designs a printed circuit board from a single sentence, inside Adom Hydrogen.\n\n00:00:15.393 --> 00:00:19.472\nThis is Adom Hydrogen, running on a remote office PC.\n\n00:00:19.522 --> 00:00:26.079\nWe installed Google's Antigravity extension into Hydrogen's editor, and after one reload its side bar appeared.\n\n00:00:26.129 --> 00:00:31.448\nClicking Continue with Google brought up Hydrogen's own browser picker, then Google's sign-in.\n\n00:00:31.498 --> 00:00:35.164\nOur new team account needed a single phone check.\n\n00:00:35.214 --> 00:00:40.119\nThen Antigravity greeted us with Gemini 4 Argon, Google's newest frontier model.\n\n00:00:40.169 --> 00:00:43.423\nNext, we hand Argon the buck converter prompt.\n\n00:00:44.930 --> 00:00:54.369\nHere is the whole prompt: make a twelve to five volt buck converter with the TPS54202, use adom-aiflow to guide you, and use KiCad.\n\n00:00:54.419 --> 00:01:03.463\nWith no other hints, Gemini 4 Argon found the adom-aiflow skill on its own, then read the intake, circuit, sourcing and layout guides.\n\n00:01:03.513 --> 00:01:08.998\nIt wrote a design brief and a requirements file, and started an aiflow run.\n\n00:01:09.048 --> 00:01:15.720\nThen the AI Flow timeline opened by itself in Hydrogen's right pane: intake done, design rules next.\n\n00:01:16.930 --> 00:01:21.252\nFor the next hour, Argon worked through the design on its own.\n\n00:01:21.302 --> 00:01:30.724\nIt wrote its own buck calculations and a four hundred line simulation, chose the parts, wrote the bill of materials, and generated the schematic and netlist.\n\n00:01:30.774 --> 00:01:39.103\nIt asked a few times for permission to run commands, and we reminded it once to leave a colleague's open KiCad boards alone.\n\n00:01:39.153 --> 00:01:45.660\nThen its board opened in KiCad: a fresh project, placed and routed, ten nets and zero unrouted connections.\n\n00:01:46.967 --> 00:01:53.701\nOnce KiCad was free, Argon reopened its board through kicad-bridge and let aiflow run the checks.\n\n00:01:53.751 --> 00:02:05.997\nThe dashboard raced through routing, heatsink vias, copper pours, rounded corners, current, thermal, fields and silkscreen, then toured the finished board in KiCad's 3D viewer, with simple placeholder parts.\n\n00:02:06.047 --> 00:02:18.717\nTwo and a half hours after the prompt, aiflow delivered: zero DRC errors, zero unconnected nets, and Gerbers, bill of materials and pick and place files, ready for the fab.\n\n00:02:19.991 --> 00:02:28.900\nThe result: a DRC-clean twelve to five volt buck converter, two and a half hours from prompt to finished board, ready for the fab.\n",
  "chapters": [
    {
      "t": 0,
      "title": "Intro"
    },
    {
      "t": 5.0,
      "title": "The prompt"
    },
    {
      "t": 14.4,
      "title": "Antigravity signs in inside Hydrogen"
    },
    {
      "t": 44.4,
      "title": "Argon finds adom-aiflow"
    },
    {
      "t": 76.4,
      "title": "An hour of design, then KiCad"
    },
    {
      "t": 106.5,
      "title": "Checks race to 100 percent"
    },
    {
      "t": 139.5,
      "title": "The result"
    },
    {
      "t": 149.3,
      "title": "Adom"
    }
  ]
}