Share your best AI workflow. We could show it to 2M+ people.

I run operations for my husband’s residential architecture firm, and I have no coding background. After every site visit, dozens of photos landed in Google Drive with names like `IMG_8834.JPG`. Renaming and filing them took about an hour per visit—when it happened at all. Otherwise, the photos sat unnamed and difficult to find, creating a professional liability gap because they document site conditions on a specific date, as well as lost portfolio material and a hole in the firm’s permanent project archive. I solved this by building a Claude skill: a saved set of instructions that runs the same way every time with one command. I trained it to examine each photo through the lens of a residential architect, describe what the image actually shows using our professional vocabulary, and rename the file in a consistent format. For example, `IMG_8834.JPG` becomes `2026-07-17_03_side-elevation-porch-brick-piers.JPG`—searchable, legible, and ready to file. Because it’s a skill rather than a one-off chat, it’s a file I can hand to anyone in the office. Everyone runs the same process and gets consistent output. Step-by-step: 1. I gathered the raw photos into one “unsorted” folder in Google Drive. 2. In Claude’s desktop app, I used Cowork mode, which handles actual files, and connected only that folder—not my whole Drive. The skill can only see and touch what I connect, so I use the narrowest folder that does the job. 3. I created a skill that tells Claude to read each photo, identify what it shows using my industry’s vocabulary, and rename each file in my standard `date_sequence_description` format. I wrote mine for residential architecture, but the approach can also work for real estate, inspections, insurance, and other field work. 4. I ran the skill with one command, and Claude worked through the folder photo by photo. 5. I had the renamed photos filed into a dated site-visit folder so they were ready to reference by number in reports. 6. I handed the skill file to teammates so they could run it on their own machines and get the same result. One caveat for anyone using this on business files: check your client confidentiality obligations and your AI vendor’s data policy before pointing any tool at project files. We did. I wrote up the full build, including how to decide when something should be a skill versus a regular Claude conversation, at The 2040 Studio: https://the2040studio.substack.com/p/every-img_8834jpg-is-snitching-on

Teachers give assessments on devices provided to students, but students can use AI to cheat. I built TypeWriter to bring the level of security found in tests like the ACT and SAT to everyday assessments. Teachers can create assessments from existing materials, post them in a locked environment, and grade submissions and provide feedback on the same website. I built TypeWriter as a high school teacher, and it is free for teachers. Step-by-step: 1. Teachers create an assessment using their existing materials in TypeWriter. 2. They post the assessment in TypeWriter’s locked environment. 3. Students complete the assessment on the provided devices. 4. Teachers grade the assessments and provide feedback on the same website.

I built an AI-assisted vertical grain supply-chain resilience workflow after discovering that the rye flour we normally use for homemade bread had been discontinued. I started by asking ChatGPT to locate alternative retail and bulk suppliers for rye and spelt flour. We compared package sizes and prices, contacted local mills and bulk-food suppliers directly, and expanded the search from finished flour to locally available whole grain. The workflow then moved offline. ChatGPT helped us identify the resources we already had: agricultural land, grain bins, a cultivator, a seeder, an old but functional industrial grain crusher, and even a combine. We also realized that a friend owns a seed-cleaning plant and that our farming neighbors can connect us with local rye and spelt growers. Our next steps are to test whether a household coffee grinder can produce sufficiently fine flour from grain, source fresh food-grade rye and spelt locally, and investigate growing a small crop ourselves. The biggest lesson was that AI was most useful not because it gave us one answer, but because the conversation kept changing the question. We began with “Where can I buy rye flour?” and ended with “Why are we buying rye flour when we already have most of the infrastructure required to produce it ourselves?” Step-by-step: 1. I asked ChatGPT to find alternative retail and bulk suppliers for rye and spelt flour after our usual rye flour was discontinued. 2. We compared package sizes and prices, contacted local mills and bulk-food suppliers directly, and expanded the search from finished flour to locally available whole grain. 3. We reviewed the resources already available to us, including agricultural land, grain bins, a cultivator, a seeder, an old but functional industrial grain crusher, and a combine. 4. We identified additional local resources: a friend’s seed-cleaning plant and farming neighbors who can connect us with local rye and spelt growers. 5. We plan to test whether a household coffee grinder can produce sufficiently fine flour from grain, source fresh food-grade rye and spelt locally, and investigate growing a small crop ourselves. 6. We reframed the question from where to buy rye flour to whether we could produce it ourselves using the infrastructure already available to us.

I’m a very unsophisticated user—and an older man—so my use of ChatGPT is still fairly basic. But it has changed my life. I use ChatGPT as a research assistant for a book I’m writing. In practice, what I do is not much more than an in-depth search, but ChatGPT has taken me places in this journey that I would have thought impossible just three months ago. We’re now deeply engaged in solid research that will likely last about two years before we reach the writing phase. I’m energized by what we’re doing and wanted to share the experience. I believe AI is going to change the way working historians conduct research. Step-by-step: 1. I use ChatGPT as a research assistant for the book I’m writing. 2. I use it for in-depth searching and research. 3. I continue developing the research with ChatGPT over an expected two-year period before beginning the writing phase. 4. I reflect on how this process is changing my research journey and the way historians may conduct research.

I kept struggling to stay consistent with social media for my own projects. Writing captions, choosing hashtags, designing graphics, and scheduling content across platforms was taking hours every week—time I would rather spend building. So I built AutoKonnekt. You give it one sentence or a website URL, and it generates a full month of on-brand social posts, including captions, hashtags, and AI-generated images. It then schedules them across Instagram, Facebook, LinkedIn, TikTok, Pinterest, X, and Threads. The hardest part was getting the AI to sound like a specific brand’s voice instead of producing generic marketing copy. That took a lot of iteration on the prompting side. It’s live now with a free plan if anyone wants to try it: https://autokonnekt.com I’d love to hear what the community thinks. For those of you managing social media manually, which part takes the most time? I’m trying to figure out what to build next. Step-by-step: 1. I enter one sentence describing the project or provide a website URL. 2. AutoKonnekt generates a month of on-brand social posts with captions, hashtags, and AI-generated images. 3. I use the generated content across Instagram, Facebook, LinkedIn, TikTok, Pinterest, X, and Threads. 4. AutoKonnekt schedules the posts across those platforms. 5. I iterate on the prompting to make the content sound like the specific brand instead of generic marketing copy.

Most businesses don't need another AI tool. They need to automate the repetitive bottleneck already slowing the team down. A simple example is connecting the tools already in use: Lead → AI qualification → CRM → WhatsApp → follow-up Instead of adding more software, automate the repetitive steps between these tools. The goal isn't more AI; it's less manual work and faster execution. Step-by-step: 1. Identify the repetitive bottleneck slowing the team down. 2. Capture the lead and use AI to qualify it. 3. Send the qualified lead to the CRM. 4. Use WhatsApp for follow-up. 5. Connect the steps so the process requires less manual work and supports faster execution.

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 built a workflow to examine complaints I had about a local bureaucratic service and check whether my account of what happened was supported by the written record. I was concerned about delays, incomplete handling, and the way my case progressed after I gave feedback about a harmful aspect of the service and asked for a different person to handle the dossier. That request was refused. Afterwards, I felt that the process had become slower, more confusing, and more prone to mistakes. Rather than asking GPT to confirm that the service had handled things badly, I used it to test my own interpretation against the evidence. I asked GPT to review the relevant emails and dossier communications, reconstruct the chronology, and identify requests, replies, delays, unresolved issues, and changes in how the case was handled over time. We then compared the periods before and after my feedback and request for reassignment. The central questions were deliberately neutral: Were my complaints grounded in the correspondence? Did the handling of the dossier objectively become slower or more incomplete afterwards? Were there concrete errors or unanswered questions in the record? Or was I remembering the experience as worse than the documentation supported? This distinction mattered to me. The workflow was not designed to produce a verdict or turn frustration into evidence after the fact. It was designed to challenge my assumptions and separate what I felt from what could actually be demonstrated. Where the documentation supported a complaint, we could point to the relevant chronology, delays, unanswered questions, or inconsistencies. Where the evidence was incomplete or ambiguous, that was noted too. The result was a more grounded account of the case: not “I know this was handled terribly,” but “these are the parts of my experience that are supported by the written record, these are the parts that remain uncertain, and this is where the timeline changed.” In simple terms, the workflow was: emails and dossier communications → chronology reconstruction → before-and-after comparison → review of delays, errors, and unresolved issues → evidence check against my complaints → a grounded account of what can and cannot be supported. What I liked about this workflow was that it used AI as a reality-checking tool rather than an agreement machine. It helped me test whether my criticism was actually anchored in the record before I relied on it in further communication. Step-by-step: 1. I gathered the relevant emails and dossier communications about my case. 2. I asked GPT to reconstruct the chronology and identify requests, replies, delays, unresolved issues, and changes in how the case was handled. 3. I compared the period before and after my feedback about a harmful aspect of the service and my request for reassignment, which was refused. 4. I examined whether the record showed that the process became slower or more incomplete, and whether it contained concrete errors or unanswered questions. 5. I separated points supported by the documentation from points that remained incomplete or ambiguous. 6. I used the resulting chronology and evidence check to create a grounded account of what my complaints could and could not demonstrate.

I used Claude to review the book *Why Machines Learn*. Then I went through each chapter while Claude questioned me at relevant points. To make the concepts more concrete, I used interactive graphs with x and y axes. The first graph shows the relationship between x and a function, along with the slope of the curve. It uses f(x) = x³ with a tangent line illustrating the derivative. I can drag a slider to move the point and watch the slope change, then switch to 3x to compare it with a straight line. The graph demonstrates several ideas: - Sliding x to 0 on x³ makes the tangent flat and the slope 0, so a small nudge barely changes the output. This is similar to a flat spot at the ends of a sigmoid, where learning stalls. - Sliding to 2 and then to −2 shows a slope of 12 at both points. Because the derivative is 3x², it is positive on both sides and the curve is always climbing. - Switching to 3x makes the tangent lie directly on top of the line, with a constant slope of 3 everywhere. - The nudge-check box tracks the derivative closely, showing that the derivative is essentially “change in output ÷ small change in input.” The second graph shows the input and output layers of a small pattern detector. It represents a 2 × 2 image flattened into four inputs, a hidden layer of two neurons, and two outputs. The weights are set by hand so the network can distinguish a vertical line from a horizontal one. I can click the pixels to change the image and watch the numbers flow through the network. The setup uses weight +1, weight −1, ReLU activation defined as max(0, z), softmax output, and all biases set to 0. For example: - Flatten: x = [1, 0, 1, 0] - h1 = ReLU((1)(1) + (-1)(0) + (1)(1) + (-1)(0)) = ReLU(2) = 2 — left column versus right column - h2 = ReLU((1)(1) + (1)(0) + (-1)(1) + (-1)(0)) = ReLU(0) = 0 — top row versus bottom row - Output: scores (2, 0) → softmax → Vertical 88%, Horizontal 12% The graph includes examples for a left vertical line, top horizontal line, right vertical line, and diagonal. Seeing the numbers change as the factors change really helps bring these concepts to life for me. Step-by-step: 1. I used Claude to review *Why Machines Learn* and question me as I worked through each chapter. 2. I used an interactive x-and-y graph to explore how a function changes and how its slope relates to the derivative. 3. I moved the slider across f(x) = x³, including 0, 2, and −2, to observe how the tangent and slope changed. 4. I switched the graph to 3x and used the nudge-check box to compare a constant derivative with the changing derivative of x³. 5. I explored a second interactive diagram representing a 2 × 2 image, four inputs, two hidden neurons, and two outputs. 6. I clicked different pixels and watched the ReLU activations, output scores, and softmax predictions change for vertical, horizontal, and diagonal patterns.

Maintaining an AI-built property finance app: proven Codex testing, release and handoff workflows? I’m building a small family property-management app using ChatGPT for requirements and Codex desktop on Linux for implementation, with TypeScript, PostgreSQL/Supabase and Vercel. It covers renovation forecasts, quotes, costs and payments, operating income and expenses, and family loans. The app is already in use. We have automated checks, isolated synthetic data, financial reconciliation and controlled releases. I’m looking for practical experience from people who have maintained an AI-built financial or admin app beyond its prototype: 1. How do you keep requirements, acceptance tests, candidate versions and deployed releases aligned across long Codex threads and workspaces? 2. What browser-testing and release-evidence workflow has caught failures that builds and unit tests missed? 3. Which GitHub skills or agent packages have improved your results without conflicting instructions or excessive process? 4. What works well for translating approved mockup images into maintainable application code, including screenshot comparison and mobile behaviour? 5. What broke after deployment, and what did you change? Links to maintained repositories, runbooks, example acceptance records or fictional-data screen recordings would be especially useful. The aim is to improve the existing application and workflow while keeping everyday tasks understandable for non-technical family users.

My friend shot a short film and gave me his hard drive to help with post-production. It contained more than 400 clips, with no clear way to tell when each one had been shot. I asked Claude to review the metadata for every clip and group them by timestamp, so they were organized by shoot session instead of sitting in one large folder. Claude also built a spreadsheet listing each clip, its shoot session, the date, runtime, and file size. This saved my friend the hassle of reviewing every clip manually. Step-by-step: 1. I received my friend’s hard drive with more than 400 short-film clips. 2. I asked Claude to review the metadata for every clip. 3. I had Claude group the clips by timestamp and organize them by shoot session. 4. I had Claude create a spreadsheet with each clip’s shoot session, date, runtime, and file size. 5. My friend could avoid going through every clip manually.

A while ago, my dad told me he wanted to use AI to analyze World Cup matches. He had never coded before, and his AI experience was mostly limited to occasionally asking Gemini a question. I installed Claude Code for him and gave him a few prompting tips. He ended up building a full football analytics site himself and deploying it on Vercel so he could show it to his friends. Getting started with AI is easier than people assume. Sometimes, you just need a project you genuinely want to make. Now that the Premier League season has kicked off, he’s already reworking the site for it. Step-by-step: 1. I helped my dad choose a football analytics project he genuinely wanted to build for analyzing World Cup matches. 2. I installed Claude Code for him, since he had never coded before. 3. I gave him a few prompting tips and let him use AI to help build the site. 4. He built a full football analytics site himself. 5. He deployed the site on Vercel so he could show it to his friends. 6. After the Premier League season kicked off, he began reworking the site for the new competition.

I applied for Schengen visas from India for my wife and me, using Claude to handle the process without an agent. We had two linked applications, with me as her sponsor. The biggest value came from determining which rules actually applied and making sure both files were consistent. Claude used the official checklist and reviewed dozens of recent threads about visa rejections to identify common gaps and ensure our applications addressed them. Initially, I used a generic India-wide checklist. Claude caught that mistake and found the destination’s jurisdiction-specific requirements for New Delhi. This materially changed the application and significantly reduced the paperwork. Each correction removed unnecessary work and saved me a lot of time. Claude drafted the document set, including two cover letters, a sponsorship affidavit for notarization, a self-employment letter, and a day-by-day itinerary. It then kept simplifying the documents and suggested workarounds wherever needed, drawing on the Reddit research. It also cross-checked the finalized forms and documents and flagged human errors, including a missing digit in my mobile number and a checklist box that contradicted the letter beside it. Finally, it helped with the practical details: sequencing our appointments, deciding which documents needed originals or copies, and determining what to do if counter staff asked for something that was not on the governing checklist. Both visas came through. For me, the useful part was having one system research the requirements, build the paperwork, and audit the entire application for inconsistencies before submission. Step-by-step: 1. I gave Claude the details of our two linked Schengen visa applications, including that I was sponsoring my wife. 2. I had Claude review the official checklist and dozens of recent visa-rejection threads to identify common gaps. 3. I asked it to verify the requirements for our destination and the New Delhi jurisdiction instead of relying on a generic India-wide checklist. 4. I used Claude to draft and simplify two cover letters, a sponsorship affidavit for notarization, a self-employment letter, and a day-by-day itinerary. 5. I asked it to suggest workarounds wherever needed, based on the Reddit research. 6. I had Claude cross-check the finalized forms and documents for inconsistencies and human errors, including the missing mobile-number digit and the contradictory checklist box. 7. I used its guidance to sequence our appointments, determine which documents needed originals or copies, and prepare for requests from counter staff that were not on the governing checklist. 8. I submitted the applications after the research, paperwork, and consistency checks were complete.

Most people remember the predictions they got right and rationalize the ones they got wrong. This workflow forces every meaningful forecast into a structured record so you can measure not only whether you were right, but also whether your confidence was justified. The objective is not simply to make more correct predictions. It is to make your stated confidence increasingly match reality. For every forecast, record the following: Step-by-step: 1. State exactly what you believe will happen. The claim must be specific enough to resolve later. Bad: “AI stocks look vulnerable.” Better: “The Nasdaq-100 will fall at least 15% from its current level within six months.” 2. Assign a numeric probability from 0–100%. Avoid vague terms such as “likely” or “probably” without attaching a percentage. 3. Define when the prediction should resolve, such as within 30 days, by year-end, or within 12 months. 4. Identify the one to three factors most responsible for the forecast being correct. This makes the causal thesis explicit. 5. Specify what evidence would materially weaken or invalidate the forecast. This prevents moving the goalposts later. 6. Define in advance what counts as correct, incorrect, or ambiguous. Do not wait until the outcome is known to decide how success will be measured. 7. Freeze the forecast by preserving the original forecast exactly. If new information materially changes your view, create a new forecast rather than editing the old one. This preserves the forecasting record. 8. At the end of the time horizon, record what actually happened. Then distinguish between a thesis error, in which the underlying reasoning was wrong; a timing error, in which the thesis may have been right but the forecast horizon was wrong; and a driver error, in which the expected outcome occurred but for different reasons. 9. Review calibration by comparing probability bands with actual results over time. If forecasts assigned 70% confidence are correct about 70% of the time, your confidence is well calibrated. If high-confidence forecasts fail too often, you are overconfident. If lower-confidence forecasts succeed too often, you may be underconfident. Do not overinterpret tiny sample sizes; calibration becomes more meaningful as forecasts accumulate. 10. Periodically review error patterns, including overconfidence, underconfidence, timing errors, weak assumptions, ignored counterevidence, wrong key drivers, poor resolution criteria, and repeated mistakes by forecasting domain. Use those patterns to improve future forecasts. Copy-and-paste prompt Act as a forecasting and calibration analyst. Whenever I make a meaningful prediction, create a forecast record using: CLAIM: PROBABILITY: TIME HORIZON: KEY DRIVERS: DISCONFIRMING SIGNALS: RESOLUTION CRITERIA: Make the prediction specific enough to evaluate later. Require a numeric probability and a defined time horizon. Preserve the original forecast exactly. If new information materially changes the forecast, create a new version rather than rewriting the original. When the forecast resolves, add: OUTCOME: RESULT: THESIS ACCURACY: TIMING ACCURACY: DRIVER ACCURACY: WHAT WAS RIGHT: WHAT WAS WRONG: CALIBRATION REVIEW: LESSON: Periodically review resolved forecasts for: Accuracy by probability band Overconfidence Underconfidence Timing errors Repeated bad assumptions Strongest forecasting domains Weakest forecasting domains Never rewrite history to make an old forecast look better. The objective is not to maximize correct predictions. The objective is to make confidence increasingly match reality.

I'm a British Academy (BAFTA) voting member. Every autumn, the members' screener platform fills up with more than 100 eligible films—major contenders, obscure documentaries, and hidden gems all mixed together. I have a few weeks to decide what deserves my viewing time before I vote. The fun challenge is finding the sleeper nobody has heard of yet; the problem is the sheer volume of clutter I have to sift through. I built a workflow in Claude Cowork that turns the overwhelming list into an ongoing conversation with a curator that knows my taste. I started by inputting my film notes from previous years: what I watched each season, what I loved, what I abandoned, and why. Claude stores this in persistent memory alongside a growing profile of my taste, including my go-to critic, my low tolerance for slow cinema, the kinds of films that reward me, and my rule that a film gets minutes—not acts—to earn my time. Every session starts with this context already loaded. When a new batch of films drops, Claude opens the screener platform in its built-in browser, reads the full slate, and sends research agents to cover every title in parallel. They research the director, cast, runtime, Rotten Tomatoes scores, festival prizes, awards buzz, and whether my favourite critic has reviewed each film. Claude even pulls the transcripts of his YouTube reviews and summarises the verdict. In about 20 minutes, a 37-film batch is triaged into three categories: priority viewing, worth sampling, and skips. Slow starters are flagged so I know which films need a committed evening and which get 10 minutes to prove themselves. As I watch, I feed verdicts back in plain English, such as “gave it ten minutes, too abstract.” Claude updates both the tracker and its model of my taste, so each recommendation round becomes sharper. By voting time, I have a complete, searchable record of everything I watched and what I thought of it, built conversationally throughout the season. Step-by-step: 1. I input my film notes from previous years—everything I watched, loved, and abandoned, along with my reasons. Claude saves them to persistent memory, which every future session loads automatically, and builds a profile of my taste from them. 2. When new films appear on the members' platform, Claude opens it in its built-in browser and reads the full list of titles. 3. Claude launches parallel research agents to cover every title, including the cast, crew, runtime, Rotten Tomatoes scores, festival prizes, awards buzz, and my preferred critic's verdict from YouTube review transcripts. 4. Claude compiles a triage tracker that ranks every film by viewing priority, flags likely sleepers, and warns me about slow starters. 5. As I sample films, I report quick verdicts in plain English. Claude logs them and continuously refines its profile of my taste, so recommendations improve throughout the season. 6. At voting time, I have a complete record of what I watched, what I thought, and why, built conversationally across the season.

I have tried many AI Tools however - I feel the time I Input data and effort into schedulign and resourcing is the problem - I need a Fix or a rubust reliable AI workflow so i can buy my time back. Any suggestions?

The content, business plan, and trajectory is established. Coding and execution is the precise matter that is required. I lack coding skills, and have yet to acquire a proper coder to fit the context.

I write science fiction and use ChatGPT to make sure my stories stay within certain rules. I use Willow Voice AI for dictation and video generators to create proof-of-concept visuals. I also recently used AI to find quick answers within a 40-minute YouTube video. I turned it from watchbait into quick answers. Step-by-step: 1. I use ChatGPT to check that my science-fiction stories stay within certain rules. 2. I use Willow Voice AI to dictate my writing. 3. I use video generators to create proof-of-concept visuals. 4. I use AI to find quick answers within a 40-minute YouTube video. 5. I turn the video from watchbait into quick answers.

I moved to France, where my German hunting license is not accepted. As a resident, I have to pass the French hunting exam to obtain a French license. I downloaded a guide for the exam from various internet sources, along with publicly available literature on the relevant topics. I gave these materials to Perplexity and instructed it to develop a preparation course with logically structured learning units covering French hunting vocabulary, exam topics broken down into detailed subunits, game, hunting law, and more. For each unit, I requested a test with 12 questions combining multiple-choice and free-text formats. I also asked Perplexity to include every mistake in the next unit and continue reviewing those errors until I know the material 100%. Now, every second day when I open my computer, Perplexity presents a new unit aligned with my progress and the errors from previous units. The preparation schedule is optimized for the exam this November, with October reserved for reviewing all topics. Step-by-step: 1. I downloaded an exam guide and publicly available literature on the relevant French hunting topics. 2. I provided these materials to Perplexity. 3. I instructed Perplexity to create a logically structured preparation course covering French hunting vocabulary, detailed exam topics, game, hunting law, and related subjects. 4. I required each learning unit to include a 12-question test with a mix of multiple-choice and free-text questions. 5. I asked Perplexity to carry every mistake into the next unit and continue reviewing it until I know the material 100%. 6. Every second day, I open my computer and complete the new unit generated according to my progress and previous errors. 7. I use the schedule leading up to the exam in November, reserving October for a full review of all topics.

During a period when my medical symptoms suddenly became much worse, the hardest part was not only the symptoms themselves. Pain, dizziness, visual disturbances, brain fog, and acute stress reduced my ability to explain what was happening, make decisions, and keep track of multiple healthcare contacts. That created an awkward problem: the moment I most needed to communicate clearly was often the moment I had the least cognitive capacity to do so. I used ChatGPT as a temporary coordination and communication layer. I kept a symptom diary so I did not have to reconstruct everything from memory. When my symptoms changed, I could compare the new episode with previous days and prepare a concise description. I also used ChatGPT to think through where to seek care. Depending on the severity and type of symptoms, the relevant question might be whether something belonged with my regular GP, an out-of-hours GP service, emergency care, or one of the specialists already involved. Before speaking with a clinician, I asked ChatGPT to help reduce a messy description to a few medically useful points: what changed, when it started, how severe it was, what made it better or worse, which associated symptoms were present, and what had already been investigated. One of the most useful workarounds was extremely simple: if speaking became difficult, I prepared a short note on my phone and showed it to the clinician. At the top, I explained why I was using written communication—for example, that acute stress, autism, pain, dizziness, or brain fog were making speech harder. Underneath, I included my symptoms, timeline, medications, relevant history, and the questions I wanted answered. That mattered because someone arriving alone, visibly anxious, or struggling to speak can easily have difficulty presenting a coherent medical history. The same is true when symptoms reduce concentration, working memory, or language ability. AI did not diagnose the problem. It helped preserve my ability to participate in my own care when some of the abilities normally required to do that were temporarily impaired. During that period, clinicians investigated several possible causes, treated the problems they found, provided medication when needed, and ruled out more serious possibilities. The valuable part of the workflow was not AI replacing a doctor. It was AI helping me reach doctors with a clearer history, better questions, and a communication method I could still use when my normal one was failing. Step-by-step: 1. I kept a symptom diary so I could compare new episodes with previous days instead of relying on memory. 2. I used ChatGPT to help me think through whether to contact my regular GP, an out-of-hours GP service, emergency care, or a specialist already involved, based on the severity and type of symptoms. 3. Before speaking with a clinician, I used ChatGPT to organize what had changed, when it started, how severe it was, what affected it, which associated symptoms were present, and what had already been investigated. 4. When speaking became difficult, I prepared a short note on my phone and showed it to the clinician. 5. I put the reason for using written communication at the top of the note, followed by my symptoms, timeline, medications, relevant history, and questions. 6. I used the clearer history, better questions, and written communication method to remain involved in my care while clinicians investigated possible causes, treated problems they found, provided medication when needed, and ruled out more serious possibilities.