Workflow Hub

I use Gemini Learn to fast-track my learning about Unblooms. Here's the prompt I used: ```text "I'm learning about the Unblooms, https://substack.com/home/post/p-194387968, https://unblooms.gainable.ai/, as well as any resource you can find to help me. I need to understand what it is, how it works, and ways I can use it when designing powerful learning experiences for my students." ``` Gemini Learn guided me through classroom examples of how Unblooms works, using examples from my own teaching because I customized my Gemini account with content from my teacher blog. Gemini helped me create three separate graphic organizers that my sixth-grade Math and Science students can paste into their interactive notebooks to track their decision trails when using and critiquing AI in class. Step-by-step: 1. I used Gemini Learn to study Unblooms and understand what it is, how it works, and how I could use it to design learning experiences for my students. 2. I gave Gemini Learn the Unblooms resources and prompt above, along with access to teaching content from my teacher blog through my customized Gemini account. 3. I asked Gemini Learn to explain Unblooms through classroom examples connected to my own teaching. 4. I used Gemini's guidance to create three graphic organizers for my sixth-grade Math and Science students. 5. My students can paste the organizers into their Math and Science interactive notebooks to track their decision trails when using and critiquing AI in class.

As a business owner, I used to check performance data across Google Analytics 4, Google Search Console, and Google Merchant Center by logging into three separate portals, navigating complex submenus, and exporting raw CSVs. To solve this, I built an automated workflow that connects my AI coding assistant, Google Antigravity, directly to all three Google platforms through a Google Cloud Service Account. Instead of manually clicking through dashboards, I can ask natural-language questions in plain English, such as "Did yesterday's email send generate traffic or phone bookings?" or "Are any products disapproved in Google Merchant Center?" I then receive instant, cross-platform analysis in seconds. Step-by-step: 1. I created a Google Cloud Service Account by going to Google Cloud Console (console.cloud.google.com) > IAM & Admin > Service Accounts > Create Service Account. I named it `ai-marketing-assistant`, copied the generated service account email address, such as `ai-marketing-assistant@<project-id>.iam.gserviceaccount.com`, and downloaded the JSON private key file to my local project folder. 2. In Google Cloud Console > APIs & Services > Library, I enabled the three required APIs: - Google Analytics Data API - Google Search Console API - Content API for Shopping (Google Merchant Center) 3. In Google Analytics > Admin > Property Access Management, I added the Service Account email address with "Viewer" permissions and copied my numerical GA4 Property ID. 4. In Google Search Console > Settings > Users and permissions > Add User, I added the Service Account email address with "Full" or "Restricted" access. 5. In Google Merchant Center > Settings & Tools > Account Access > Add User, I added the Service Account email address with "Standard" or "Admin" access and ensured that "Content API access" was enabled. 6. In my local AI environment, such as Google Antigravity or a custom Python environment, I authenticated using standard Google client libraries (`google-oauth2`, `googleapiclient`, `google-analytics-data`) connected to the downloaded JSON key file. 7. Anytime I launch a marketing campaign, want an SEO audit, or need to check product feed health, I ask my AI assistant a plain-English question. 8. The AI executes live API queries against GA4, Search Console, and Merchant Center, cross-references website traffic with bookings, and delivers an instant report.

My AI digest looked perfect and was quietly wrong. What actually fixed it. Every run succeeded. Every dashboard was green. And the content was still wrong. My digest invented "AI Moat Brief", a newsletter that does not exist. It reported scan counts nobody measured. It resurfaced week-old stories as fresh headlines. Here is what broke, and what fixed it. The sorting used to happen in my head: skimmed subject lines, unopened tabs, quiet guilt. The Signal is one email at 08:00: a single Make scenario calling Claude Sonnet through OpenRouter. It reads the last 24 hours of my RSS feeds and newsletters, keeps what touches what I am actively building plus the domains I need to stay current in, and arrives in the language I actually think in. Core items end with what it means for my work. Five to ten minutes, and I know where to go deep today. Structurally it looks like this, minus the content, rendered in English for this post (Image 1). No real edition is shown; section names and sample lines are illustrative. The dangerous failures were never pipeline failures. They were content failures, and the cause is structural: an LLM summarizing newsletters that already summarize primary sources is third hand by construction. Every hop strips attribution and adds confidence, and when data goes missing the model fills the gap the way LLMs do: fluently. Valid HTML, confident tone, green pipeline, wrong content. Image 2 is that whole failure class in one frame. Three rules closed the gaps I caught, all live in production: Step-by-step: 1. Verbatim or nothing. A source name is copied character for character, and a link exists only if that exact URL is in the input. The model copies; it never composes. 2. The model never generates metrics. Every count the report shows is injected by the pipeline after the model returns. 3. Recycled news gets demoted. A recap of recaps gets one line at most, and is dropped when the underlying story falls outside the collection window. Rules 1 and 3 lean on the prompt, and that is why the counters exist. The pipeline writes a hidden HTML comment into every email it sends: items, links, urls, cost, finish status. That line caught what I could not see. In one run, the published-links counter and the leftover-urls counter read 45 and 435: the only sign a new cleanup step was a silent no-op. Another morning the model stopped at 15,999 tokens against a 16,000 cap, one token from an email cut off mid-sentence. On the morning I wrote this they agreed, 21 links and 21 urls, and boring is the goal. Image 3 is that morning's actual comment, with the same two counters from the no-op run. The run itself has a dead man's switch on Healthchecks.io, so a missing 08:00 email reaches me before I notice. Honest limits: the $0.31 per report is a fresh measurement I am still validating, and I have not proven these rules hold as the source set scales. There is more behind every part of this; I would rather share it where it is wanted. Ask and I will put it in the comments: the three rules in full, the exact cost and what drives it, what this replaced in my day, how it compares to what is on the market, or the ugliest of the 15 documented bugs. I am sharing this because I doubt I am the only one building fragile things behind the scenes, and monitoring text is harder than monitoring uptime. What content-level checks do you run on LLM output, the kind pipeline monitoring cannot see? Real thresholds and embarrassing failures especially welcome.

As an AI consultant, I need to stay ahead of a landscape that evolves daily by reading dozens of industry articles each week. Manual tech watch quickly becomes a major time sink and pulls me away from client work. I built a specialized AI agent for challenge-focused summarization. Instead of producing generic, passive summaries, it answers two questions for every article: What specific problem, friction, or limitation does the article highlight? What practical solutions, tools, or actionable steps does it provide? The agent strips away marketing hype, introductory fluff, and generic definitions. It identifies the author’s core pain point and produces a quick-read summary focused on actionable technical or business solutions. This turns 15-minute reads into 30-second, high-value digests. By focusing on problem-solving rather than passive reading, the workflow helps me identify practical tools and frameworks I can apply directly to client projects and improve my consulting work. Step-by-step: 1. I provide the agent with a raw article link or the article text. 2. The agent filters out marketing hype, introductory fluff, and generic definitions. 3. It identifies the core pain point, friction, or limitation discussed by the author. 4. It extracts the concrete answers, including practical solutions, tools, and actionable steps. 5. It synthesizes the findings into a quick-read format focused on actionable technical or business solutions. 6. I use the digest to identify tools and frameworks that may apply directly to client projects.

Commercial vehicle maintenance information is often fragmented across driver reports, warning lights, fault codes, inspections, repair records, and vehicle history. This makes it difficult for smaller fleets to decide whether a vehicle can continue operating, requires scheduled repair, or should be stopped immediately. We built TruckFixr Fleet AI to turn an unstructured driver report into a clear, reviewable maintenance action. The workflow begins when a driver submits symptoms, photos, fault codes, and vehicle information through a mobile-friendly form. AI and optical character recognition extract the relevant details and organize them into a structured maintenance case. The report is then evaluated alongside available vehicle history and previous repairs. The workflow provides decision support through three practical actions: continue operating while monitoring, schedule an inspection or repair, or stop and escalate for immediate professional assessment. Final safety decisions remain with authorized fleet or maintenance personnel. After an inspection or repair, the confirmed cause, work performed, and outcome are recorded, creating a more complete vehicle history for future cases. The general workflow can be recreated using a mobile form, OCR, a vehicle-history database, an AI model, automation software, and a human-review dashboard. Step-by-step: 1. A driver submits symptoms, photos, fault codes, and vehicle information through a mobile-friendly form. 2. AI and optical character recognition extract the relevant details and organize them into a structured maintenance case. 3. The workflow compares the report with available vehicle history and previous repairs. 4. The system provides one of three decision-support actions: continue operating while monitoring, schedule an inspection or repair, or stop and escalate for immediate professional assessment. 5. Authorized fleet or maintenance personnel make the final safety decision. 6. After inspection or repair, the confirmed cause, work performed, and outcome are recorded in the vehicle history. TruckFixr has used this approach to support more than 100 vehicle-issue resolutions in early fleet pilots, helping fleets identify problems earlier, prevent avoidable breakdowns, and keep vehicles moving safely.

I built an interactive AI recommender for Medium publications and packaged it as a Gemini Gem. Medium writers who want their articles to be discovered can submit their pieces to a publication, which is like a digital magazine focused on a specific topic. However, there are hundreds of publications, so it can be difficult to find the right one for a particular article. A key resource is "Medium's Huge List of Publications Accepting Submissions." It contains basic information about each publication, but the list is difficult to navigate because of its size. My solution was to organize that information and use it as the source for an AI recommender. I packaged the system as a Gem because the interface is cleaner, and users do not need to see the sources I used. Step-by-step: 1. I asked Gemini to compile and format basic information for each publication, including its topic, size by number of followers, and a short description. 2. I consolidated that information in a Google Sheet. 3. I used the spreadsheet as a source for a Google Notebook (formerly NotebookLM). 4. I added instructions for the AI, like the following: "You are an expert guiding the user to find the ideal publications for their articles in Medium. Ask the user to write down what their interests, topics, etc., are; whether they are beginner writers; whether they want to start with a small publication (less than 1,000 followers), mid-size (a few thousand), or only the biggest (tens or hundreds of thousands). Ask them for any other personal information and details about their writing, and take that into account." 5. I packaged the system as a Gemini Gem instead of distributing it as a Notebook so users could access it through a cleaner interface without seeing the sources. It can be accessed at the following link: https://gemini.google.com/gem/1HDPzcE6Jls76V4I2tFZhIn-SbeeDe-_-?usp=sharing

I kept forgetting who I had lent books to, and spreadsheets felt like overkill. So I built Runo, a book-lending app for friends, without traditional coding. Runo (runo.club) is a web app where I can catalog my home library, get a unique shareable link, and let friends browse my books and request to borrow them. I can approve or decline each request with one click. Step-by-step: 1. I used Claude to think through the feature set, data model, and UX flow before writing a single prompt. This helped me avoid building the wrong thing first and gave me a clear blueprint for the Lovable prompts that followed. 2. I used Claude to create precise, narrowly scoped prompts for Lovable, with each prompt focused on a single change so existing functionality would be less likely to break. This significantly conserved Lovable credits. The React, TypeScript, and Supabase stack came out of the box. 3. I added two ways to scan books instead of requiring users to type titles manually: - Barcode scanner: Point the camera at an ISBN barcode to autofill the title, author, and cover using the Open Library API. - Cover photo scanner: Photograph the cover so Gemini 2.5 Flash can extract the title and author in under 2 seconds. 4. I routed the cover scanner through a Supabase Edge Function using Lovable’s AI Gateway, so the API key never touches the client bundle. 5. For every bug fix and feature, I followed the same iteration loop: describe the problem to Claude, get a precise Lovable prompt, push the changes to GitHub, and let Lovable auto-sync them. Claude and Lovable’s bidirectional GitHub sync made the process feel like pair programming. Tools used: Lovable, Claude (Sonnet), Gemini 2.5 Flash (via Lovable AI Gateway), Supabase, and GitHub. Live at: runo.club — public beta and free to use. Feedback welcome. #appbuilding #vibecoding #buildinpublic #lovable #nocode

I had a project that was perplexing me, so I asked an AI for help by simply typing, "I'm a stupid moron." The AI helped me with the issues I was having with my project. 1. I described my project-related difficulties by typing, "I'm a stupid moron." 2. I used the AI's help to address the issues I was having with my project.

For the start of the new school year, I wanted to use the current eastern Washington wildfires near Spokane with my two sixth-grade science classes. I wanted an AI tool to create a website I could upload to my hosting service. The site needed to provide daily updates from verified news sources, along with air quality data comparing Spokane in eastern Washington, Kirkland near Seattle, and Chimacum, where we live, on the western side of the state. I also wanted to include a simulation where students could change different variables to see how they affect the direction of the smoke and air quality. I could not decide which AI service to use, so I entered the same prompt into my personal paid Claude and Gemini Spark accounts, as well as my free teacher ChatGPT and Claude accounts, to compare which one created the best site for students. Here is the prompt I used: "Create a dynamic website with information of the Spokane, WA 2026 wildfires. Information include only verified facts from credible news sources. Information needs to be updated from when the largest fire started until it is completely put out. At that point, this website is complete and done. Include a page with air quality data. Provide air quality data on a daily basis from the onset of the fire to the end of the fire. Include Spokane, Kirkland, and Chimacum to compare the air quality from eastern WA near the fire, mid WA, and western WA. Include factors that explain the air quality such as winds, inversion, altitude of smoke and any other relevant data that students can view to answer questions. Provide a way for students to click on different variables to see how different factors affect the fire, direction of smoke, and air quality. Use the /inversa-design skill to make the website." Here is a portal page with links to all four sites: https://educatoral.com/2026SpokaneFire/ Step-by-step: 1. I identified the eastern Washington wildfires near Spokane as a topic for my two sixth-grade science classes. 2. I defined the website requirements: verified news updates, daily air quality data, comparisons among Spokane, Kirkland, and Chimacum, and a student-facing smoke and air quality simulation. 3. I used the same prompt with my paid Claude and Gemini Spark accounts and my free teacher ChatGPT and Claude accounts. 4. I compared the sites created by the four AI accounts to determine which one would be best to use with students. 5. I collected links to all four sites on this portal page: https://educatoral.com/2026SpokaneFire/

I created a Gemini Gem with custom instructions. When I paste a link to the previous Sunday’s sermon, the Gem “watches” the video and creates five messages—one for each weekday. Each message uses a specific engagement method, such as a link to watch the sermon for anyone who missed it, a graphic featuring a verse from the sermon, or a reflection question tied to the sermon’s theme. After I approve the copy, the Gem creates a properly formatted Google Sheet in my Google Drive, ready to be dragged and dropped into our text provider. Within five minutes, I have content deployed that extends the impact of the 45-minute sermon throughout the week. Step-by-step: 1. I paste a link to the previous Sunday’s sermon into my Gemini Gem. 2. The Gem watches the video and creates five weekday messages. 3. I review and approve the copy for each message. 4. The Gem creates a correctly formatted Google Sheet in my Google Drive. 5. I drag and drop the content into our text provider for deployment.

I regularly use ChatGPT for lesson planning and materials development with students ranging from EFL learners to UK undergraduates. I keep a separate anonymous thread for each student, so GPT can track the context and suggest the best direction for the next session. I also contribute my experience as a tutor while using AI to create fresh worksheets based on typical materials from various UK exam boards. Today, I had a successful interview for a lecturer role. Gemini helped me design and plan my demo seminar, and it looks like I’ve landed the job. Step-by-step: 1. I create a separate anonymous thread for each student. 2. I use ChatGPT to track each student’s context and suggest the best direction for the next session. 3. I combine AI-generated ideas with my experience as a tutor when planning lessons and developing materials. 4. I use typical materials from various UK exam boards as the basis for creating fresh worksheets. 5. For my lecturer interview, I used Gemini to design and plan my demo seminar. 6. I had a successful interview, and it looks like I’ve landed the job.

I use AI to create personalized tools and social stories that help therapists and group-home staff better understand my son’s complex disability and support his independence as an adult. Step-by-step: 1. I use AI to create personalized tools for my son. 2. I create social stories that help therapists and group-home staff better understand his complex disability. 3. I use these resources to support his independence as an adult.

I created an online app where my friends can select the gigs they plan to attend. It shows who is going to each gig and when, along with a clear festival-wide timeline. The festival host only provides stage-based schedules, which are difficult to read and coordinate. My app brings the information together in a more practical format for planning with friends. Step-by-step: 1. I created an online app for coordinating festival plans. 2. I added a way for friends to select the gigs they plan to attend. 3. I organized the selections to show who is going to each gig and when. 4. I created a clear timeline that combines the festival’s stage-based schedules. 5. I used the combined timeline to make planning and coordination easier.

This World Cup 2026 poetry generator scraped the web for match information and called LLMs to help users generate match-specific poems. 1. A daily schedule triggered web scraping to collect match information. 2. When a user requested a poem, the generator used that match information to create a new match-specific poem with help from LLMs.

Creative ideas often appear in the wrong place: inside unrelated chats, jokes, photographs, or practical problems. The problem usually isn't a lack of ideas. Ideas are scattered across time and conversations, while humans are bad at holding dozens of active threads at once. I built this workflow to turn scattered conversation history into a recoverable creative idea system. Its job isn't to decide what matters; it's to make sure good ideas can come back. I keep four jobs separate: a local script tracks what has been processed, an extraction model finds ideas and recurring language, a synthesis layer connects related concepts across conversations, and I decide whether an idea is alive and worth doing now. Step-by-step: 1. I export chats roughly once a week so the recent past doesn't disappear before it becomes useful. 2. I use an Incremental Archive to compare exports and mark conversations as New, Changed, Unchanged, or Missing. Only new and changed conversations need extraction. I reprocess changed conversations in full because later context can change earlier meaning. The Incremental Archive decides what changed; Creative Idea Recovery decides what is worth remembering. 3. I extract information conversation by conversation, looking for creative concepts, project ideas, visual motifs, writing fragments, systems, metaphors, recurring language, worldbuilding, and unfinished ideas. 4. I preserve the raw language instead of aggressively normalizing labels. “liminal space” and “The Liminal Space” may later mean different things, while “desert” may belong to the same family without being identical. Raw labels are evidence. 5. I build a lexicon above the extraction layer without replacing the original terms. It records aliases for the same concept with different spellings, variants from the same family with meaningful nuance, subtypes that are more specific, related concepts that are connected but not interchangeable, and concepts to keep separate because they are similar but distinct. I normalize obvious formatting noise without flattening meaning. 6. I periodically review recurring container terms such as autonomy, worldbuilding, or liminal space across the corpus. I don't only ask how often a term appears; I ask what different things it is doing across contexts. 7. I leave the long tail alone. Not every strange one-off phrase needs a taxonomy. The Royal Sleeping Tail™ can remain gloriously unclassified. Rare ideas can stay raw until they recur, become useful, or connect to something else. 8. I build a browseable creative inventory so I can ask questions such as: - Show me creative concepts I never made. - Which visual ideas disappeared? - Which concepts resurfaced several times? - Which unfinished ideas fit low physical energy? Each concept can include its name, description, sources, recurrence, status, and timing. 9. I track state lightly so the system doesn't keep rediscovering something already hanging on the wall. 10. I use Timing rather than Priority because creative ideas aren't invoices. I classify them as Now when they are alive and actionable, Someday when they are valuable but not right for this period, Maybe when they are worth preserving, and Unreviewed when they haven't been assessed yet. I make this decision, not the system. 11. I let ideas resurface intelligently by combining timing with recurrence. For example, I can ask, “Show me Now ideas requiring little physical effort” or “Which Maybe ideas have resurfaced three or more times?” An idea that keeps returning may simply be waiting for the right conditions. 12. I use recent scans as short-term continuity. They can say, “You mentioned this once. It seemed meaningful. Here it is again.” I can then answer, “Still alive,” “That passed,” or “This is ready now.” Retrieval is the intervention. 13. I use evidence to challenge unreliable self-assessment, such as “I never have good ideas.” The archive doesn't respond with motivational fluff; it points to evidence of progress that can be hard to feel from inside the current day. 14. I treat renewed access as the real product, rather than the archive itself. The system exists so I can say, “I know I thought about this before. Find it,” “Show me what I already made possible but forgot existed,” or “Give me something worth making today.” When my brain says, “I never have good ideas,” the system can point toward the pile of evidence and say, “I dispute this claim.” For non-octopuses. 😑🐙 A creative life shouldn't require eight arms, perfect memory, and seventeen open mental tabs.

I used ChatGPT to help create a book in a specialized area of hypnosis. It still needs some refining. The book provides a verbal account of the actions parents need to take to accomplish their goal. It supports both the parents and the child through positive reinforcement. As the parents speak their part, the message becomes ingrained in them as well. Step-by-step: 1. I used ChatGPT to help create the book. 2. I focused the content on the actions parents need to take to accomplish their goal. 3. I used positive reinforcement to support both the parents and the child. 4. I had the parents speak their part so the message would become ingrained in them as well.

Last year, my daughter was diagnosed with a rare autoimmune disease. Like any parent in that situation, I wanted to understand everything I could so we could make the best decisions for her care. I used both Gemini and ChatGPT to help me sort through the medical literature, treatment options, possible side effects, and how other countries approach treatment. I also turned to ChatGPT to identify the leading specialists in the country — thankfully, our referred doctor turned out to be one of them, which gave us even more reassurance. More than anything, it helped demystify the disease and make us feel confident that we were doing everything we could. She's doing really well on her medications, and seeing her recover has been an enormous relief. Step-by-step: 1. I gathered the diagnosis, questions, and medical context I needed to understand more clearly. 2. I used Gemini and ChatGPT to work through medical literature, treatment options, possible side effects, and approaches used in other countries. 3. I asked ChatGPT to identify leading specialists and explain why their experience was relevant. 4. I compared the research with the care team we had already been referred to. 5. I used the findings to prepare better questions and support discussions with clinicians, not to replace medical care.

I built Atlas to turn AI-assisted creative findings into readable project cards with source links, relationships, comments, and a calm HTML interface. Extracting creative findings is only half the job. Once fragments, metaphors, visual ideas, and research trails accumulate, I need somewhere to return to them and keep working. Atlas is that project layer over my old conversations. AI helps me revisit source material and suggests findings worth keeping. I decide what they mean, how to name them, where they belong, and which relationships matter. The results become readable cards. My harvesting system points to conversations that seem rich, and then I revisit them with AI. We identify existing projects, standalone findings, recurring material, and connections. Sometimes the review sparks new ideas. After just two rich conversations, we had 28 cards, including four collection cards and three new ideas. The harvest is the radar. The review is where interpretation happens. Atlas keeps the results usable. Step-by-step: 1. I let the harvest flag chats containing project ideas, unusual language, visual concepts, or unfinished thoughts. It suggests where to look without deciding what matters. 2. I review promising conversations with AI and ask, “What here deserves a place in the creative system?” AI suggests findings and connections, while I correct interpretations, separate unrelated material, and decide what belongs together. The card structure grows out of that dialogue. 3. I create readable cards with information such as a name, category, description, findings, sources, relationships, questions, and comments. The contents depend on the material: a story needs different information from an essay. The goal is to recognise and understand the work when I return. 4. I group recurring fragments into collection cards for language finds, story material, or visual motifs. Individual items stay visible without turning Atlas into hundreds of tiny, barely distinct cards. 5. I link each card back to the original conversations so I can access exact wording, context, and how an idea developed. Several conversations can feed one card, giving me a stable starting point while its source history grows. 6. I record meaningful relationships that I recognise, such as shared themes, predecessors, spin-offs, fictional worlds, or research overlaps. Similar words alone do not establish a meaningful relationship. Categories provide visual orientation, while relationships let me move across them. 7. When I remember a source but cannot find it yet, I leave a comment: “Find and link the old conversation about XYZ.” When it turns up, I attach it and update the comment: “Found it, now linked.” This turns imperfect memory into a useful breadcrumb, so missing sources do not have to stop the work. 8. I use a small green indicator to mark cards with updates I have not viewed yet, such as a new source, finding, relationship, or resolved comment. This shows me where something changed without requiring me to check every card. 9. I let cards stay unfinished. One paragraph, one source, and an open question can already make a useful card, and more context can accumulate later. Reviewing old material can also spark new work, making the archive generative through fresh interpretation. 10. I keep the HTML environment calm and make it feel like a reading room: Browse → recognise → open → read → follow a source or relationship. Code handles IDs, CSV rows, statuses, and consistency checks underneath while I work with readable cards. Each layer answers a different question: the harvest tells me where to look, the collaborative review tells me what is there and what it means, and Atlas keeps the result usable. AI helps me notice and organise, while I assign meaning. Atlas preserves the results with the original conversations available underneath. I can navigate backwards to the source and sideways to related work, starting wherever I am. The harvest tells me where to look, the review tells me what I found, and Atlas makes sure I can use it again.