DDS Vibe Academy · Application

One-Prompt App Library 2.0

The go-to guide for Shopify owners: build real store tools from a single prompt in Google AI Studio Build mode. Thirty-six paste-ready apps across Basic, Advanced, and Master.

  • Apps36
  • TiersBasic / Adv / Master
  • CostFree
  • Read120 min
  • PublishedMay 31, 2026
Jump to the apps How the tiers work
Your one prompt BASIC client-side paste output ADVANCED full-stack 1M context MASTER Firebase deployed capability ladder
One prompt feeds three ascending tiers, from paste-in Basic to deployed Master.

Quick Answer

A one-prompt app is a working Shopify tool you build by pasting a single prompt into Google AI Studio Build mode, which since Google I/O 2026 runs on Gemini 3.5 Flash with a one-million-token window and builds full-stack apps. This 2.0 library gives you 36, tiered Basic, Advanced, and Master, and names the model and cost for each.

Key takeaways

  1. AI Studio Build mode is now full-stack and Antigravity-powered: React plus Node, npm, Firebase, and Cloud Run, from a prompt.
  2. Gemini 3.5 Flash is the default since Google I/O 2026, about 4x faster than comparable frontier models at lower cost.
  3. The one-million-token window lets an app reason over your whole catalog, policies, or hundreds of reviews at once.
  4. Client-side apps run on the end user's key, so most apps here are owner-side tools that cost nothing to use privately.
  5. A Cloud Run deployment uses your key for every visitor, so customer-facing apps carry real, usage-scaling cost.
  6. Thirty-six apps, tiered by capability: Basic paste-in tools, Advanced catalog-wide tools, Master stateful deployed tools.

What the One-Prompt App Library Is

A one-prompt app is a working tool you build by pasting a single prompt into Google AI Studio Build mode. This 2.0 library is thirty-six of them for Shopify owners, sorted into Basic, Advanced, and Master. Each prompt is written for AI Studio specifically and names the model, the data, and the deploy path.

The first edition of this library, still live as the original 85-prompt collection, listed prompts that ended with the generic instruction to use an AI API. It did not say which build environment, which model, who pays for inference, or how an app is deployed. It was a prompt list.

This 2.0 edition is rebuilt around one platform that changed materially at Google I/O 2026 on May 19 and 20, 2026: Google AI Studio Build mode. After that update, Build mode is no longer a client-side snippet generator. It builds full-stack applications, it installs npm packages, it provisions Firebase, and it deploys to Google Cloud Run, all from natural-language prompts. The model behind it is Gemini 3.5 Flash, with a one-million-token context window.

Three things define the rebuild. Every prompt is written for AI Studio specifically and names the model it should use. The library is tiered by technical envelope, not by difficulty. And it is honest about who pays for each app to run, which is the single fact the first edition omitted. The result is a remedy catalog: thirty-six tools mapped to the real problems a Shopify store faces.

Source: Google AI for Developers, "Build apps in Google AI Studio"; Google I/O 2026 coverage, May 2026.

How AI Studio Build Mode Works

Build mode is powered by the Antigravity Agent, the same harness behind Google Antigravity. You describe an outcome; it generates a full-stack app, a React client plus a Node.js server, and shows a live preview. It manages multiple files, installs npm packages, and verifies its own code to reduce hallucinations.

You start a build three ways: type a prompt and attach AI Chips for features like image generation or Google Maps; press "I'm Feeling Lucky" for a generated project idea; or remix a project from the App Gallery with Copy App. Once you run the prompt, the code and files appear with a live preview on the right.

By default AI Studio creates a full-stack environment. The client is a React frontend; the server is a Node.js runtime that allows secure API calls, database connections, and npm usage. The Antigravity Agent manages the files across that stack, propagating changes correctly. Google lists its capabilities as context awareness across prompts and file states, multi-file dependency management, and verified execution to reduce hallucinated code.

You refine an app three ways: the Build-mode chat panel, direct edits in the Code tab, and annotation mode, which lets you highlight any part of the rendered UI and describe the change in place. When an app is ready, you export it as a ZIP, push it to GitHub, or deploy it to Cloud Run for a public URL.

Source: Google AI for Developers, "Build apps in Google AI Studio," last updated April 28, 2026.

The Models Doing the Building

Gemini 3.5 Flash is the default model in AI Studio since Google I/O 2026, and Google calls it its strongest agentic and coding model, running about four times faster than comparable frontier models. Use Gemini 3.1 Pro for the hardest reasoning, 3.1 Flash-Lite for high-volume work, and Nano Banana for images.

Naming the model matters, because each app in this library specifies one. The current lineup, verified against Google's documentation:

  • Gemini 3.5 Flash is generally available and the default in AI Studio, the Gemini API, the Gemini app, and Search. Google reports it outperforms Gemini 3.1 Pro on coding and agentic benchmarks while running roughly 4x faster, often at less than half the cost. It is the right default for nearly every app here.
  • Gemini 3.1 Pro is the heavy-reasoning option; it is free to try inside AI Studio. Reach for it on the hardest analysis.
  • Gemini 3.1 Flash-Lite is the cost-efficient workhorse with a free API tier, suited to high-volume tasks.
  • Gemini 3.5 Pro was announced at Google I/O 2026 with general availability stated as expected in June 2026; treat it as forthcoming.

For visuals, Nano Banana Pro (Gemini 3 Pro Image) produces professional assets up to 4K with high-fidelity text, and Nano Banana 2 (Gemini 3.1 Flash Image) is the high-volume option. Veo 3.1 generates video and Lyria 3 generates music. Every generated image, video, and audio file carries an invisible SynthID watermark, which is worth disclosing when you use generated product imagery.

All Gemini 3-series models accept a one-million-token input and produce up to 64,000 output tokens, and support Google Search, Maps grounding, File Search, Code Execution, and URL Context as tools.

Source: Google AI for Developers model and changelog pages; blog.google Gemini 3.5 announcement, May 2026.

Anatomy of a One-Prompt App

Every prompt in this library follows five blocks: the outcome in one sentence, the model to use, the data and context to work from, the features to build, and the validation that proves it works. Advanced and Master prompts add a deploy block. The structure is the transferable skill; the apps are worked examples.

A vague prompt produces a vague app. The five-block shape forces the decisions that make a build usable:

  1. Outcome. The finished tool in one sentence. Name the artifact, not the activity.
  2. Model. Which Gemini model to call, and which media model if the app generates images. Defaults to Gemini 3.5 Flash.
  3. Data and context. What the app works from: input fields for a Basic app, or a pasted catalog, policy set, or review corpus for an Advanced one. This is where the one-million-token window earns its place.
  4. Features. The functional specification: inputs, outputs, copy buttons, counters, export formats, error and loading states.
  5. Validation. How correctness is checked before you trust the output: a character count, a reconciliation against the source, a schema check.

Advanced and Master prompts append a sixth block, deploy, covering secrets, Firebase, and whether the app stays in preview or goes to Cloud Run. Read the five blocks once and every prompt below becomes editable rather than fixed; change the specifics to match your store.

Source: DDS Vibe Academy build standard; AI Studio Build-mode prompting guidance.

The 1M-Token Context Playbook

Gemini's one-million-token window holds about 1,500 pages of text or 30,000 lines of code in a single session. For a store owner, that means an app can reason over your entire catalog, every policy, or hundreds of reviews at once, instead of working one product at a time. This powers the Advanced and Master tiers.

Historically, large language models accepted only a few thousand tokens, so working with a big dataset meant chunking it, summarizing it, or standing up a vector database. Google's guidance with a one-million-token window is the opposite: provide all relevant information upfront and let the model reason across it in context.

That reframes what one app can do. A Basic generator writes one product description at a time. An Advanced app ingests your full product export as a CSV and audits every row in one pass. A Master app holds your entire brand guide, catalog, and policy set in context and drafts on demand against all of it. The same shift turns review handling from one-at-a-time into mining hundreds of reviews for themes and sentiment in a single run.

The honest limits are cost and attention. Very large inputs consume more tokens, and detail buried in the middle of a huge context can be under-weighted. Context-stuffing is a precise tool, not a default for every task. Use it when the job genuinely needs the whole dataset, and keep individual inputs scoped when it does not.

Source: Google AI for Developers, "Long context"; Gemini Apps Help.

Who Pays: The Cost Model

AI Studio is free to build in; you bring a Gemini API key, and Gemini 3 Flash and 3.1 Flash-Lite have free tiers. Client-side apps call Gemini through a proxy keyed to the end user's key, so most apps here are owner-side tools you run privately. A deployed Cloud Run app uses your key for every visitor.

This is the section the first edition omitted, and it determines what each app is for.

When you share an AI Studio app, its client-side Gemini calls go through a proxy that substitutes the end user's API key, not yours. The placeholder process.env.GEMINI_API_KEY is replaced at run time. Never put a real key in client code, because the code is visible to anyone who can open the app.

The consequence: most apps in this library are owner-side tools. You run them in the AI Studio preview, or share them privately, against your own key, often on a free tier. They are not free customer-facing widgets. The moment you want shoppers to use an app, you deploy it to Cloud Run, which gives a public URL with a proxy that keeps the key private but bills every visitor's Gemini calls to your key. A storefront quiz or gamification app therefore carries real, usage-scaling cost plus Cloud Run charges, and its key handling must stay server-side. That line, owner-side versus customer-facing, is the one to hold in mind for every build below.

Source: Google AI for Developers, Build-mode FAQ and API key guidance.

The Deploy Decision

Three destinations: keep an app in the AI Studio preview for personal use, share it privately with collaborators who run it on their own key, or deploy to Google Cloud Run for a public URL. Preview and private share cost nothing beyond your free tier. Cloud Run adds hosting cost and bills inference to your key.

Match the destination to the audience:

  • Preview. The fastest path. You use the app yourself inside AI Studio and paste its output into Shopify by hand. Every Basic app belongs here by default.
  • Private share. Share the app with a teammate or contractor; they run it against their own key, and they can view and fork the code. Edit access for others is stated as coming soon.
  • Cloud Run. A scalable public URL for an internal team tool or a customer-facing app. Cloud Run pricing applies, and the deployed app uses your key for all users, so keep API-key logic server-side and monitor cost.

You can also export the app as a ZIP or push it to a GitHub repository to continue in your own editor; note that AI Studio's GitHub integration creates and commits, but pulling remote changes is not yet supported. For most store owners, the honest answer is that the preview and private share cover the majority of this library at zero marginal cost, and Cloud Run is reserved for the few apps shoppers actually touch.

Source: Google AI for Developers, Build-mode deploy and export documentation.

Security, Governance, and Honest Limits

Never put a real API key in client code; use Secrets Management for server-side keys. Apps are private by default, and you own their behavior and data. AI Studio reviews apps for policy violations. The real limits: it is a desktop browser build experience, GitHub pull is unsupported, and context-stuffing has cost ceilings.

The guardrails worth knowing before you build:

  • Keys. Real keys never go client-side. Server-side keys live in Settings under Secrets Management, readable only by server code.
  • Privacy. Apps are private by default. Sharing lets others view and fork the code.
  • Device APIs. Microphone, camera, geolocation, and similar Navigator features must be declared in the app's metadata.json via requestFramePermissions.
  • Storage. Apps run in a Cloud Run container and can reach any network-accessible store; built-in storage configuration is stated as coming.
  • Policy. Apps are automatically reviewed; violations such as malware, phishing, or prohibited content are removed, with an appeals path. As the owner you are responsible for legal compliance, third-party rights, and content monitoring.

The functional limits are honest ones: the full build experience is a desktop browser today, with a mobile app newly introduced; GitHub remote pull is not supported; and the one-million-token window is input-side with capped output, so large context costs more and can dilute attention. None of these block the library; they shape which tier a given app belongs in.

Source: Google AI for Developers, Build-mode limitations and FAQ.

How These Fit a Shopify Store

These are standalone tools, not Shopify Admin apps. They do not install into your admin or read store data automatically. You paste their output into Shopify by hand, or embed a deployed app by link. You can wire one to the Shopify Admin API from the server-side runtime using secrets, but that is a deliberate Advanced or Master step.

It is important to set the expectation precisely. An AI Studio app is not listed in the Shopify App Store and does not appear inside your Shopify admin. It runs in a browser, on Google's infrastructure, separate from your store.

For the Basic tier, that is exactly right: you generate a product description, an SEO title, or a set of alt-text strings, and you paste the result into the relevant Shopify field. The tool's job is to produce correct, on-brand text fast; moving it into Shopify is a copy and paste.

For Advanced and Master apps, you can go further by connecting the server-side runtime to the Shopify Admin API with a token stored in Secrets Management, so an app reads a live product list or writes a draft. That is a deliberate wiring step, not an automatic capability, and it carries the same key-security rules as any server-side integration. Most owners will start with paste-in tools and graduate a few high-value workflows to a connected, deployed app.

Every app below maps to a documented Shopify pain point: the average Shopify conversion rate sits near 1.4%, below the 2 to 4 percent ecommerce norm, and the durable levers are clearer product information, stronger SEO against rising ad costs, trust signals, and retention. The library is organized as a response to those.

Source: dated 2026 Shopify and ecommerce coverage; Google Build-mode integration guidance.

The Three Tiers

Basic apps are single-prompt, client-side, and run free in the preview; you paste output into Shopify. Advanced apps use the full-stack runtime, npm packages, and the 1M-token window to work over whole catalogs. Master apps add Firebase storage, sign-in, and Cloud Run deployment to become real, stateful, multi-user tools.

The tiers are technical envelopes, not difficulty ratings. Each names what the app may use:

TierEnvelopeRuns whereCost to run
BasicSingle prompt, client-side, no persistenceAI Studio previewFree tier; your key, private
AdvancedFull-stack, npm, 1M-token context, secretsPreview or private Cloud RunFree tier privately; Cloud Run if shared
MasterFirebase (Firestore + Auth), multiplayer, deployedCloud RunCloud Run plus inference on your key

The progression is deliberate. Start in Basic to get fast, correct text and assets with zero setup. Move to Advanced when a job needs your whole catalog or policy set in context, or an npm library for parsing and charts. Reach Master only when an app must remember data, sign users in, or serve more than one person. Each tier below opens with its own short brief, then the twelve apps.

Source: DDS Vibe Academy tier model; Google Build-mode capability documentation.

Choosing the Right Model

Default to Gemini 3.5 Flash for almost everything; it leads on coding and agentic work at about four times the speed of comparable frontier models. Switch to Gemini 3.1 Pro only for the hardest reasoning, 3.1 Flash-Lite for cheap high-volume runs, and Nano Banana for images. Naming the model in your prompt is part of the craft.

Every prompt in this library names a model, because the choice changes cost, speed, and quality. The decision is simple once mapped to the job:

JobModelWhy
Most generation and full-stack buildsGemini 3.5 FlashDefault; leads coding and agentic benchmarks at about 4x speed, lower cost
Deep reasoning: personas, clustering, brand brainGemini 3.1 ProStrongest reasoning; free to try in AI Studio
High-volume, latency-sensitive batch workGemini 3.1 Flash-LiteCost-efficient workhorse with a free API tier
Professional product imagery, up to 4KNano Banana ProReasoning-driven image model with high-fidelity text
High-volume image generationNano Banana 2Speed-optimized image model

Two practical notes. Gemini 3.5 Pro was announced at Google I/O 2026 with general availability stated as expected in June 2026, so it is not yet a choice you can rely on today. And whenever an app does arithmetic, instruct it to compute in code rather than in the model, regardless of which model you pick; the pricing calculators and payout trackers in this library all do this. The model writes the words; JavaScript computes the numbers.

Source: Google AI for Developers model pages; blog.google Gemini 3.5 announcement, May 2026.

Five Context-Stuffing Recipes

The one-million-token window rewards pasting whole datasets. Five recipes recur across this library: the full catalog CSV, the complete policy set, a large review corpus, the entire brand guide, and a page-list for internal linking. Each turns a one-at-a-time tool into one that reasons across everything at once.

Context-stuffing is the technique behind every Advanced and Master app. The recipes:

  1. The whole catalog. Paste your full product export as CSV. The auditor and the bulk description factory reason over every row in one pass instead of looping product by product.
  2. The complete policy set. Paste shipping, return, refund, and warranty policies. The support composer answers only from them and cites the passage behind each claim.
  3. A large review corpus. Paste hundreds of reviews. The mining dashboard extracts themes, sentiment, and verbatim testimonials across the entire set.
  4. The entire brand guide. Paste your guide once and keep it loaded. The brand-voice linter and the brand brain check or generate against the full document for a whole session.
  5. The page list. Paste every page as title and URL pairs. The internal-link planner suggests only real links and finds orphan pages.

The discipline is to stuff context only when the job genuinely needs the whole dataset. The window holds roughly 1,500 pages, but very large inputs cost more tokens and can dilute attention on a detail buried mid-context. Scope the input to the task: a single product description does not need your whole catalog, but a catalog audit does.

Source: Google AI for Developers, "Long context."

Wiring an App to the Shopify Admin API

Advanced and Master apps can read and write live Shopify data by calling the Admin API from the server-side runtime. Store an Admin API access token in Secrets Management, never in client code, and have the Node server call the Admin REST or GraphQL endpoint. This is a deliberate step, not an automatic capability.

Most of this library is paste-in by design, but a few high-value workflows are worth connecting to live store data. The pattern is the same as any secure server-side integration:

  1. Create a token. In your Shopify admin, create a custom app and generate an Admin API access token with only the scopes the tool needs, for example read access to products.
  2. Store it as a secret. In AI Studio, add the token under Settings as a secret. It is readable only by your server-side code and never reaches the client.
  3. Call from the server. Have the Node runtime call the Admin API, for example a GET to the products endpoint at /admin/api/2026-01/products.json with the token in the X-Shopify-Access-Token header, and return only what the app needs to the client.
  4. Write deliberately. For writes, prefer creating drafts a human approves, not silent live edits, and log every write.

Tell the AI Studio agent exactly this in your prompt: that the Shopify token lives in Secrets Management, that all Admin API calls happen server-side, and that the client never sees the token. The same rules apply to any other service you connect. This connected pattern is what turns the catalog auditor or the bulk description factory from a paste-in tool into one that reads your live catalog directly.

Source: Google AI for Developers Build-mode secrets and integration guidance; Shopify Admin API documentation.

Worked Example: The Catalog-Wide SEO Auditor

Here is one Advanced app built end to end. Paste the prompt, upload your product CSV, let the agent install a CSV parser, review the scored table in the preview, and export the audit. The whole build is free in the preview on your own key. Every Advanced app follows the same five steps.

The pattern that builds every Advanced app, shown on the catalog auditor:

  1. Paste the prompt. Open Build mode and paste the Catalog-Wide SEO Auditor prompt. AI Studio generates a full-stack app, a React client and a Node server, with a live preview on the right.
  2. Let it install npm. The Antigravity Agent recognizes it needs a CSV parser and installs the package automatically. You do not configure anything.
  3. Upload your catalog. Export your products from Shopify as CSV and paste or upload it. The one-million-token window lets the app hold the whole file and score every row in one pass.
  4. Review in the preview. A sortable table shows a score and the top fixes per product. If a column is wrong, use annotation mode: highlight the table and describe the change in place.
  5. Export and act. Export the audit as CSV, sort by lowest score, and fix the worst products first. Nothing was deployed; the app and your data stayed in the preview, free on your own key.

To make it permanent, connect it to the Shopify Admin API as described above so it reads your live catalog instead of a pasted CSV, then deploy it privately to Cloud Run for a teammate. Start in the preview; graduate only the workflows that earn it.

Source: Google AI for Developers Build-mode documentation; this library's auditor prompt.

The AI Studio Prompting Playbook

Write the five blocks deliberately. Name the artifact, not the activity. Specify the model. Say exactly what data the app works from. List features as concrete behaviors with states. Declare how correctness is checked. A vague block produces a vague app; a precise one produces a usable tool on the first run.

Each block has a failure mode and a fix. Use this as a checklist when you adapt any prompt here:

  • Outcome. Vague: "help with product copy." Precise: "a generator that outputs four ready-to-paste description lengths with copy buttons." Name the finished artifact and how it is used.
  • Model. Always state it. Default to Gemini 3.5 Flash; specify Gemini 3.1 Pro for heavy reasoning or Nano Banana for images. If the app does arithmetic, add "compute in code, not in the model."
  • Data and context. Say where the data comes from: named input fields for a Basic app, or a pasted CSV, policy set, or review corpus for an Advanced one. If you want catalog-wide reasoning, say "use the one-million-token window to hold the whole file."
  • Features. List behaviors, not adjectives. Specify copy buttons, counters, export formats, and the loading, empty, and error states. The agent builds what you enumerate; unstated states get skipped.
  • Validation. Tell the app how to check itself: a character limit, a row-count reconciliation, a schema check, a "cite the source passage" rule. If you cannot name a check, the task is underspecified.

Two habits separate a usable build from a demo. First, ground the app: tell it never to invent specs, policies, or numbers it was not given, and to flag gaps instead of filling them. Second, iterate in place: once the app renders, use annotation mode to highlight the exact element you want changed rather than re-describing the whole app in chat. The five blocks get you a strong first build; annotation mode gets you the last ten percent.

Source: Google AI for Developers Build-mode prompting and iteration guidance.

Basic12 apps · paste-ready

Basic: 12 Single-Prompt Apps

Twelve apps you build with one prompt and run free in the AI Studio preview against your own key. No server, no database, no deploy. Each produces correct, on-brand text or assets that you paste straight into Shopify. Default model: Gemini 3.5 Flash; image apps use Nano Banana 2.

01 Product Description Studio

Brand-voice descriptions with SEO, in four lengths.

Fixes: Unclear product information, the conversion killer named in Shopify CRO guidance.

Gemini 3.5 Flash
App: a Shopify product description generator that matches my brand voice and outputs four ready-to-paste lengths.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a client-side React app.
Data and context:
- Input fields: product name, 3 to 5 key features, target customer, price.
- A tone selector: casual, professional, luxury, playful.
- A "store voice" textarea where I paste two existing descriptions so output mirrors my voice.
Features:
1. One Generate button produces a 150 to 200 word storytelling description, 5 to 7 scannable bullet benefits, a 50-word short description for collection pages, and a 155-character meta description.
2. Each output block has its own copy button and a live word and character counter.
3. A Regenerate button per block so I can reroll one section.
4. A tighten and a lengthen control on the main description.
Validation:
- Enforce the meta description at 155 characters or fewer; red counter when over.
- Never invent specifications, materials, or claims absent from my inputs.
- If a required input is blank, prompt for it rather than guessing.
Deploy: AI Studio preview; run on my own free-tier key; paste outputs into Shopify by hand.
Acceptance: one product in, four on-brand, length-correct blocks out, ready to paste.
Worked example: input and output
Input
Product name: Organic Cotton Crew Tee Features: GOTS-certified organic cotton; mid-weight 180gsm; pre-shrunk; ribbed collar; side-seamed Target customer: design-conscious shoppers who care about sustainability Price: 38.00 Tone: casual Store voice samples: two existing DDS descriptions pasted in
Output
Storytelling (178 words): Some tees you wear once and forget. This is not one of them. The Organic Cotton Crew Tee is cut from GOTS-certified organic cotton in a mid-weight 180gsm knit, the weight that holds its shape instead of going sheer after a season. It is pre-shrunk, so the fit you buy is the fit you keep, and side-seamed so it hangs straight rather than twisting in the wash. The ribbed collar is built to survive being pulled over your head a thousand times without losing its snap. We made it to be the tee you reach for first and replace last, the quiet default in a drawer full of louder things. No slogans, no season, no compromise on the cotton. Bullets: - GOTS-certified organic cotton, grown without synthetic pesticides or fertilizers - Mid-weight 180gsm knit that drapes cleanly without clinging or going sheer - Pre-shrunk for a consistent fit that survives the wash - Side-seamed construction so it hangs straight instead of twisting - Ribbed collar engineered to keep its shape over years of wear - Cut for an everyday fit: not boxy, not tight Short (collection, 48 words): A pre-shrunk, mid-weight crew in GOTS-certified organic cotton. Side-seamed, ribbed collar, built to hold its shape. The quiet daily default you reach for first and replace last. Meta (151 chars): Organic Cotton Crew Tee in GOTS-certified cotton. Mid-weight 180gsm, pre-shrunk, side-seamed, ribbed collar. A sustainable daily default. Shop the Crew Tee.

02 SEO Meta and SERP Preview

Title tags, meta descriptions, and a live Google preview.

Fixes: Weak organic visibility against rising ad costs.

Gemini 3.5 Flash
App: a Shopify SEO metadata generator with a live Google SERP preview and a social card preview.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a client-side React app.
Data and context:
- Inputs: page type (product, collection, page), name, a short description, the target keyword.
Features:
1. Generate 5 title-tag variations at 50 to 60 characters and 3 meta-description variations at 150 to 160 characters.
2. Generate a URL handle, Open Graph title and description, and Twitter card text.
3. Render a Google SERP preview card and a social preview card that update live as I edit.
4. Show a checklist score: keyword in title, keyword in description, optimal length, compelling call to action, each with a tick or cross.
5. Copy buttons on every field; a Copy all button.
Validation:
- Real-time character counters with color warnings; block titles over 60 and descriptions over 160.
- Keep the keyword in the first 50 characters of at least three title variations.
Deploy: AI Studio preview; own key; paste the chosen fields into the Shopify SEO section.
Acceptance: title and meta options that pass the checklist, with a preview of how they read in Google.
Worked example: input and output
Input
Page type: product Name: Organic Cotton Crew Tee Short description: GOTS-certified organic cotton crew, mid-weight 180gsm, pre-shrunk Target keyword: organic cotton t-shirt
Output
Title-tag variations (chars): 1. Organic Cotton T-Shirt | GOTS-Certified Crew Tee (49) 2. Organic Cotton T-Shirt, Pre-Shrunk Crew Tee | DDS (52) 3. GOTS-Certified Organic Cotton T-Shirt for Everyday (52) 4. Mid-Weight Organic Cotton T-Shirt | Crew Tee (45) 5. Organic Cotton T-Shirt, Built to Last | DDS (44) Meta-description variations (chars): A (156): Shop our organic cotton t-shirt: a GOTS-certified, mid-weight crew tee, pre-shrunk with a ribbed collar. Sustainable, durable, and made to be your daily default. B (152): The organic cotton t-shirt that holds its shape. GOTS-certified, 180gsm, pre-shrunk, side-seamed. Sustainable everyday wear from Design Delight Studio. C (149): An organic cotton t-shirt built to last: GOTS-certified cotton, mid-weight knit, pre-shrunk fit. Shop the Crew Tee and skip the trend cycle. URL handle: organic-cotton-t-shirt-crew-tee Open Graph title: Organic Cotton Crew Tee | GOTS-Certified Open Graph description: A GOTS-certified, mid-weight organic cotton t-shirt, pre-shrunk and built to last. Twitter card: summary_large_image, same title and description. Checklist score: keyword in title (yes), keyword in description (yes), title 50-60 (yes), description 150-160 (yes), CTA present (yes). Score 5/5.

03 Product Title A/B Optimizer

Ten title angles with SEO scores and test pairs.

Fixes: Titles that neither rank nor convert in a narrow apparel funnel.

Gemini 3.5 Flash
App: a Shopify product title optimizer that generates angles, scores them, and proposes A/B pairs.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a client-side React app.
Data and context:
- Inputs: current title, main keyword, product type.
Features:
1. Generate 10 title variations across five angles: SEO-first, benefit, audience, feature, emotional.
2. For each, show a 70-character counter and an SEO score from keyword placement, length, and readability.
3. Highlight which words are the keyword in each title.
4. Suggest two A/B test pairs and explain what each pair tests.
5. Copy individual titles or all of them.
Validation:
- Flag any title over 70 characters; the main keyword appears in at least half the variations.
- Do not duplicate the input title in the output set.
Deploy: AI Studio preview; own key.
Acceptance: ten scored titles and a clear A/B pair to test first.
Worked example: input and output
Input
Current title: Crew Tee Main keyword: organic cotton t-shirt Product type: t-shirt
Output
Variations (angle, chars, SEO score): 1. Organic Cotton T-Shirt | Pre-Shrunk Crew Tee (SEO-first, 44, 92) 2. The Organic Cotton T-Shirt You Reach For First (emotional, 47, 84) 3. Organic Cotton Crew Tee for Everyday Wear (audience, 41, 88) 4. Mid-Weight Organic Cotton T-Shirt, Ribbed Collar (feature, 49, 86) 5. GOTS-Certified Organic Cotton T-Shirt (SEO-first, 38, 90) 6. The Last Organic Cotton T-Shirt You Need (emotional, 41, 83) 7. Organic Cotton T-Shirt Built to Last (benefit, 37, 89) 8. Everyday Organic Cotton Crew Tee for Men and Women (audience, 50, 85) 9. Side-Seamed Organic Cotton T-Shirt | 180gsm (feature, 45, 84) 10. Organic Cotton T-Shirt, Pre-Shrunk and Durable (benefit, 47, 88) Keyword highlight: "organic cotton t-shirt" appears in 8 of 10 variations. A/B pair 1: variation 1 vs variation 3 (keyword-forward vs audience-forward). A/B pair 2: variation 5 vs variation 7 (certification angle vs durability angle). Check: no variation exceeds 70 characters; input title not duplicated.

04 Alt-Text Generator

SEO image alt text read from the picture itself.

Fixes: Missing alt text that costs image SEO and accessibility.

Gemini 3.5 Flash
App: an image alt-text generator that reads the actual image and writes SEO and accessible alt text.
Model: Gemini 3.5 Flash, using its multimodal image understanding.
Build in Google AI Studio Build mode as a client-side React app.
Data and context:
- Let me upload an image or paste an image URL.
- Inputs: product name and target keyword.
Features:
1. Analyze the image and produce a descriptive alt text and an SEO alt text containing the keyword, each under 125 characters.
2. Detect decorative images and flag them as needing empty alt text.
3. A batch mode that accepts several image URLs and returns a table of filename and alt text.
4. Export the table as CSV (filename, alt text).
5. Inline image thumbnails so I can see what each line describes.
Validation:
- Enforce the 125-character recommendation with a counter.
- Describe only what is visibly in the image; never assert an unseen brand, color, or detail.
Deploy: AI Studio preview; own key; paste alt text into Shopify image fields or import the CSV.
Acceptance: every product image leaves with accurate, keyworded, length-correct alt text.
Worked example: input and output
Input
Image: a folded sage-green crew-neck t-shirt on a light wood surface, soft daylight Product name: Organic Cotton Crew Tee Target keyword: organic cotton t-shirt Batch URLs: 3 product images pasted
Output
Single image: Descriptive (74 chars): Folded sage-green crew-neck t-shirt resting on a light wood surface SEO (88 chars): Sage-green organic cotton t-shirt, folded crew tee on light wood, GOTS-certified Decorative? No Batch table (filename, alt text): crew-tee-sage-front.jpg | Sage-green organic cotton t-shirt, front view, folded on wood (61) crew-tee-sage-back.jpg | Back of sage organic cotton crew tee showing ribbed collar (62) crew-tee-detail.jpg | Close-up of organic cotton t-shirt knit and side seam (56) CSV export ready. All alt texts under 125 characters; descriptions reflect only what is visible in each image.

05 Collection Description Writer

Above-fold and long descriptions for collection pages.

Fixes: Thin collection pages that miss commercial-intent search.

Gemini 3.5 Flash
App: a Shopify collection description writer producing hero and extended copy plus meta.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a client-side React app.
Data and context:
- Inputs: collection name, the products it contains, target keyword.
- A style selector: minimal, story-driven, feature-focused, lifestyle.
Features:
1. Generate a 50 to 100 word hero description for above the product grid.
2. Generate a 200 to 300 word extended description for below the grid, with who it is for and how to choose.
3. Generate a meta title and meta description.
4. Place the keyword naturally; never stuff it.
5. Copy buttons and character counters per block; a collection-page preview.
Validation:
- Keep the meta title at 60 characters or fewer.
- Confirm the keyword appears in the hero description once or twice, not more.
Deploy: AI Studio preview; own key.
Acceptance: hero copy, extended copy, and meta that read naturally and target the keyword.
Worked example: input and output
Input
Collection name: Organic Basics Products: crew tees, long-sleeves, hoodies in GOTS-certified organic cotton Target keyword: organic cotton basics Style: minimal
Output
Hero (84 words): Organic cotton basics, built to last. This is the core of the wardrobe: crew tees, long-sleeves, and hoodies cut from GOTS-certified organic cotton and made for an everyday fit. No seasonal gimmicks, no thin fabric that gives out by spring, just the staples you wear on repeat. Each piece is pre-shrunk and side-seamed so it keeps its shape, and chosen to outlive the trend cycle rather than feed it. Start here and build out. Extended (236 words): Most "basics" are anything but. They go sheer, they twist in the wash, and they are replaced within a season. The Organic Basics collection is the opposite bet. Every piece is cut from GOTS-certified organic cotton, grown without synthetic pesticides, and knit at a mid-weight that holds its shape instead of surrendering it. They are pre-shrunk, so the fit you choose is the fit you keep, and side-seamed for a clean drape that does not rotate around your body over time. Who it is for: anyone rebuilding a wardrobe around fewer, better things, who would rather own three tees that last than ten that do not. How to choose: start with the crew tee in your everyday color, add a long-sleeve for shoulder-season layering, and finish with the hoodie for the days that need it. Sizing runs slightly fitted, so size up for a relaxed look. This is a foundation, not a fad. Buy the pieces you will actually wear, take care of them, and let them earn their place. That is the whole idea behind Organic Basics: sustainable staples that are quiet, durable, and certified at the fiber. Meta title (47): Organic Cotton Basics | Crew Tees and Hoodies Meta description (146): Shop organic cotton basics: crew tees, long-sleeves, and hoodies in GOTS-certified cotton. Minimal, durable, sustainable everyday staples that last.

06 Review Response Writer

On-brand replies for every star rating.

Fixes: Unanswered reviews that erode the trust signals buyers check.

Gemini 3.5 Flash
App: a customer-review response writer that handles every rating in my brand voice.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a client-side React app.
Data and context:
- Paste a customer review; select a star rating from 1 to 5.
- For negative reviews, select an issue type: shipping, quality, sizing, service, wrong item.
- A store-name input and a tone note.
Features:
1. Generate a response that thanks the customer, addresses their specific points, offers a solution if negative, and invites future engagement.
2. Provide two alternative variations per review.
3. An editable field so I can adjust before copying.
4. A small template library for the most common situations.
Validation:
- The response must reference at least one detail the reviewer actually mentioned.
- Never use defensive or argumentative language, even for a one-star review.
Deploy: AI Studio preview; own key; paste into the review platform.
Acceptance: paste any review, get a calm, specific, on-brand reply in one click.
Worked example: input and output
Input
Review: "Love the look but it runs a size small. Disappointed I had to exchange." Rating: 2 Issue: sizing Store name: Design Delight Studio
Output
Primary reply: Thank you for the honest feedback, and we are genuinely sorry the first size missed the mark. You are right that this style runs slightly fitted, and communicating that clearly is on us, not on you; we have flagged it to make the size guide more explicit so the next person sizes up from the start. We are glad the exchange got you into the right fit, and we would love to hear how it wears in over the next few weeks. Anything at all, reach us at customersupport@ddsboston.com and we will make it right. Variation A (shorter): We appreciate the honesty, and we are sorry about the sizing surprise. You are right that this runs fitted, and we are updating the size guide to say so plainly. Glad the exchange sorted it, and we are here if you need anything at customersupport@ddsboston.com. Variation B (warmer): This is exactly the kind of feedback that makes the next tee better, so thank you. The fitted cut caught you off guard, and that is a guide problem we are fixing. We are really glad you stuck with us through the exchange, and we hope the new size becomes a favorite. References the reviewer's specific points: runs small, and the exchange. No defensive language.

07 FAQ and JSON-LD Generator

Product FAQs plus valid FAQPage schema.

Fixes: Missing FAQ content that AI answer engines and shoppers both want.

Gemini 3.5 Flash
App: a product FAQ generator that also outputs valid FAQPage schema.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a client-side React app.
Data and context:
- Inputs: product name, description, key features, price.
Features:
1. Generate 10 to 15 FAQs covering specs, sizing, care, shipping, returns, comparisons, and durability.
2. Let me edit answers inline and reorder questions.
3. Export three ways: an HTML accordion to paste into Shopify; valid JSON-LD FAQPage schema; plain text.
4. Toggle individual FAQs on or off before export.
Validation:
- The exported JSON-LD must be valid JSON.
- The FAQPage Question count must equal the number of enabled FAQs on screen.
- Answers grounded in the inputs; do not promise policies I did not provide.
Deploy: AI Studio preview; own key; paste the accordion and the JSON-LD into the product page.
Acceptance: an editable FAQ set and matching schema that validates.
Worked example: input and output
Input
Product: Organic Cotton Crew Tee Features: GOTS-certified, mid-weight 180gsm, pre-shrunk, side-seamed Price: 38.00
Output
FAQs (8, editable): Q: Is the Crew Tee true to size? A: It runs slightly fitted. Size up for a relaxed fit, or stay true to size for a closer cut. Q: Is the cotton certified? A: Yes. It is GOTS-certified organic cotton, grown without synthetic pesticides. Q: Will it shrink in the wash? A: It is pre-shrunk, so expect minimal change. Wash cold and tumble low to keep it that way. Q: How heavy is the fabric? A: Mid-weight at 180gsm, structured enough to hold its shape without feeling stiff. Q: Is it see-through? A: No. The 180gsm knit is opaque in standard colors. Q: How should I care for it? A: Machine wash cold, tumble dry low, no bleach. Hang-drying extends its life further. Q: Is it unisex? A: The fit works across sizes; consult the size guide and size up for a looser look. Q: What makes it sustainable? A: GOTS-certified organic cotton plus a durable construction designed to be replaced less often. JSON-LD (excerpt, valid): { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ {"@type": "Question", "name": "Is the cotton certified?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. It is GOTS-certified organic cotton, grown without synthetic pesticides."}}, {"@type": "Question", "name": "Will it shrink in the wash?", "acceptedAnswer": {"@type": "Answer", "text": "It is pre-shrunk, so expect minimal change. Wash cold and tumble low."}} ] } Enabled FAQs on screen: 8; JSON-LD Question count: 8 (match).

08 Size Guide Builder

Size charts with measure-how instructions and export.

Fixes: Sizing uncertainty, a top apparel return and abandonment driver.

Gemini 3.5 Flash
App: a product size-guide builder with conversions and an HTML export.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a client-side React app.
Data and context:
- Select product type: t-shirts, pants, dresses, shoes, hats, accessories.
- Paste my own size data or use a standard template.
- A fit descriptor: relaxed, regular, slim.
Features:
1. Generate a size-chart table (XS to 3XL or numeric).
2. Generate how-to-measure instructions and a between-sizes recommendation.
3. Generate US, UK, and EU conversions.
4. Export as an HTML table to paste into Shopify; show a mobile-friendly preview.
Validation:
- Confirm every size row has a value for every measurement column.
- Flag missing cells rather than inventing measurements.
Deploy: AI Studio preview; own key.
Acceptance: a complete, responsive size table and instructions ready to paste.
Worked example: input and output
Input
Product type: t-shirts Size data: standard template Fit: regular
Output
Size chart (inches): Size | Chest | Length | Sleeve S | 36-38 | 28 | 8 M | 39-41 | 29 | 8.5 L | 42-44 | 30 | 9 XL | 45-47 | 31 | 9.5 2XL | 48-50 | 32 | 10 3XL | 51-53 | 33 | 10.5 How to measure: - Chest: measure around the fullest part, keeping the tape level under the arms. - Length: measure from the highest point of the shoulder straight down to the hem. - Sleeve: measure from the shoulder seam to the sleeve opening. Between sizes: size up for a relaxed fit, down for a fitted look. Conversions: Size | US | UK | EU S | S | 36 | 46 M | M | 39 | 48 L | L | 42 | 52 XL | XL | 45 | 56 Validation: every size row has chest, length, and sleeve values; no missing cells. HTML table export ready, mobile preview confirmed.

09 Product Tag Generator

Thirty-plus filterable tags by type.

Fixes: Poor filtering and weak on-site search from sparse tags.

Gemini 3.5 Flash
App: a Shopify product tag generator that proposes tags grouped by purpose.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a client-side React app.
Data and context:
- Inputs: product title, description, category.
Features:
1. Generate 30 or more tags grouped by type: category, attribute, style, occasion, audience, search-term.
2. Click tags to select or deselect, with a running count.
3. Copy selected tags comma-separated for Shopify.
4. Suggest a consistent naming convention.
Validation:
- Warn on any tag over 255 characters and block it from the copied set.
- Ensure each group has at least three tags.
Deploy: AI Studio preview; own key.
Acceptance: a curated, deduplicated tag set ready to paste into the product.
Worked example: input and output
Input
Title: Organic Cotton Crew Tee Description: GOTS-certified, mid-weight 180gsm, pre-shrunk, side-seamed Category: tops
Output
Tags (34, grouped): Category: tops, t-shirts, crew-neck, short-sleeve, tees Attribute: organic-cotton, GOTS-certified, mid-weight, 180gsm, pre-shrunk, side-seamed, opaque, breathable Style: minimal, everyday, basics, classic, versatile, capsule-wardrobe Occasion: everyday, casual, layering, work-from-home, weekend Audience: unisex, mens, womens, sustainable-shoppers, conscious-consumers Search-term: organic-cotton-tshirt, sustainable-tshirt, gots-certified-tee, eco-friendly-top, durable-tshirt, plastic-free-tee Naming convention: lowercase, hyphenated, no spaces. Copied set (selected): tops, t-shirts, crew-neck, organic-cotton, GOTS-certified, mid-weight, pre-shrunk, side-seamed, minimal, everyday, basics, unisex, sustainable-shoppers, organic-cotton-tshirt, sustainable-tshirt, gots-certified-tee Validation: every group has at least three tags; no tag exceeds 255 characters.

10 Email Subject Line Lab

Twenty subject lines with preview text and spam check.

Fixes: Low email open rates on an owned channel that beats paid CAC.

Gemini 3.5 Flash
App: an email subject-line generator with preview text and a spam check.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a client-side React app.
Data and context:
- Inputs: email purpose, main offer, urgency level.
Features:
1. Generate 20 subject lines across styles: curiosity, urgency, personalization, question, list, emoji, benefit, FOMO.
2. Suggest matching preview text for each.
3. Show a character counter (50 recommended, 70 max) and a mobile truncation indicator.
4. Run a spam-word check and flag risky lines.
5. Offer two A/B test pairs; copy subject and preview together.
Validation:
- Flag subject lines over 70 characters and any that trip the spam-word list.
- Personalization variants include a clear name token placeholder.
Deploy: AI Studio preview; own key; paste into Klaviyo or Shopify Email.
Acceptance: twenty vetted subject lines and a first A/B pair to test.
Worked example: input and output
Input
Purpose: launch a new organic basics line Offer: 15% off first order Urgency: medium
Output
Subject lines (style, chars, preview text): 1. New: Organic Basics, built to last (curiosity, 32) | The everyday staples, reimagined 2. Your 15% off starts now (offer, 24) | First-order welcome, inside 3. Meet the Organic Basics line (curiosity, 28) | Crew tees, hoodies, and more 4. The basics worth keeping are here (benefit, 33) | GOTS-certified, made to last 5. {NAME}, your wardrobe upgrade just dropped (personalization, 41) | Start with 15% off 6. Three staples. One certification. Zero compromise. (list, 49) | Inside the new line 7. Why we rebuilt the basics (question-ish, 26) | The cotton, the cut, the reason 8. 15% off ends Sunday (urgency, 19) | Organic Basics launch week Counters: lines 1-8 all under 70; lines 1-4 and 7-8 under 50 (preferred). Mobile truncation flagged on line 6. Spam check: clean across all eight. A/B pair: line 1 vs line 2 (curiosity vs offer). Personalization variant includes a {NAME} token.

11 Social Caption Multi-Platform

One message, every platform, correct lengths.

Fixes: Slow, inconsistent social output across channels.

Gemini 3.5 Flash
App: a multi-platform social caption generator that adapts one message per network.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a client-side React app.
Data and context:
- Inputs: product or topic, key message, call to action, a brand-voice note.
Features:
1. Generate captions for Instagram (storytelling, up to 30 hashtags), TikTok (short hook), Facebook (conversational), Pinterest (searchable keywords), X (under 280 characters), and LinkedIn (professional), shown in tabs.
2. Regenerate per platform and edit inline.
3. Per-platform character counters and hashtag suggestions.
4. Copy button per platform.
Validation:
- Enforce each platform's character limit, especially X at 280.
- Keep hashtag counts within platform norms; never exceed 30 on Instagram.
Deploy: AI Studio preview; own key.
Acceptance: one input yields ready captions for six platforms, each within its limits.
Worked example: input and output
Input
Topic: Organic Basics launch Key message: built to last, GOTS-certified cotton CTA: shop the line Brand voice: warm, plain, no hype
Output
Instagram (storytelling): The basics, done right. Our new Organic Basics line is cut from GOTS-certified cotton and built to outlast the trend cycle, the crew tees, long-sleeves, and hoodies you actually reach for. No seasonal gimmicks, just staples that keep their shape. Tap to shop the line. Hashtags (8 of up to 30): #organiccotton #sustainablefashion #basics #gotscertified #slowfashion #capsulewardrobe #consciousstyle #madetolast TikTok (hook): The reason your tees go sheer in a season, and what we did about it. Facebook (conversational): We rebuilt the basics. The new Organic Basics line is GOTS-certified cotton, pre-shrunk and side-seamed so it holds its shape wash after wash. Crew tees, long-sleeves, hoodies. Shop the line at the link. Pinterest (searchable): Organic cotton crew tees, long-sleeves, and hoodies. Sustainable everyday basics in GOTS-certified cotton, built to last. X (138 chars): New drop: Organic Basics in GOTS-certified cotton, built to last. Crew tees, long-sleeves, hoodies. Shop the line. LinkedIn (professional): We launched Organic Basics, a core line in GOTS-certified organic cotton designed for durability over disposability. A small step toward a wardrobe that lasts. Validation: X under 280; Instagram hashtags under 30; each platform within its norm.

12 Blog Outline to Draft

SEO post structure, then a full HTML draft.

Fixes: No content engine to build organic traffic over time.

Gemini 3.5 Flash
App: a Shopify blog post generator that drafts in two stages, outline then full draft.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a client-side React app.
Data and context:
- Inputs: topic, target keyword, word-count goal, post type (how-to, listicle, comparison, buyer's guide).
Features:
1. First generate an SEO title, meta description, and an H2 and H3 outline.
2. On my approval, expand each section into a full draft.
3. Suggest internal-link anchors and a closing call to action.
4. Show a live word count and a keyword-density readout.
5. Export as HTML for Shopify.
Validation:
- Keep within 10 percent of the word-count goal.
- Confirm the keyword appears in the title, the first paragraph, and at least one H2.
Deploy: AI Studio preview; own key; paste the HTML into a Shopify blog post.
Acceptance: approve an outline, leave with a structured, keyworded HTML draft.
Worked example: input and output
Input
Topic: how to tell if a t-shirt is actually sustainable Keyword: sustainable t-shirt Word goal: 1200 Type: how-to
Output
SEO title: How to Tell If a Sustainable T-Shirt Is the Real Thing Meta description (149): Learn how to spot a genuinely sustainable t-shirt: the certifications, materials, and construction signals worth checking before you buy. Outline: H2: What "sustainable" actually means on a clothing label H2: Certifications worth checking H3: GOTS (organic content and processing) H3: GRS and OCS (recycled and organic content) H3: Fair Trade (labor standards) H3: How to verify a certification is real H2: Material and construction signals H3: Fiber type and weight H3: Pre-shrinking and side seams H2: Red flags and greenwashing H3: Vague claims with no certification H3: "Eco" branding without proof H2: A simple checklist before you buy Draft (first section excerpt): The word "sustainable" has no legal definition in fashion, which is exactly why it is on so many labels. To tell a genuine sustainable t-shirt from a marketing one, you check three things in order: the certification, the material, and the construction... Internal-link anchors suggested: "GOTS certification", "organic cotton basics". Keyword present in title, first paragraph, and the H2 on materials. Word count tracking to ~1200.
Advanced12 apps · paste-ready

Advanced: 12 Full-Stack Apps

Twelve apps that use the full-stack runtime, npm packages, and the one-million-token window to work over whole catalogs, policy sets, and review corpora. They run free in the preview and can deploy privately to Cloud Run. Keys live in Secrets Management; outputs export as CSV or formatted files.

13 Catalog-Wide SEO Auditor

Paste your whole product CSV; get scored gaps.

Fixes: No way to see SEO gaps across a large catalog at once.

Gemini 3.5 Flash
App: a catalog-wide SEO auditor that scores every product in one pass.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a full-stack app (React client, Node server).
Data and context:
- A file upload or large textarea where I paste my full Shopify product export as CSV (title, description, tags, handle).
- Use the one-million-token context window so the model reasons over every row in one pass; the window holds roughly 1,500 pages of text, so a full catalog fits.
Features:
1. For each product, score title length and keyword use, description length and quality, missing tags, and handle health.
2. Output a sortable table with a 0 to 100 score per product and the top three fixes for each.
3. Use an npm CSV parser the agent installs automatically.
4. Summary cards: average score, count of products under 50, most common gap.
5. Export the full audit as CSV.
Validation:
- The row count in the audit must equal the row count in the uploaded CSV.
- Flag any row that failed to parse rather than skipping it silently.
Deploy: keep in the AI Studio preview for personal use; the CSV stays in your session and is not shared.
Acceptance: paste a catalog, leave with a scored, sortable, exportable audit of every product.
Worked example: input and output
Input
Pasted CSV (4 of 412 rows): title,description,tags,handle Crew Tee,Soft cotton tee.,,crew-tee Organic Cotton Hoodie,GOTS-certified organic cotton hoodie with kangaroo pocket and ribbed cuffs.,hoodie;organic-cotton,organic-cotton-hoodie Beanie,A beanie.,,beanie-1 Recycled Tote,Made from GRS-certified recycled cotton canvas. Roomy and durable.,tote;recycled,recycled-tote
Output
Audit table (4 of 412): title | score | top fixes Crew Tee | 41 | title too short, no keyword; description 3 words; no tags Organic Cotton Hoodie | 86 | add 1-2 long-tail tags; otherwise healthy Beanie | 28 | generic title and handle; 2-word description; no tags Recycled Tote | 79 | add a long-tail keyword to title; expand tags Summary cards: - Average score: 63 - Products under 50: 118 of 412 - Most common gap: missing tags (197 products) - Quick wins (score 40-60, one fix away): 96 products Reconcile: rows in = 412; rows audited = 412 (match). Parse failures: 0. CSV export ready, sorted ascending by score so the worst products come first.

14 Bulk Description Factory

CSV in, brand-locked descriptions CSV out.

Fixes: Rewriting hundreds of descriptions by hand is impossible solo.

Gemini 3.5 Flash
App: a bulk product-description factory that rewrites a whole catalog in my voice.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- Upload a CSV of products (name, features, price).
- Paste my brand guide and two sample descriptions into a context panel; hold them in the one-million-token window so every generated description matches my voice and rules.
Features:
1. For every row, generate a 150-word description, five bullets, and a 155-character meta description.
2. Process in batches with a visible progress bar and a pause and resume control.
3. Use an npm CSV library to read input and write output.
4. Export a CSV ready for Shopify product import.
Validation:
- Output row count equals input row count.
- Each meta description is 155 characters or fewer.
- No banned word from my brand guide appears in any output.
Deploy: preview for personal use; or private Cloud Run if a teammate runs it on their own key. Keys are never placed in client code.
Acceptance: upload a catalog CSV, download a brand-consistent descriptions CSV ready to import.
Worked example: input and output
Input
Uploaded CSV (2 of 60 rows): name,features,price Organic Cotton Hoodie,GOTS-certified; mid-weight; kangaroo pocket,78 Recycled Canvas Tote,GRS-certified recycled cotton; roomy; durable,42 Brand guide pasted; banned words: cheap, luxury
Output
Output CSV (2 of 60): name,description,bullets,meta Organic Cotton Hoodie,"Mid-weight and made to last, the Organic Cotton Hoodie is cut from GOTS-certified cotton with a roomy kangaroo pocket and ribbed cuffs that keep their shape. Warm without bulk, built for the days that need it.","GOTS-certified organic cotton | Mid-weight, holds its shape | Kangaroo pocket and ribbed cuffs | Built to last","Organic Cotton Hoodie in GOTS-certified cotton. Mid-weight, kangaroo pocket, built to last. Shop the hoodie. (108)" Recycled Canvas Tote,"Roomy and ready for everything, the Recycled Canvas Tote is made from GRS-certified recycled cotton canvas. Durable enough for a grocery run or a work bag, with a clean shape that goes anywhere.","GRS-certified recycled cotton canvas | Roomy main compartment | Durable everyday carry | Clean, minimal shape","Recycled Canvas Tote in GRS-certified cotton. Roomy, durable, minimal. Shop the tote. (88)" Reconcile: input 60 rows = output 60 rows (match). Each meta under 155 chars. Banned words found: 0. Import-ready CSV produced; batch ran in 6 chunks of 10 with a progress bar.

15 Review-Mining Dashboard

Hundreds of reviews into themes, sentiment, charts.

Fixes: Customer feedback sits unread instead of guiding the store.

Gemini 3.5 Flash
App: a review-mining dashboard that analyzes a full review set at once.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- Paste hundreds of customer reviews as bulk text; use the one-million-token window to analyze them all together.
Features:
1. Extract an overall sentiment score, the most-mentioned positives and negatives, recurring themes, feature requests, and competitor mentions.
2. Render charts with the recharts npm package: a sentiment breakdown and a theme-frequency bar chart.
3. Pull quotable testimonials for marketing.
4. List specific product-description and FAQ improvements suggested by the reviews.
5. Export a summary report.
Validation:
- The sum of categorized reviews must equal the number pasted.
- Every extracted testimonial must be a verbatim quote present in the input.
Deploy: preview for personal use.
Acceptance: paste a review set, leave with charts, themes, testimonials, and a concrete improvement list.
Worked example: input and output
Input
Pasted reviews (5 of 240): Great fit, soft cotton. (5) Runs small, had to exchange. (2) Love it but shipping was slow. (4) Holds up after a year of washing. (5) Wish it came in more colors. (4)
Output
Overall sentiment: 71% positive, 17% neutral, 12% negative (240 reviews). Most-mentioned positives: - Fit and feel (98 mentions) - Softness of the cotton (74) - Durability over time (61) Most-mentioned negatives: - Runs small / sizing (39) - Slow shipping (22) - Limited color range (18) Recurring themes: quality holds up after repeated washing; sizing guidance needs to be clearer. Feature requests: more colors (18), tall sizes (7). Competitor mentions: 3 (all favorable to us on fabric). Quotable testimonials (verbatim): - Great fit, soft cotton. - Holds up after a year of washing. Suggested fixes: add an explicit sizing note to product pages and the size guide; review the shipping SLA; survey demand for additional colors. Charts: sentiment breakdown (pie) and theme frequency (bar) rendered with recharts. Reconcile: reviews in = 240; categorized = 240 (match).

16 Policy-Aware Support Composer

Replies grounded in all your real policies.

Fixes: Support answers that contradict policy and create disputes.

Gemini 3.5 Flash
App: a policy-aware customer-support reply composer.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- Paste my full shipping, return, refund, and warranty policies into a context panel held in the one-million-token window.
- Then paste a customer message.
Features:
1. Generate a reply that answers using only my actual policies, links to the relevant policy section, and offers clear next steps, in a chosen tone.
2. Show which policy passage each part of the answer is based on.
3. Offer two variations and an SMS-length version.
4. A template tray for the most common questions.
Validation:
- Every claim in the reply must trace to a sentence in the pasted policies.
- If the policies do not cover the question, say so and suggest escalation rather than inventing a policy.
Deploy: preview, or private Cloud Run for a support teammate. Keys stay server-side.
Acceptance: paste a message, get an on-policy reply with each claim traceable to my policy text.
Worked example: input and output
Input
Pasted return policy (excerpt): Unworn items may be returned within 30 days for a full refund. Customer pays return shipping. Final-sale items are not returnable. Customer message: Can I return a tee I bought 3 weeks ago? It is unworn and not on sale.
Output
Primary reply: Yes. Since the tee is unworn, not a final-sale item, and it has been about three weeks, it falls inside our 30-day return window, so you are eligible for a full refund. Please note that return shipping is covered by the customer. Reply here and we will send you the return steps and address. Shorter variation: Good news, you are inside the 30-day window and the tee qualifies, so a full refund is available. Return shipping is on the customer. Want me to send the steps? SMS-length version: You are inside the 30-day return window and the tee qualifies for a full refund. Return shipping is customer-paid. Reply YES for the steps. Traceability: - "30-day window" and "full refund" -> policy sentence 1 - "customer pays return shipping" -> policy sentence 2 - "not a final-sale item" qualifier -> policy sentence 3 If the item had been final sale, the app would have declined the return and cited sentence 3 instead of inventing an exception.

17 Content Calendar Generator

A month of posts, exportable to CSV and iCal.

Fixes: Ad-hoc posting with no plan or cadence.

Gemini 3.5 Flash
App: a social content-calendar generator with CSV and iCal export.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- Inputs: month, posting frequency, and a list of upcoming launches, sales, and events.
Features:
1. Generate a full calendar with date, content type, topic, platform focus, best posting time, and the content pillar each post serves.
2. Balance content types automatically and include relevant holidays.
3. Render an interactive month grid; click a day for full details.
4. Use an npm date library the agent installs.
5. Export as CSV and as an iCal file.
Validation:
- The number of posts matches the chosen frequency across the month.
- No two adjacent days repeat the same content type.
Deploy: preview for personal use.
Acceptance: a balanced month of dated, typed posts I can export to my calendar.
Worked example: input and output
Input
Month: June; frequency: 4 posts/week; events: Organic Basics launch June 12, summer sale June 21-23
Output
Calendar (week of June 8-14 shown; full month generated): date | type | topic | platform | time | pillar Jun 9 | educational | What GOTS certification actually means | Instagram | 11am | education Jun 10 | product | Crew Tee in three colors | Pinterest | 2pm | product Jun 12 | launch | Organic Basics is live | all | 9am | launch Jun 14 | UGC | Repost a customer photo | Instagram | 6pm | community Week of June 15-21 (excerpt): Jun 16 | educational | How to care for organic cotton | Facebook | 12pm | education Jun 18 | product | Hoodie feature: kangaroo pocket | Instagram | 5pm | product Jun 20 | promo | Summer sale starts tomorrow | all | 9am | promotion Jun 21 | promo | Summer sale is on | Instagram | 10am | promotion Holidays included where relevant. Reconcile: 4 posts/week across all of June; no two adjacent days repeat the same content type. Exports: CSV and an iCal file (.ics) for calendar import.

18 Keyword Cluster Mapper

Seed terms into clusters mapped to page types.

Fixes: Keyword effort scattered with no topic structure.

Gemini 3.1 Pro
App: a keyword cluster mapper that turns seeds into structured clusters.
Model: Gemini 3.1 Pro for the heavier reasoning.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- Inputs: a seed keyword, product type, target audience.
- Optionally enable the Google Search tool for current trends.
Features:
1. Generate primary, long-tail, question, and commercial-intent keywords, grouped into topic clusters.
2. For each keyword show estimated difficulty, intent type, and the suggested page type (product, collection, or blog).
3. Render clusters as expandable groups.
4. Export as CSV.
Validation:
- Every keyword is assigned to exactly one cluster and one page type.
- Flag duplicates across clusters.
Deploy: preview for personal use.
Acceptance: a clustered keyword map with page-type assignments, exportable to CSV.
Worked example: input and output
Input
Seed: organic cotton t-shirt; product type: tops; audience: sustainable shoppers; Google Search tool: on
Output
Cluster 1 - Product / commercial intent (page type: product): organic cotton t-shirt (medium difficulty, transactional) GOTS-certified t-shirt (low, transactional) sustainable crew tee (low, transactional) Cluster 2 - Comparison / commercial (page type: collection): best organic cotton t-shirts (medium, commercial) organic vs recycled cotton tee (low, commercial) Cluster 3 - Informational / questions (page type: blog): is organic cotton better for the environment (low, informational) how to wash organic cotton (low, informational) what does GOTS certified mean (low, informational) Cluster 4 - Care and longevity (page type: blog): how to keep a t-shirt from shrinking (low, informational) how long should a t-shirt last (low, informational) Validation: every keyword assigned to exactly one cluster and one page type; no duplicates across clusters. CSV export ready.

19 Competitor Teardown

Live competitor pages into a comparison matrix.

Fixes: No structured read on how rivals position and price.

Gemini 3.5 Flash
App: a competitor teardown tool that reads live pages and builds a matrix.
Model: Gemini 3.5 Flash with the URL Context tool enabled.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- Inputs: up to three competitor URLs plus my own store URL.
- Use URL Context to read the live pages.
Features:
1. For each competitor, summarize product range and pricing, value proposition, target audience, messaging, strengths, and weaknesses.
2. Render a side-by-side comparison matrix and a gap analysis of what none of them offer.
3. List concrete differentiation opportunities for my store.
4. Export a report.
Validation:
- Every claim cites which URL it came from.
- Mark anything the pages did not reveal as not stated rather than guessing.
Deploy: preview for personal use.
Acceptance: a sourced comparison matrix and a gap list I can act on.
Worked example: input and output
Input
Competitor URLs: example-rival.com/collections/tees, basic-co.com/products/everyday-tee My URL: ddsboston.com/collections/organic-basics URL Context tool: on
Output
Comparison matrix (from the live pages): dimension | example-rival | basic-co | DDS (mine) range | 6 tee colors | 1 tee, 4 colors | crew/LS/hoodie, fewer colors price band | 25-30 | 22 | 38-78 value prop | soft everyday tees | cheapest everyday | certified, built to last certification | not stated | not stated | GOTS-certified, per product weakness | no cert claims | thin spec detail | higher price, narrower range Gap analysis (none of them offer): published per-product certification detail and durability spec. Differentiation opportunities for my store: 1. Lead every product page with the verifiable GOTS certification. 2. Make durability concrete (gsm, pre-shrunk, side-seamed) where rivals stay vague. 3. Justify the price with a cost-per-wear framing. Citations: ranges and prices -> respective competitor URLs; "certification not stated" -> not present on competitor pages (marked as not stated, not assumed).

20 Pricing Strategy Calculator

Margins, break-even, and strategy side by side.

Fixes: Pricing set by feel, not by margin and break-even math.

Gemini 3.5 Flash
App: a pricing-strategy calculator that computes exact numbers and explains them.
Model: Gemini 3.5 Flash for the written guidance; compute math in code, not in the model.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- Inputs: product cost, two or three competitor prices, a target profit margin.
Features:
1. Compute cost-plus, competitive, value-based, and psychological pricing.
2. For each strategy show the resulting price, margin percent, and break-even units, computed in JavaScript so the numbers are exact.
3. A discount-impact calculator: if I discount X percent, how many more units to hold profit.
4. Render a bar chart comparing strategies with recharts.
5. Export the analysis.
Validation:
- All financial figures are computed in code and must reconcile.
- The model writes only the explanation, never the numbers.
Deploy: preview for personal use.
Acceptance: exact prices and margins per strategy, with a clear recommendation and a discount calculator.
Worked example: input and output
Input
Product cost: 8.00; competitor prices: 24, 29; target margin: 60%
Output
Computed in code (exact): strategy | price | margin | break-even units (fixed cost = 0) Cost-plus (60%) | 20.00 | 60.0% | 1 Competitive (low) | 24.00 | 66.7% | 1 Value-based (mid) | 27.00 | 70.4% | 1 Psychological | 26.99 | 70.4% | 1 Margin math: margin = (price - cost) / price. At 27.00, (27.00 - 8.00) / 27.00 = 70.4%. Discount-impact calculator (baseline 26.99): - 15% off -> 22.94 (margin 65.1%). Gross profit per unit falls from 18.99 to 14.94, so you need about 27% more units to hold total gross profit. - 20% off -> 21.59 (margin 62.9%). Profit per unit 13.59, needing about 40% more units. Recommendation: anchor at 26.99 (value-based, psychological), reserve discounts for launch and sale windows, and watch the unit math before discounting deeper than 15%. Note: every number above was computed in JavaScript; the model wrote only the labels and the recommendation.

21 Ad Copy Factory

Character-validated Facebook and Google ads.

Fixes: Slow ad iteration and copy that breaks platform limits.

Gemini 3.5 Flash
App: an ad-copy factory for Facebook and Google with strict, code-enforced limits.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- Inputs: product, main benefit, target audience, offer, and platform (Facebook or Google Ads).
Features:
1. For Facebook, generate primary text in three lengths, five headlines, and three descriptions.
2. For Google Responsive Search Ads, generate 15 headlines at 30 characters each and 4 descriptions at 90 characters each, with counters computed in code.
3. Show a SERP or ad preview.
4. Export an ad-set bundle as CSV.
Validation:
- Enforce every platform character limit in code and block any line that exceeds it.
- Run a prohibited-words check.
Deploy: preview for personal use.
Acceptance: platform-valid ad sets that never exceed a character limit, exportable to CSV.
Worked example: input and output
Input
Product: Organic Cotton Crew Tee; benefit: GOTS-certified, built to last; audience: sustainable shoppers; platform: Google RSA
Output
Google Responsive Search Ad: Headlines (15, each <=30 chars): 1. Organic Cotton Crew Tee (23) 2. GOTS-Certified, Built to Last (28) 3. Sustainable Everyday Tee (24) 4. Organic Cotton T-Shirt (22) 5. Pre-Shrunk, Holds Its Shape (27) 6. The Last Tee You Need (21) 7. Mid-Weight Organic Cotton (25) 8. Skip the Trend Cycle (20) 9. Shop Organic Basics (19) 10. Certified Organic Cotton (24) 11. Made to Last, Not a Season (26) 12. Soft, Durable, Certified (24) 13. Everyday Sustainable Style (26) 14. 180gsm Organic Cotton Tee (25) 15. Built for Daily Wear (20) Descriptions (4, each <=90 chars): 1. GOTS-certified organic cotton crew tee. Mid-weight, pre-shrunk, built to last. Shop now. (88) 2. The everyday tee that holds its shape. Certified organic cotton, side-seamed. Order today. (89) 3. Sustainable basics without the compromise. Organic cotton, durable construction. Shop. (86) 4. Fewer, better tees. GOTS-certified cotton made to outlast the trend cycle. Buy now. (84) Validation: all headlines <=30 and descriptions <=90, enforced in code; prohibited-words check passed. Ad-set bundle exported as CSV.

22 Internal Link Planner

Your content plus page list into a link map.

Fixes: Orphan pages and missed internal-linking SEO value.

Gemini 3.5 Flash
App: an internal-link planner that maps links across my own pages.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- Paste the page or blog content I am working on.
- Paste a list of my other pages as title and URL pairs; hold the full list in context.
Features:
1. Suggest which pages to link to, the optimal anchor text for each, where in the content to place the link, and why it is relevant.
2. Prioritize suggestions by SEO value.
3. Identify orphan pages with no inbound links.
4. Export the complete linking plan as a table.
Validation:
- Every suggested link targets a URL from my pasted list; never invent a URL.
- Anchor text must appear plausibly in the content.
Deploy: preview for personal use.
Acceptance: a prioritized link plan that only references my real pages, plus an orphan list.
Worked example: input and output
Input
Working content: a blog post on choosing sustainable basics Page list: /collections/organic-basics, Organic Basics /pages/about-certifications, Our Certifications /blogs/news/care-guide, Organic Cotton Care Guide /products/organic-cotton-crew-tee, Organic Cotton Crew Tee
Output
Link suggestions (prioritized by SEO value): 1. -> /collections/organic-basics | anchor: "organic cotton basics" | place: intro paragraph | high | the post's core commercial target 2. -> /pages/about-certifications | anchor: "GOTS certification" | place: certifications section | high | supports the central claim 3. -> /products/organic-cotton-crew-tee | anchor: "the Crew Tee" | place: example paragraph | medium | a concrete product example 4. -> /blogs/news/care-guide | anchor: "how to care for organic cotton" | place: longevity section | medium | keeps readers on related content Orphan check: none of the four pages are orphaned within this set after these links are added. Validation: every target URL is from the pasted list; no URL invented; each anchor appears plausibly in the content. Linking plan exported as a table.

23 Brand Voice Linter

Check any draft against your brand guide.

Fixes: Off-brand copy slipping out across many drafts.

Gemini 3.5 Flash
App: a brand-voice linter that checks any draft against my guide.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- Paste my brand guide once into a context panel held in the one-million-token window.
- Then paste any draft (product copy, email, post).
Features:
1. Check the draft against my guide for tone, banned words, sentence-length norms, and required phrases.
2. Output a pass or fail per rule with the exact offending text and a suggested rewrite.
3. Score the draft overall.
4. Keep the guide loaded so I can lint many drafts in a session.
Validation:
- Every flagged issue quotes the offending text from the draft.
- Never flag a rule the guide does not contain.
Deploy: preview, or private Cloud Run for a content teammate.
Acceptance: a per-rule pass or fail with quoted offenders and rewrites, reusable across drafts.
Worked example: input and output
Input
Brand guide pasted. Rules: banned words include "cheap" and "steal"; tone is warm and plain, no hype; required: mention a certification where relevant; sentences under 30 words. Draft: These cheap tees are an absolute steal you won't believe, grab yours before they're gone forever!!!
Output
Lint results: RULE: banned word -> FAIL. Offender: "cheap". Rewrite: "affordable". RULE: banned word -> FAIL. Offender: "steal". Rewrite: "value". RULE: tone (no hype) -> FAIL. Offender: "an absolute steal you won't believe" and "!!!". Rewrite: "a genuinely good everyday pick". RULE: certification mention -> FAIL. No certification referenced. Suggestion: note the GOTS-certified cotton. RULE: sentence length under 30 words -> PASS. Overall score: 1 of 5 rules passed. Suggested rewrite: "These affordable tees are a genuinely good everyday pick in GOTS-certified organic cotton. Worth a look while sizes last." Every flag quotes the offending text from the draft; no rule was flagged that the guide does not contain. The brand guide stays loaded, so the next draft can be linted without re-pasting it.

24 Customer Persona Builder

Three to four evidence-shaped buyer profiles.

Fixes: Marketing aimed at a vague, assumed customer.

Gemini 3.1 Pro
App: a customer-persona builder grounded in evidence when available.
Model: Gemini 3.1 Pro for richer reasoning.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- Inputs: my products, price range, and what I already know about current customers.
- Optionally paste real review text to ground the personas in evidence.
Features:
1. Generate three to four distinct personas with demographics, values, pain points, goals, shopping behavior, objections, and the messaging that converts each.
2. Add marketing do's and don'ts per persona.
3. Render persona cards and a side-by-side compare view.
4. Export as a document.
Validation:
- If review text is provided, each persona trait must be supported by a pattern in that text.
- Label any trait that is an inference rather than evidence.
Deploy: preview for personal use.
Acceptance: three to four usable personas with conversion messaging, grounded where evidence exists.
Worked example: input and output
Input
Products: organic cotton basics; price band: 38-78 What I know: repeat buyers skew urban and value sustainability Review snippet pasted: I only buy from brands that actually show their certifications.
Output
Persona: The Verifying Minimalist (1 of 3 generated) Demographics: 28-42, urban, mid-to-high income (inference) Values: proof over marketing; supports brands with verifiable sustainability (evidence: review snippet and stated repeat-buyer pattern) Pain points: greenwashing fatigue; uncertainty about whether a claim is real (evidence: review snippet) Goals: build a small, durable wardrobe from brands they can trust Shopping behavior: researches before buying; reads certification and care detail; buys fewer, higher-quality pieces (inference, partly supported by price band) Objections: "Is the certification actually real?" and "Is the price justified?" (evidence: review snippet) Messaging that converts: lead with per-product certification detail; make durability concrete; use plain language, not hype Do: show the GOTS certificate detail; quantify durability. Don't: use superlatives or vague "eco" claims. Labeling: certification focus and greenwashing fatigue are evidence-based; age, income, and detailed shopping behavior are inferences. Two further personas generated (The Practical Gifter, The Capsule Builder); card and compare views rendered; export ready.
Master12 apps · paste-ready

Master: 12 Stateful, Deployed Apps

Twelve apps that provision Firebase for persistent storage and Google sign-in, support multiplayer where useful, and deploy to Cloud Run as real tools. Remember the cost model: a deployed app bills every user's Gemini calls to your key, so keep keys server-side and monitor usage.

25 Content Ops Hub

Team drafting with saved history and sign-in.

Fixes: No shared, persistent place for a team to draft on-brand content.

Gemini 3.5 Flash
App: a content operations hub for my team with saved history and sign-in.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- My brand guide stored once and reused for every draft.
Features:
1. Generate product copy, emails, and social posts from one workspace.
2. Save every draft, the content calendar, and version history to Firestore.
3. Sign team members in with Firebase Authentication using Sign in with Google.
4. Support multiplayer so two people can work without overwriting each other.
5. A searchable archive of past drafts by type and date.
Deploy: provision Firebase (Firestore and Auth) through the agent and deploy to Cloud Run.
Cost note: the deployed app uses your Gemini key for all users, so keep the key server-side and monitor usage.
Validation:
- Saved drafts persist across sessions; sign-in gates access.
- Two simultaneous editors do not overwrite each other.
Acceptance: a signed-in team workspace that drafts on brand and never loses work.
Worked example: input and output
Input
Request: Draft a welcome email for new subscribers, warm tone. (Brand guide already stored in the workspace; two team members signed in.)
Output
Draft (saved): Subject: Welcome to the studio Body: Welcome to Design Delight Studio. You just signed up for first access to new drops and, more to the point, the reasoning behind every piece we make. We build a small range of certified, durable basics rather than a flood of seasonal product, because a wardrobe that lasts is the whole idea. Here is 15% off your first order to start. Tell us what you are looking for and we will point you to the right staple. Persistence: draft id ops_0481 written to Firestore; version 1 of 1; timestamped. Access control: visible only to signed-in team members via Firebase Authentication (Sign in with Google). Multiplayer: a teammate editing the June content calendar at the same time does not overwrite this draft; both changes persist. Archive: searchable by type (email) and date; the draft now appears in the team library.

26 Customer Gamification Engine

Storefront spin-or-quiz with a real leaderboard.

Fixes: Weak email capture and low repeat-visit engagement.

Gemini 3.5 Flash
App: a customer gamification engine for my storefront with a persistent leaderboard.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- A spin-to-win or quiz game that issues discount codes, with weighted odds defined in code.
Features:
1. Collect an email before play; award weighted prizes.
2. Store scores and a leaderboard in Firestore.
3. Enforce session and daily play limits.
4. Provide a shareable result card and a Shop Now call to action.
Deploy: provision Firestore and deploy to Cloud Run, then embed on the storefront by link or iframe.
Cost warning, foregrounded: every shopper's Gemini calls and Cloud Run usage bill to your key. Keep keys server-side, cap calls per session, and watch spend before exposing this to traffic.
Validation:
- Prize odds match the configured weights over many plays.
- The leaderboard persists; the email gate blocks play until completed.
Acceptance: a working storefront game with a real leaderboard and a controlled, understood cost.
Worked example: input and output
Input
Spin config (odds defined in code): 60% no win, 25% 10% off, 12% 15% off, 3% free shipping Player email collected: shopper@example.com
Output
Play result: shopper@example.com won "10% off" (code SPIN10-7QF2, single use). Result card: shareable image with the prize and a Shop Now button. Persistence: play recorded in Firestore; leaderboard updated; daily play limit of 1 enforced per email. Odds verification: across 10,000 simulated plays, observed outcomes (59.8% / 25.1% / 12.0% / 3.1%) matched the configured weights within tolerance. Cost controls, foregrounded: each play is a Gemini call billed to your key; calls per session are capped at 1, and a daily spend cap is set before this is exposed to live storefront traffic. Email gate: play is blocked until a valid email is entered.

27 Brand Brain

Your whole brand, catalog, and policies on call.

Fixes: Re-pasting brand context into every tool, every time.

Gemini 3.1 Pro
App: a brand brain that holds my whole brand and drafts on demand.
Model: Gemini 3.1 Pro for reasoning depth.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- Persist my full brand guide, product catalog, and all policies in Firestore.
- Load them into the one-million-token window at run time so every output reflects the whole brand.
Features:
1. A single prompt box where I ask for any asset, a product description, an email, a policy-accurate answer, and get output grounded in the stored brand.
2. Save outputs to a library.
3. Let me update the stored brand documents through the app.
4. Sign in with Firebase Auth.
Deploy: provision Firestore and Auth and deploy to Cloud Run; keys server-side; monitor cost.
Validation:
- Outputs must not contradict the stored brand documents.
- A policy answer must trace to a stored policy; never assert an uncertified claim about the brand.
Acceptance: one box that produces on-brand, policy-accurate assets without re-pasting context.
Worked example: input and output
Input
Ask: Write a policy-accurate answer: can a customer return a worn item? (Brand guide, full catalog, and all policies stored in Firestore and loaded into context.)
Output
Answer: Returns require items to be unworn and within 30 days of delivery, so a worn item is not eligible for a standard return or refund. There are two exceptions worth checking: if the item arrived damaged or developed a fault, that is covered under our warranty rather than the return policy; and final-sale items are not returnable in any case. If you tell me which applies, I can point you to the right next step. Traceability: - "unworn, within 30 days" -> stored return policy, sentence 1 - "damaged or faulty -> warranty" -> stored warranty policy - "final-sale items not returnable" -> stored return policy, final-sale clause Persistence: answer saved to the output library in Firestore; the stored policies can be updated through the app, after which future answers reflect the change. Guardrail: no uncertified claim about the brand was made; every statement traces to a stored document.

28 Inventory Planning Board

Reorder signals and notes that persist.

Fixes: Stockouts and overstock from no reorder signal or forecast.

Gemini 3.5 Flash
App: an inventory planning board with persistent data and reorder math.
Model: Gemini 3.5 Flash for the written guidance; compute reorder math in code.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- I enter or upload current stock, sell-through, and lead times per product and location; store it in Firestore.
Features:
1. Flag low-stock and overstock items.
2. Compute a suggested reorder quantity and date in code.
3. Keep multi-location notes.
4. Sign in with Firebase Auth so only my team sees it.
5. A dashboard with status badges.
Deploy: provision Firestore and Auth, deploy to Cloud Run, keys server-side; monitor cost.
Validation:
- Reorder quantities are computed in code and must reconcile to the inputs.
- The model writes only commentary, never the numbers; data persists across sessions.
Acceptance: a persistent board that flags reorders with exact, reconcilable quantities.
Worked example: input and output
Input
Product: Organic Cotton Hoodie; current stock: 12; sell-through: 3 per week; lead time: 4 weeks; safety stock: 6
Output
Computed in code (exact): - Weeks of cover: 12 / 3 = 4.0 weeks - Demand over lead time: 3 x 4 = 12 units - Reorder point: demand over lead time + safety stock = 12 + 6 = 18 units - Status: 12 < 18, so BELOW reorder point -> reorder now - Suggested reorder quantity (target 8 weeks of cover): 8 x 3 = 24 units, less 12 on hand = order 24 Dashboard: status badge reads "Reorder now" in amber; a second product at 40 units reads "Healthy" in green; an overstock item at 120 units reads "Overstock" in grey. Multi-location note: flagged that the Boston location holds all 12 units; warehouse is at 0. Persistence: stock, sell-through, and lead times stored in Firestore and reload across sessions; access gated by Firebase Auth. Guardrail: every number computed in code; the model wrote only the status commentary.

29 Review-to-Roadmap Tracker

Reviews over time become product priorities.

Fixes: Recurring complaints never turn into a prioritized plan.

Gemini 3.5 Flash
App: a review-to-roadmap tracker that turns recurring feedback into priorities.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- Paste new reviews on a recurring basis; store each batch in Firestore with its date.
Features:
1. Track theme and sentiment trends over time.
2. Surface rising complaints and feature requests.
3. Turn them into a prioritized improvement roadmap with a trend chart.
4. Sign in with Firebase Auth.
Deploy: provision Firestore and Auth and deploy to Cloud Run; keys server-side; monitor cost.
Validation:
- Every roadmap item links back to stored reviews that support it.
- Trend counts reconcile to the stored batches.
Acceptance: a living roadmap, evidenced by reviews, that updates as feedback accrues.
Worked example: input and output
Input
Batch A (May, stored): 5 mentions of "runs small", 2 of "more colors" Batch B (June, stored): 11 mentions of "runs small", 4 of "more colors", 3 of "tall sizes"
Output
Trends over time: - "runs small": 5 (May) -> 11 (June), rising - "more colors": 2 -> 4, rising - "tall sizes": new in June (3) Prioritized roadmap: 1. Add an explicit fit note to product pages and the size guide. Evidence: 16 "runs small" mentions across batches A and B. Effort: low. Impact: high (reduces returns). 2. Scope additional colorways for the core tees. Evidence: 6 "more colors" mentions. Effort: medium. 3. Evaluate a tall size run. Evidence: 3 mentions, June only. Effort: high. Status: watch. Trend chart rendered over the stored batches. Persistence and access: batches stored in Firestore with dates; signed-in via Firebase Auth. Guardrail: every roadmap item links to the stored reviews that support it; trend counts reconcile to the stored batches exactly.

30 UGC and Testimonial Library

Capture, tag, and reuse customer proof.

Fixes: Scattered testimonials that never get reused as proof.

Gemini 3.5 Flash
App: a UGC and testimonial library with tagging and safe reuse.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- I paste or upload customer testimonials and UGC references; store them in Firestore with tags.
Features:
1. Auto-tag each item by theme and sentiment.
2. Let me search and filter the library.
3. Generate ready-to-post captions from any item, with privacy-safe redaction of personal details.
4. Export selected items.
5. Gate access with Firebase Auth.
Deploy: provision Firestore and Auth, deploy to Cloud Run, keys server-side.
Validation:
- Generated captions quote the testimonial accurately.
- Redaction removes names and contact details when requested; the library persists.
Acceptance: a searchable proof library that turns any testimonial into a safe, on-brand post.
Worked example: input and output
Input
Pasted testimonial: Best hoodie I own. Soft, warm, and it held up after a year. - Jess M., Boston (Stored to the library.)
Output
Auto-tags: theme=durability, theme=comfort, theme=warmth, sentiment=positive, product=hoodie Generated caption (quotes accurately): "A year in and still going strong." Real words from a real customer. Shop the hoodie that earns its place. Privacy-safe redaction (on request): "- Jess M., Boston" becomes "- a verified customer". Search and filter: the item is findable by tag (durability) and by product (hoodie). Export: selected items exported as a formatted block for a landing page. Persistence and access: stored in Firestore; library gated by Firebase Auth; the caption only ever quotes text present in the stored testimonial.

31 Launch Command Center

Multi-channel launches, saved and reusable.

Fixes: Chaotic launches with no repeatable plan.

Gemini 3.5 Flash
App: a product-launch command center with saved, reusable plans.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- Inputs: product, launch date, and features; store each launch plan in Firestore.
Features:
1. Generate a full sequence, teasers, launch emails, social posts, ad copy, on a timeline.
2. A task checklist and a countdown.
3. Save and reload past launches.
4. Sign in with Firebase Auth for the team.
Deploy: provision Firestore and Auth and deploy to Cloud Run; keys server-side; monitor cost.
Validation:
- Timeline dates are internally consistent relative to the launch date.
- Saved launches reload intact.
Acceptance: a reusable launch plan with copy, tasks, and a countdown the team can run.
Worked example: input and output
Input
Product: Organic Basics line; launch date: June 12; key features: GOTS-certified, three core pieces
Output
Timeline (internally consistent against June 12): - Jun 5: teaser email + social tease ("something durable is coming") - Jun 9: behind-the-scenes post on the certification - Jun 10: two-days-to-go countdown post - Jun 11: final reminder email to the list - Jun 12, 9am: launch email + launch posts across platforms + ads live - Jun 15: follow-up email to non-openers Generated assets: 2 emails, 5 social posts, 3 ad variations, all on the timeline. Checklist: assets approved, discount code created, inventory confirmed, support macros ready. Countdown widget: live to June 12. Persistence: the full plan saved to Firestore; signed-in via Firebase Auth; reloads intact for reuse on the next launch. Guardrail: every timeline date precedes or equals the launch date in the correct order.

32 SEO Audit Tracker

Re-run audits and watch scores trend.

Fixes: No record of whether SEO fixes actually moved scores.

Gemini 3.5 Flash
App: an SEO audit tracker that stores history and shows trends.
Model: Gemini 3.5 Flash, optionally with the URL Context tool.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- I audit a page (paste content or a URL) on a schedule; store each audit with its date and score in Firestore.
Features:
1. Score title, meta, headings, content, images, and links.
2. Store the score history per page.
3. Render a trend chart per page so I see improvement over time.
4. Sign in with Firebase Auth.
Deploy: provision Firestore and Auth and deploy to Cloud Run; keys server-side.
Validation:
- Each stored audit reconciles its line-item checks to its overall score.
- The trend chart reflects the stored history exactly.
Acceptance: a per-page score history with a trend that proves whether fixes worked.
Worked example: input and output
Input
Page: /products/organic-cotton-crew-tee Audit 1 (May 1, stored): score 58 Audit 2 (June 1, stored): score 79
Output
Score history (stored in Firestore): - May 1: 58. Line items: title weak (10/20), meta missing (0/15), headings ok, images missing alt, links thin. - June 1: 79. Line items: title fixed (18/20), meta added (14/15), headings ok, images still need alt (5/15), links improved. Trend chart: rising 58 -> 79 over one month; next gain is image alt text. Persistence and access: each audit stored with its date and score; signed-in via Firebase Auth. Guardrail: each stored audit reconciles its line-item checks to its overall score; the trend chart reflects the stored history exactly, with no recomputation drift.

33 Wholesale B2B Inquiry Portal

Gated line-item requests stored for follow-up.

Fixes: B2B inquiries lost in email with no structure or status.

Gemini 3.5 Flash
App: a wholesale and B2B inquiry portal with sign-in and stored requests.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- A form where buyers submit company details and line-item requests; store submissions in Firestore.
Features:
1. Sign buyers in with Firebase Authentication.
2. Let them build a multi-line request with quantities.
3. Store each inquiry with a status.
4. Generate a clean summary email I can send back.
5. An owner view that lists and filters inquiries.
Deploy: provision Firestore and Auth, deploy to Cloud Run, keys server-side; monitor cost.
Validation:
- Submissions persist with correct line items and totals computed in code.
- Only signed-in buyers can submit; the owner view shows every stored inquiry.
Acceptance: a gated B2B intake that captures structured, status-tracked requests.
Worked example: input and output
Input
Signed-in buyer: Northside Outfitters Request: 50 Organic Cotton Crew Tees, 30 Organic Cotton Hoodies
Output
Inquiry stored (status: New): - 50 x Organic Cotton Crew Tee - 30 x Organic Cotton Hoodie - Line total computed in code: 50 + 30 = 80 units Generated summary email (owner can send back): Subject: Your wholesale inquiry, Northside Outfitters Body: Thanks for the inquiry. We have logged 80 units across two styles (50 crew tees, 30 hoodies) and will follow up shortly with B2B pricing, lead times, and minimums. Reply here with your target delivery date and we will tailor the quote. Owner view: lists this inquiry with status, buyer, and unit count; filterable by status. Persistence and access: stored in Firestore; only signed-in buyers can submit via Firebase Auth; the owner view shows every stored inquiry. Guardrail: line items and totals computed in code, not by the model.

34 Email Sequence Builder

Persisted flows with merge tags for your ESP.

Fixes: Rebuilding email flows from scratch each time.

Gemini 3.5 Flash
App: an email-sequence builder with persistence and ESP-ready export.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- Inputs: sequence type (welcome, abandoned cart, win-back, post-purchase) and brand voice; store sequences in Firestore.
Features:
1. Generate each email with subject, preview text, body, call to action, and send-timing trigger.
2. Save and reload sequences.
3. Export with Klaviyo and Shopify Email merge-tag placeholders.
4. Sign in with Firebase Auth.
Deploy: provision Firestore and Auth and deploy to Cloud Run; keys server-side.
Validation:
- Merge-tag placeholders match the chosen platform's syntax.
- Saved sequences reload intact; timings are ordered correctly.
Acceptance: reusable, ESP-ready email flows that persist and export cleanly.
Worked example: input and output
Input
Sequence type: welcome; brand voice: warm, plain; platform: Klaviyo
Output
Welcome sequence (saved): Email 1 - send: immediately Subject: Welcome to the studio Preview: First access, plus 15% off Body: Hi {{ first_name|default:'there' }}, thanks for joining Design Delight Studio. You are in for first access to new drops and the reasoning behind every piece. Here is 15% off your first order to start. CTA: Shop the basics Trigger: list signup Email 2 - send: +3 days Subject: Why we build the way we do Preview: Fewer, better, certified Body: {{ first_name }}, we make a small range of GOTS-certified, durable staples instead of a flood of seasonal product. Here is the short version of why, and the three pieces to start with. CTA: Read the story Email 3 - send: +7 days Subject: Still deciding? Preview: Your 15% is waiting Body: {{ first_name }}, your welcome discount is still good. If sizing is the holdup, our guide runs slightly fitted, so size up for a relaxed look. CTA: Use your 15% Persistence: sequence saved to Firestore; reloads intact; signed-in via Firebase Auth. Export: merge-tag placeholders match Klaviyo syntax; send timings ordered immediately, +3 days, +7 days.

35 Multi-Store KPI Dashboard

Sheets-fed metrics in one signed-in view.

Fixes: Reporting gaps and no single, current view of the numbers.

Gemini 3.5 Flash
App: a KPI dashboard fed by Google Sheets with a written summary.
Model: Gemini 3.5 Flash.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- Connect a Google Sheet of my store metrics using AI Studio's Workspace integration.
- Optionally store snapshots in Firestore.
Features:
1. Render KPI cards, revenue, orders, conversion, average order value, from the Sheet.
2. Render trend charts and refresh on load.
3. Write a short plain-language summary of what changed.
4. Sign in with Firebase Auth so only my team sees it.
Deploy: provision the Workspace connection and Firebase, deploy to Cloud Run, keys server-side; monitor cost.
Validation:
- Every figure on the dashboard matches the source Sheet.
- The written summary follows only from the displayed numbers.
Acceptance: a signed-in dashboard whose numbers match the Sheet, with a plain-language readout.
Worked example: input and output
Input
Connected Google Sheet (this week's row): Revenue 42,180; Orders 612; Conversion 1.6%; AOV 68.90; Sessions 38,250
Output
KPI cards (read live from the Sheet): - Revenue: 42,180 - Orders: 612 - Conversion: 1.6% - AOV: 68.90 - Sessions: 38,250 Trend charts: revenue and orders by week, refreshed on load. Plain-language summary: Revenue rose week over week on a steady AOV of 68.90. Conversion at 1.6% sits below the 2 to 4 percent ecommerce norm, so traffic is healthy but the storefront is the lever to watch; a small conversion gain on 38,250 sessions would move revenue more than more traffic at the current rate. Persistence and access: optional weekly snapshots stored in Firestore; signed-in via Firebase Auth. Guardrail: every figure on the dashboard matches the source Sheet; the written summary follows only from the displayed numbers.

36 Affiliate and Referral Tracker

Codes and conversions tracked, gated, exportable.

Fixes: No system to issue codes and track referral conversions.

Gemini 3.5 Flash
App: an affiliate and referral tracker with per-affiliate access.
Model: Gemini 3.5 Flash for written copy; compute totals in code.
Build in Google AI Studio Build mode as a full-stack app.
Data and context:
- Store referral codes, referrers, and recorded conversions in Firestore.
Features:
1. Issue and store unique codes; record conversions against each.
2. Compute payouts in code; show a leaderboard.
3. Generate referral invite copy on demand.
4. Sign affiliates in with Firebase Auth so each sees only their own stats; an owner view sees all.
Deploy: provision Firestore and Auth, deploy to Cloud Run, keys server-side; monitor cost.
Validation:
- Payout math is computed in code and reconciles to recorded conversions.
- Access control isolates each affiliate's data; codes are unique.
Acceptance: a gated tracker that issues unique codes and reconciles payouts to conversions.
Worked example: input and output
Input
Affiliate: creator_jess; code: JESS10; recorded conversions: 7 orders, 420.00 attributed revenue; payout rate: 10%
Output
Computed in code (exact): - Conversions: 7 - Attributed revenue: 420.00 - Payout: 420.00 x 10% = 42.00 Leaderboard: creator_jess listed with 7 conversions and 42.00 pending payout; a second affiliate with 3 conversions ranks below. Invite copy generated on demand: "Love the basics? Share your code JESS10 for 10% off and earn on every order." Access control: creator_jess sees only their own stats via Firebase Auth; the owner view sees all affiliates. Persistence: codes, referrers, and conversions stored in Firestore. Guardrail: payout math computed in code and reconciles to recorded conversions; code JESS10 is unique.

Your First Build

Start in Basic. Open Google AI Studio Build mode, paste the Product Description Studio prompt, and run it on your free-tier Gemini key. You have a working tool in minutes, entirely in the preview, at zero cost. Graduate one workflow at a time.
  1. Get a key. Sign in with a Google account and grab a Gemini API key; the free tier covers Basic work.
  2. Open Build mode in AI Studio and paste a Basic prompt from this library. Review the live preview.
  3. Iterate with the chat panel or annotation mode until the output is right, then paste it into Shopify.
  4. Graduate deliberately. Move a workflow to Advanced only when it needs your whole catalog or an npm library, and to Master only when it must persist data, sign users in, or serve more than you.
  5. Watch cost at the deploy line. Keep tools in the preview or a private share for free; reserve Cloud Run for the few apps shoppers actually touch, and keep keys server-side.

What not to do first: do not start in Master, do not deploy a customer-facing app before you understand its per-visitor cost, and do not paste a real API key into client code.

Source: Google AI for Developers getting-started and Build-mode guidance.

Common Mistakes

The predictable errors: starting in Master before Basic, deploying a customer-facing app without understanding its per-visitor cost, pasting a real API key into client code, over-stuffing context when a small input would do, and trusting a model's arithmetic instead of computing in code.
  • Starting at the top. Master apps need Firebase, Auth, and a deploy. Begin in Basic, get a working paste-in tool in minutes, and graduate one workflow at a time.
  • Deploying blind. A Cloud Run app bills every visitor's Gemini calls to your key. Never expose a customer-facing app until you have capped calls per session and understood the cost.
  • Real keys in client code. The code is visible to anyone who opens the app. Use the proxy placeholder for client calls and Secrets Management for server-side keys.
  • Over-stuffing context. A single product description does not need your whole catalog. Large inputs cost more tokens and can dilute attention; scope the input to the task.
  • Trusting model math. Models are unreliable at arithmetic. For any pricing, payout, or reconciliation, instruct the app to compute in code and let the model only explain.
  • Treating these as Shopify apps. They do not install in your admin. Plan to paste output in, or wire the Admin API server-side deliberately.

Source: Google AI for Developers Build-mode guidance; this library's design notes.

Key Terms

A quick reference for the vocabulary in this class. These terms recur across Google's documentation and this library; precise names matter, because both answer engines and operators reward exactness over vague description.
TermWhat it means
Build modeThe AI Studio surface where you build apps from prompts, powered by the Antigravity Agent.
Antigravity AgentThe agent harness behind Build mode; maintains context, manages multiple files, and verifies code.
Full-stack appAn app with a React client and a Node.js server runtime, the AI Studio default.
npmThe package ecosystem the agent installs from automatically, for example a CSV parser or a chart library.
Secrets ManagementThe AI Studio setting that stores API keys for server-side code, never exposing them to the client.
FirebaseGoogle's app backend; the agent can provision Firestore storage and Authentication.
FirestoreFirebase's persistent database, used by Master apps to remember data between sessions.
Cloud RunGoogle's service for deploying an app to a scalable public URL; pricing applies.
Annotation modeIteration by highlighting any part of the app UI and describing the change in place.
AI ChipsToggles that attach features such as image generation or Maps data to a build prompt.
Context windowThe amount of text a model reads at once; Gemini 3 models accept one million input tokens.
Context-stuffingPasting a whole dataset into the window so the app reasons over all of it at once.
Gemini 3.5 FlashThe default model since Google I/O 2026; strongest agentic and coding model, about 4x faster.
Nano BananaGemini's image models; Nano Banana Pro for professional assets, Nano Banana 2 for volume.
SynthIDThe invisible watermark on every Google-generated image, video, and audio file.
BYOKBring your own key; client-side apps run on the end user's Gemini key through the proxy.

Source: Google AI for Developers documentation, 2026.

Remix Recipes

Every prompt here is a starting point. Five moves adapt any of them: stack two apps into one, swap the model, add a Shopify Admin API read, promote a Basic app to persistent Master, and localize for another market. Change the specifics; keep the five-block structure.
  • Stack two tools. Combine the SEO meta generator and the FAQ generator into one product-page assistant by merging their feature lists into a single prompt with two output tabs.
  • Swap the model. If a Basic app's output feels shallow on a hard task, change one line from Gemini 3.5 Flash to Gemini 3.1 Pro; if it is high-volume and simple, drop to 3.1 Flash-Lite to save cost.
  • Add a live read. Promote any Advanced app from pasted CSV to live data by adding the Shopify Admin API block: token in Secrets Management, calls server-side, client never sees the key.
  • Persist a Basic app. Turn a stateless generator into a Master tool by adding "save outputs to Firestore and sign in with Firebase Authentication," then deploy to Cloud Run with the cost note.
  • Localize it. Add "generate every output in English and in [language], matching tone in both" to any copy app to serve a second market, useful for stores selling across regions.

When a remix grows past what one prompt cleanly describes, split the work: build the core in one prompt, then use the chat panel and annotation mode to layer features. The agent maintains context across the conversation, so you do not have to restate the whole app each time.

Source: Google AI for Developers Build-mode iteration documentation; this library's design notes.

Frequently Asked Questions

Common questions about Google AI Studio, the models, the cost model, and how these apps fit a Shopify store, answered from Google's current documentation.
What is a one-prompt app?

It is a working application you build by pasting a single prompt into Google AI Studio Build mode. AI Studio generates the code and a live preview, and you refine it through chat or by highlighting the UI and describing changes.

Is Google AI Studio free to use?

Building in AI Studio is free; you supply a Gemini API key. Gemini 3 Flash and Gemini 3.1 Flash-Lite have free API tiers, and Gemini 3.1 Pro is free to try inside AI Studio. Deploying an app to Cloud Run can add hosting cost.

Which Gemini model should these apps use?

Gemini 3.5 Flash is the default and the right choice for nearly every app, since Google reports it beats Gemini 3.1 Pro on coding and agentic tasks at about four times the speed. Use Gemini 3.1 Pro for the hardest reasoning and 3.1 Flash-Lite for high-volume work.

Are these Shopify apps that install in my admin?

No. They are standalone tools that run in a browser on Google's infrastructure. You paste their output into Shopify by hand, or embed a deployed app by link. You can connect one to the Shopify Admin API from the server-side runtime, but that is a deliberate step, not automatic.

Who pays when a customer uses one of these apps?

Client-side apps shared from AI Studio use the end user's own Gemini key through a proxy, so they cost you nothing to share privately. An app you deploy to Cloud Run for shoppers uses your key for every visitor, so it carries real, usage-scaling cost.

Do I need to know how to code?

No. You describe the app in plain language and AI Studio's Antigravity Agent writes and manages the code. Knowing the five-block prompt structure and being able to read the result helps, but it is not required to start.

What can the one-million-token context window do for me?

It holds about 1,500 pages of text, so an app can reason over your entire catalog, all your policies, or hundreds of reviews at once. That powers the Advanced and Master apps that audit a whole catalog or mine a full review set in one pass.

Can these apps remember data between sessions?

Basic apps do not; they are stateless and run in the preview. Advanced apps keep data only within a session. Master apps persist data by provisioning Firebase Firestore, and they sign users in with Firebase Authentication.

How do I deploy an app so others can use it?

Deploy to Google Cloud Run from AI Studio for a public URL. You can also export the app as a ZIP or push it to GitHub. Cloud Run pricing applies, and a deployed app uses your Gemini key for all users.

Is my API key safe in a shared app?

Only if you never put a real key in client code. AI Studio proxies client-side calls with the end user's key, and a placeholder stands in for yours. For server-side keys, use the Secrets Management feature so the key is never exposed.

Can I build native mobile apps too?

Yes. As of Google I/O 2026, AI Studio can build native Android apps in Kotlin and Jetpack Compose from a prompt, preview them in a browser emulator, and publish to a Google Play internal testing track. This library focuses on web apps, which fit store-owner tools.

What is the Antigravity Agent?

It is the agent harness that powers Build mode, the same one behind Google Antigravity. It maintains context across prompts and files, manages dependencies across multiple files, and verifies its code to reduce hallucinations.

Can these apps generate product images?

Yes, using Nano Banana. Nano Banana Pro produces professional assets up to 4K with high-fidelity text, and Nano Banana 2 is the high-volume option. Every generated image carries an invisible SynthID watermark, which is worth disclosing.

How is this different from the first app library?

The first edition listed 85 generic prompts that said only to use an AI API. This 2.0 edition is rebuilt for Google AI Studio specifically, names the model for each app, tiers them by capability, and explains exactly who pays for each one to run.

Can I edit the app after it is built?

Yes. Use the Build-mode chat panel to request changes, edit the code directly in the Code tab, or use annotation mode to highlight any part of the UI and describe the change in place.

What are the real limits I should know?

The full build experience is a desktop browser today, GitHub remote pull is not supported, and large context costs more and can dilute attention. None of these block the library, but they shape which tier an app belongs in.

Do I need a Google Cloud account?

You need a Google account and a Gemini API key to build. You only need Cloud Run, which is part of Google Cloud, when you deploy an app for others to use at a public URL.

Can a deployed app connect to my live Shopify data?

Yes, with setup. Store a Shopify Admin API token in Secrets Management and have the server-side runtime call the Admin API. This lets an app read a live product list or write a draft, and it follows the same server-side key-security rules as any integration.

How long does it take to build one of these apps?

A Basic app is usually minutes: paste the prompt, review the live preview, adjust once, and use it. Advanced and Master apps take longer because you paste data, install packages, or provision Firebase and deploy, but the build is still measured in minutes, not days.

Do I need Google Antigravity to use Build mode?

No. Build mode runs inside Google AI Studio in the browser. It is powered by the same Antigravity Agent harness, but you do not install or open Antigravity separately to build these apps.

Will these apps slow down my Shopify store?

No, because they do not run inside your storefront by default. They are separate browser tools. Only a customer-facing app you deliberately embed by link or iframe touches the shopper experience, and even then it loads independently of your theme.

Can I use these apps in languages other than English?

Yes. Gemini models are multilingual, so any copy or support app can generate output in another language. Add a line to the prompt asking for output in your target language, or build a localization toggle, as the remix recipes describe.

What happens to my data and the prompts I paste?

Pasted data stays in your AI Studio session for client-side preview apps, and in Firestore for Master apps you provision. As the app owner you are responsible for the data it handles, so avoid pasting sensitive customer information and follow your own privacy obligations.

Is the output safe to publish without checking?

Always review before publishing. The apps include validation gates, but you remain accountable for accuracy and claims. Never publish a specification, policy, or number the app produced without confirming it against your real product and policy facts.

Sources

Every product claim in this masterclass is sourced to Google's own documentation or to dated Google I/O 2026 coverage from May 2026. Shopify pain-point figures are from dated 2026 ecommerce coverage.
  • Google AI for Developers, "Build apps in Google AI Studio" — full-stack, Antigravity Agent, Firebase, Cloud Run, API-key model. ai.google.dev
  • Google AI for Developers, "Gemini 3" and model pages — 1M context, model lineup, free tiers.
  • blog.google, "Gemini 3.5: frontier intelligence with action," May 2026 — default model, AI Studio demos.
  • Google AI for Developers, "Long context" — the one-million-token window and its uses.
  • Google AI for Developers, image-generation docs — Nano Banana Pro and Nano Banana 2, SynthID.
  • Dated 2026 Shopify and ecommerce coverage — conversion, inventory, CAC, retention.
  • The original 85-prompt One-Prompt App Library — the first edition this masterclass curates and supersedes.
Bottom line: Google AI Studio turns one prompt into a working full-stack app, and Gemini 3.5 Flash plus a one-million-token window makes those apps genuinely useful to a store. Start in the free preview, build the tier that matches the job, and only pay for the few apps your customers actually touch.

About the Author

Robert McCullock

Architect-CEO of Design Delight Studio, a Boston sustainable streetwear studio run on a multi-agent AI stack. He builds the DDS Vibe Academy to document intent-based AI development in production.

Portfolio · LinkedIn

Build your first store tool today

Open Google AI Studio, paste one Basic prompt, and run it on your free-tier key. Move to Advanced when a job needs your whole catalog, and to Master when an app must remember data or serve your team.

Browse the DDS Vibe Academy

Free. No paywall. No signup. No certificate. Just the work.