Vibes: Building an Asset Repository with AI
2026
Role
Creative Lead / Builder
The Story
With a recent reorg and shifting priorities, marketing efforts for our mobile app were deprioritized as the team’s focus moved elsewhere. We were tasked with wrapping up ongoing app work and preparing the screens for future use.
The challenge: we’d been relying on a patchwork of Google Sheets and Figma files to track UI screens, design partners, and product contacts. There was no single source of truth linking the screens to their owners.
The opportunity was clear. I needed to build an easily accessible, quick-turn resource site for the team — one that links to essential contacts, relevant Figma files, and Drive assets, with content simple enough to update from a spreadsheet. The design needed to be intuitive enough that a new team member could pick it up without a walkthrough.
The Process
Vibe Coding with Gemini
01. Prompt
I started with a simple ask: help me build a site featuring multiple UI screens, contacts, and relevant links. From there, I worked with Gemini to shape an architecture around three parts — a backend for data and image handling, a responsive frontend, and a Google Sheet as the database.
02. Organize
A Google Sheet was set up with two tabs, Resources and Digital Priority Features, kept intentionally clean so content could be updated without touching code. I converted image links to a web-friendly format for faster loading and integrated the Directory Tools plugin to streamline edits.
03. Develop
Most of the time went into refining index.html — getting layout and copy right. Working with Gemini meant proofreading closely for unprompted text changes and asking clarifying questions to sharpen my prompts.
The Takeaway
In a three-day sprint, I moved through 50+ submitted prompts and 80 test deployments to land on a shareable site that now serves as the team’s central repository for screens and resources. From there, I took what I learned and shared it with peers through live demos and 1:1 walkthroughs.
