Workflow Hub

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/

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 built a workflow to evaluate whether communication with a legal counseling service was as slow and incomplete as it felt. Email was my primary—and necessary—communication channel with them. I had become increasingly dissatisfied with delayed replies, partial answers, and questions that seemed to remain unresolved. Rather than relying only on memory or frustration, I asked GPT to review the relevant Gmail correspondence and turn it into a structured communication inventory. The workflow identified my outgoing questions, their replies, and whether each question had been fully answered, partially answered, or left open. From that inventory, we could calculate concrete indicators such as the median response time, the longest delay between a question and a substantive reply, and the number of questions that remained unresolved or were only partly addressed. This was useful because long email threads can create a distorted sense of what happened. A few frustrating exchanges can dominate memory, while other delays or omissions disappear into dozens of messages. Structuring the correspondence made the pattern measurable. The analysis was not meant to decide whether the counselors were “good” or “bad.” It was meant to answer narrower questions: How quickly were questions usually answered? Which ones were not answered? Were replies resolving the issues raised, or only responding to part of them? Afterward, we created a clear list of the questions that were still open. I used that list as a set of dossier questions when moving the case to another counselor, turning the analysis into practical continuity rather than just a complaint about the past. In simple terms: Gmail correspondence → question-and-response inventory → response-time and completeness analysis → unresolved-question list → handover to another counselor What I liked about this workflow is that it turned a vague feeling that “this communication is not working” into a documented overview I could actually use. Step-by-step: 1. I gathered the relevant Gmail correspondence with the legal counseling service. 2. I asked GPT to identify my outgoing questions, the counselors’ replies, and the status of each question. 3. I classified each question as fully answered, partially answered, or left open. 4. I calculated indicators including the median response time, the longest delay before a substantive reply, and the number of unresolved or partly addressed questions. 5. I created a clear list of the questions that remained open. 6. I used that list as dossier questions when handing the case over to another counselor.

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.

When medical care, psychosocial support, and administrative follow-up are spread across services, emails, documents, and people over many years, there can be plenty of information but very little overview. A new provider sees snapshots, old decisions hide in email threads, and referrals resurface months later. Reconstructing the full story from memory every time requires almost a second brain. So I built a living chronological timeline. I did not want a summary of what my situation was “more or less.” I wanted: `date → event → action taken` For example: `14 March 2026 — Symptoms discussed with service X — Service refers me to Y; appointment requested.` This shows not only what happened, but what followed. My timeline runs from 2009 to the present and is divided into five documents covering meaningful periods. A new document begins when a new phase in life or support begins. Older periods stay stable, while almost all active maintenance happens in the latest document. I reopen historical files mainly when a missing record resurfaces. Step-by-step: 1. I collect existing traces, including emails, appointments, referrals, medical or administrative documents, formal decisions, and earlier notes. A sent email is often only half an event, so I also search for replies and follow-up. 2. I search by trajectory rather than by one name. I use names, spelling variants, organisations, domains, senders, recipients, subject words, and attachment terms. 3. I read the full conversation. A search result is not yet a timeline item, so I establish what happened, when it happened, who was involved, and what action or response followed. 4. I separate evidence levels. I distinguish between my own report at the time, a response or confirmation, an official decision or document, and an event that seems real but still lacks confirming evidence. I do not replace a missing document with an assumption; the absence itself becomes part of the record. 5. I track people and organisations separately. “Contact with organisation X” can hide that different people suggested, revisited, or formally communicated different things. 6. Before adding a new event, I compare it with the existing timeline. It may add information by filling a gap, replace an incomplete entry, clarify an existing event, or mark a missing record while preserving uncertainty. This prevents duplicate versions of the same event. 7. For substantial historical work, I first create a temporary review document using `date — event — action taken`. It can contain open issues, missing documents, and uncertainties. Only after review do I update the main timeline. For ordinary new events, I skip this step when the source and date are clear. 8. I make uncertainty visible by grouping research notes into “Clearly found,” “Possible identity confusion,” and “Not found or insufficiently documented.” 9. I maintain the living timeline using the structure `year → month → chronological events`. Older information is preserved, duplicates are merged, uncertainties stay visible, and open trajectories remain open. In practice, the five documents behave like version control: the first four are mostly archive, while the fifth is alive. 10. I reuse the timeline for thematic analysis. Chronology is the factual foundation, but events can also be regrouped to reveal patterns in functioning, work capacity, transport, medical developments, administrative burden, communication needs, and realistic conditions for participation. Two workflows emerged: - Historical reconstruction: collect sources → reconstruct trajectory → determine evidence status → review → update the correct historical period - Ongoing follow-up: new event → verify source → record date and action → add to the active document Most records are organised around institutions. A GP sees one part, a psychologist another, and an agency only its own procedure. Emails are chronological within a mailbox, but not across a life. A personal timeline turns that model around. The person becomes the organising axis, not the institution. That lets administratively separate events appear next to each other in time, revealing patterns such as repeated referrals, waiting times, administrative burden, or support disappearing when the need for it increases. The workflow in one line is: `Collect sources → reconstruct trajectories → connect events to actions → distinguish evidence status → compare → review → integrate → maintain → analyse thematically.` The result is not a perfect record, but a steadily improving map of what actually happened, with mainly the newest edge continuing to grow while the past stays calmly in place.

After about 18 months of building software with AI, I realized that reliability wasn't primarily a model problem. Bigger context windows and more clever prompts didn't fix it. What did help was treating the AI like a developer joining an existing team instead of like a chatbot. Real developers don't work from memory. They inspect production, read the documentation, check the tickets, and use proven tools. I built an environment that lets the AI do the same. The workflow is tool-agnostic, so it can be rebuilt with whatever AI client and stack you already use. Step-by-step: 1. I gave the AI a persistent task and history store that it can read from and write to. This is the core of the workflow. Mine lives behind an MCP tool, but any queryable store can work. Every architectural decision, blocker, and progress note gets written there instead of being left in the chat. 2. I open every session with a stand-up. Before writing a single line of code, the AI pulls what was in progress, what's blocked, what changed since the last session, and which architectural decisions still hold. About 30 seconds later, we're both looking at the same project. Then we build. 3. I exposed real operations as MCP tools instead of relying on "write code" prompts. I wrapped specific, tested actions—such as creating a page, defining a data model, wiring an integration, and running a migration—as tools. The AI composes these known-good building blocks into larger solutions instead of regenerating infrastructure every session. I call this wave coding, and it's the biggest reason the output stays consistent. 4. I made verification a rule: before touching anything, the AI reads the live database, API state, logs, and files. It checks ground truth first instead of making assumptions. 5. I made the chat disposable and the log canonical. If it isn't logged, it didn't happen. The task store is the single source of truth, not the conversation. The payoff is that I can stop halfway through a feature, close my laptop, and come back days later. The AI reconstructs the project from its own history, so I don't spend 20 minutes re-explaining it. Full disclosure: I built this into my own platform, WebsitePublisher.ai, which currently has 43 MCP tools and 105 integration building blocks. It's delivered as an add-on that plugs into the AI client I already use over MCP, so there's no new app to learn. Nothing here is locked to that platform, though: the workflow itself works with any MCP client and any store the AI can query. I'm curious whether anyone else is running their AI this way or solving the amnesia problem from a different angle.

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

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 wanted to learn how to build websites and sell them, but I didn’t know where to start. I used AI—specifically DeepSeek—to help me plan a roadmap. Because I already had experience prompting large language models to get the results I wanted, I asked DeepSeek which areas of knowledge I would need for this path. I also asked it to prioritize each area using statistics and facts. I reviewed the areas I didn’t know and prioritized them, then told the AI that I needed free resources only. I asked it to rank the topics based on what I didn’t know or understood the least. Finally, I asked it to create a Markdown file with all the resources formatted as checklists and imported the file into Notion. Now I have a plan I’m following instead of a “someday I’ll do this, hopefully” idea. Step-by-step: 1. I explained to DeepSeek that I wanted to learn how to build and sell websites but didn’t know where to begin. 2. I asked it to identify the areas of knowledge I would need for that path. 3. I asked it to prioritize those areas using statistics and facts. 4. I reviewed the topics I knew the least about and used that information to prioritize them. 5. I specified that I wanted free learning resources only. 6. I asked DeepSeek to create a Markdown file listing the resources as checklists. 7. I imported the Markdown file into Notion and started following the resulting plan.

I’ve been using the Awish app I built less as an automation builder and more as a way to solve specific business problems people bring me. One hotel client, Aurelia Bay Hotel, had an interesting marketing problem. They could see travel trends across search, Instagram, YouTube, website traffic, and ads, but connecting those signals early enough to spot a real campaign or guest-experience opportunity was difficult. I built an automation for them with Awish and gave it to them to test. Step-by-step: 1. I opened the Awish chat and wrote: “For Aurelia Bay Hotel, monitor Google Trends, YouTube, Instagram, Google Analytics, and Google Ads every day. Find rising interests around Dubai travel, staycations, family trips, wellness, dining, events, and hotel experiences. Cross-check those trends with social engagement, website behavior, and campaign performance. Rank the strongest opportunities, send them to the marketing team in Microsoft Teams for approval, and create a campaign or guest-experience opportunity brief in SharePoint for anything they approve.” 2. Awish understood what I wanted, planned the complete workflow, and selected the apps required for each step. 3. I reviewed the plan, connected the client’s accounts, and approved it. 4. Awish added Microsoft Teams as the human approval step and SharePoint for the final opportunity briefs. 5. Once everything was connected, Awish built the workflow and started running it daily. 6. It now cross-checks trend growth, social engagement, website behavior, and ad performance. When it finds a strong opportunity, the marketing team gets the evidence in Teams. If they approve it, Awish creates the full campaign or guest-experience brief in SharePoint. The useful part is that a trend isn’t treated as an opportunity just because it is growing on one platform. Awish checks whether the same signal is appearing across the business before recommending action. Do you have any time-consuming, repetitive tasks or problematic aspects in your job? I would be happy to develop an automation solution for you as well.

I built a suite of teaching tools that work independently and together. Chalkline supports maths, while Penline supports literacy. Both tools provide quick access to the New Zealand curriculum for planning and feed information directly into my planning utility, Planline, making teacher planning faster. Planline integrates with Google Drive and is set up with Stripe billing for subscriptions. The suite also includes Compass World News, a news aggregator with a freemium model and a pro unlock. The apps are designed without user tracking. Findaroo is a freemium word-find game with ads. Slashkit helps Minecraft players quickly create commands to use in games. Everything is built into my website, www.danielsoutham.co.nz, which is hosted on Cloudflare. I push updates and changes through GitHub, so I can make changes—big or small—from anywhere, on any device. Changes are then pushed and merged in one prompt. Step-by-step: 1. I built Chalkline for maths and Penline for literacy, with each tool able to work independently. 2. I connected both tools to the New Zealand curriculum so teachers can quickly access it for planning. 3. I connected Chalkline and Penline to Planline so they can feed information into the planning utility. 4. I integrated Planline with Google Drive and set up Stripe billing for subscriptions. 5. I added Compass World News as a freemium news aggregator with a pro unlock and no user tracking. 6. I added Findaroo as a freemium word-find game supported by ads. 7. I built Slashkit to help Minecraft players quickly create commands for use in games. 8. I brought all of the apps together on www.danielsoutham.co.nz and hosted the website on Cloudflare. 9. I use GitHub to push and merge updates, allowing me to make changes from anywhere, on any device, in one prompt.

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 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 recently learned that I have severe osteoporosis. Two doctors highly recommended Evenity, which is prescribed and insurance-approved only for people at severe risk of fracture, so I knew the situation was serious. The decision was difficult because Evenity carries an increased risk of heart attack and stroke. Both conditions run in my immediate family, and one of my arteries has 75% plaque buildup. Ultimately, we agreed that my risk of a life-altering fracture was much greater than my risk of a heart attack or stroke. My father died six weeks after suffering a life-altering fracture, while my mother survived two heart attacks and a stroke, and my brother died from his first heart attack at age 60. That made it even more important to follow recommendations for both heart and bone health, even though the goals for each can be different. Monitoring everything myself would have been overwhelming, so I created a project called "Daily Meals" and prompted Chat to create a chart that tracks my daily intake of protein, carbohydrates, fiber, healthy and unhealthy fats, calcium, cholesterol, and other selected nutrients, along with a goal for each one. I enter everything I eat throughout the day. The chart maintains a running total and displays my goals underneath. When I am about halfway through my calorie goals, Chat recommends foods for the rest of the day to help me stay on target. Within a week, Chat had learned my go-to foods, and I also told it about other foods I like. There is no harsh judgment when I include ice cream. I also added pictures of the labels for the supplements I take each day. In addition to tracking my intake, Chat advises me about combinations that may help or hinder absorption. One important example for me is that vitamin D, which must be taken with fat, helps with calcium absorption, while vitamin K2 activates proteins that help carry calcium to my bones instead of my arteries. Chat also provides guidance about medications. When I was prescribed an antibiotic, I learned that taking it with calcium could greatly reduce the medication's absorption, so I adjusted what I ate accordingly. There is much more benefit than I can fit here. This project may literally be a lifesaver for me. Step-by-step: 1. I created a project called "Daily Meals." 2. I prompted Chat to create a chart for tracking protein, carbohydrates, fiber, healthy and unhealthy fats, calcium, cholesterol, other selected nutrients, and goals for each one. 3. I added pictures of the labels for the supplements I take each day. 4. I enter everything I eat throughout the day so the chart can maintain running totals. 5. I review the totals against my goals, and when I am about halfway through my calorie goals, I ask Chat to recommend foods for the rest of the day. 6. I told Chat about my go-to foods and other foods I like so its recommendations could reflect my preferences, including occasional ice cream. 7. I use Chat's guidance about nutrient combinations, including vitamin D with fat for calcium absorption and vitamin K2's role in helping carry calcium to my bones instead of my arteries. 8. When I was prescribed an antibiotic, I used Chat's medication guidance to learn that taking it with calcium could reduce the medication's absorption, and I adjusted my meals accordingly.

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.

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.

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 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.

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.