Code style

Code style

* Notebooks are for people. Write code optimized for clarity.
* Use the [Google Python Style Guide](http://google.github.io/styleguide/pyguide.html), where applicable. Code formatted
  by [`pyink`](https://github.com/google/pyink) will always be accepted.
* Ideally, if you define a function, run it and show us what it does before using it in another function.
* Demonstrate small parts before combining them into something more complex.
* Only use helper function when you don't have a choice. If it's only a couple of lines, it's usually better to write them
  everytime so that the readers don't have to check the function definition all the time.
* When selecting a model, use a colab selector for easier maintainability:
  `MODEL_ID="gemini-3.6-flash" # @param ["gemini-3.1-flash-lite", "gemini-3.5-flash-lite", "gemini-3.6-flash", "gemini-3.1-pro-preview"] {"allow-input":true, isTemplate: true}`
* Some notebooks can also benefit from having a form to update the prompt:
  `prompt = "Detect the 2d bounding boxes of the cupcakes (with “label” as topping description”)"  # @param {type:"string"}`
  or a list of prompts they can choose from:
 `prompt = "Draw a square around the fox' shadow"  # @param ["Find the two origami animals.", "Where are the origamis' shadows?","Draw a square around the fox' shadow"] {"allow-input":true}`
* The API key should always be gathered from the `GEMINI_API_KEY` colab secret. If the code is using the legacy `GOOGLE_API_KEY` secret, ask them to update it.