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

The ETHOS™ Framework (Evaluation Through Hierarchical Oversight of Sources) is a multistage forensic audit system designed to transform AI-generated research into “audit-ready” ground truth. Its five-stage lifecycle is designed to ensure technical precision: Step-by-step: 1. EXTRACT (Stage 1): Using the Ground Truth Manifesto and the six-tier Authority Ladder, ETHOS extracts structured tax reports from multiple LLM archetypes: Technical Specialists, Strategic Advisors, and Operational Drafters. This forces their initial findings to follow a strict legal hierarchy. 2. TEST (Stage 2): The Tax Citation Auditor subjects the reports to a three-pass forensic review, testing every citation for existence, pinpoint accuracy, and application fit. Any citation that cannot be verified in a primary repository is immediately downgraded or flagged. 3. HEAL (Stage 3): The Post-Audit Correction Protocol (PACP) repairs the evidence chain by requiring the LLM to resolve flagged citations, replace fabrications with 3–15-word verbatim micro-quotes, and revalidate all “knock-on” effects across downstream computations and thresholds. 4. ORGANIZE (Stage 4): The Human-in-the-Loop (HITL) controller organizes the pre-audit and post-audit artifacts in a consolidated AI sandbox, such as Google Notebook, Claude Cowork, or Perplexity Spaces. This manages the collectively exhaustive data, elevates mutually exclusive advisory angles, and maintains institutional version control. 5. SYNTHESIZE (Stage 5): ETHOS applies MECE principles (Mutually Exclusive, Collectively Exhaustive) and the Weighted Authority Confidence Index (WACI) to adjudicate model conflicts and synthesize a single ground-truth memo. Every load-bearing conclusion is certified for release.

I fed Claude my sweat-test data, and it formulated a DIY high-carb cycling mix tuned to my sweat chemistry. It also scaled the batch to match my available supplies and generated print-ready labels and batch sheets. Step-by-step: 1. I provided Claude with my sweat-test data. 2. I used Claude to formulate a DIY high-carb cycling mix tuned to my sweat chemistry. 3. I had Claude scale the batch to match my available supplies. 4. I had Claude generate print-ready labels and batch sheets.

Post-production for each of my podcast episodes used to be a significant task, even when an episode was audio-only. I’ve now built a workflow with Claude and Descript to automate the production process. I clean up the original recording in Descript, export the transcript to Claude, and run a single command to generate the remaining assets. This includes show notes for Hello Audio, opening and closing scripts written in my voice using anti-AI files to avoid a robotic tone, audio clips and audiograms for social platforms through a custom Claude skill, teaser posts for each audiogram on LinkedIn, and launch-day posts for LinkedIn and Substack, where my audience is. I’m sure there’s a way to streamline the workflow further to include distribution of the posts, audiograms, and episodes. It’s a work in progress 😀 Step-by-step: 1. I clean up the original podcast recording in Descript. 2. I export the transcript from Descript to Claude. 3. I run a single command in Claude to produce show notes for Hello Audio. 4. I generate opening and closing scripts for each episode using my voice and anti-AI files to avoid a robotic tone. 5. I use a custom Claude skill to automate the production of audio clips and audiograms for social platforms. 6. I create teaser posts for each audiogram on LinkedIn. 7. I prepare the main LinkedIn and Substack posts for each episode’s launch day. 8. I’m continuing to look for a way to streamline distribution of the posts, audiograms, and episodes.

I ran a prompt to read and listen to all key notes from companies in the medical device industry over the last year. I used it to identify where attention was being drawn and where companies were investing. This helped me see the trends companies were discussing, investing in, or directing their efforts toward. Step-by-step: 1. I ran a prompt over key notes from medical device companies covering the last year. 2. I used the prompt to identify where companies were directing attention and investment. 3. I reviewed the results to see which trends companies were discussing and prioritizing.

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.

I used Claude Cowork to replace a weekly analysis of closed-end funds for a weekly newsletter. I created a project that uses Claude for Chrome to scrape and download all closed-end pricing information from a CEF website. It adds that information to a weekly dated spreadsheet and calculates changes from the prior week, month, and year. It also updates other data points, including graphs, Top 10 and Bottom 10 rankings, and our own portfolio of funds. Step-by-step: 1. I created a Claude Cowork project for the weekly closed-end fund analysis. 2. I used Claude for Chrome to scrape and download all closed-end pricing information from a CEF website. 3. I added the information to a weekly dated spreadsheet. 4. I calculated changes from the prior week, month, and year. 5. I updated the graphs, Top 10 and Bottom 10 rankings, and our own portfolio of funds. 6. I used the resulting analysis for a weekly newsletter.

Customer events trigger AI workflows that classify requests, automate actions, update systems, and keep teams in sync without manual intervention. Step-by-step: 1. Customer events trigger the AI workflows. 2. The workflows classify requests. 3. They automate actions and update systems. 4. They keep teams in sync without manual intervention.

I’m researching two separate documentary films. For each project, the bot runs three web crawls and one health check every day. Based on my notes, scripts, and other existing initial research, it identifies research domains by theme and media type, favoring audio and images while applying a higher threshold to other documents. Anything scoring eight or higher is logged in Notion and downloaded automatically when possible. The bot cycles through different themes, and the health check adjusts the similarity threshold based on the results. If many items score eight, it may log and download only nines. If fewer qualifying items appear, it may begin downloading sevens. Most items cannot be downloaded because they are inaccessible to the bot, but they are still logged and linked. I review the items in Notion and mark each one according to criteria such as “people only for research” or “reject—permissions required.” It isn’t a full replacement for professional archival research, but I feel it’s getting me 90% of the way there. As an independent filmmaker, this is a huge benefit. Each morning, it sends me a synopsis, and each week, it sends me a list of pre-written emails to send to archives that require human interaction. Step-by-step: 1. I provide the bot with my notes, scripts, and existing initial research for each documentary project. 2. For each project, the bot runs three web crawls and one health check every day. 3. It identifies research domains by theme and media type, with a preference for audio and images and a higher threshold for other documents. 4. It logs items scoring eight or higher in Notion and automatically downloads them when possible. 5. It cycles through different themes and uses the health check to adjust the similarity threshold: it may focus on nines when many eights appear, or begin downloading sevens when fewer qualifying items appear. 6. It logs and links items that cannot be downloaded because they are inaccessible to the bot. 7. I review each item in Notion and mark it according to criteria such as “people only for research” or “reject—permissions required.” 8. Each morning, I receive a synopsis, and each week, I receive pre-written emails for archives that require human interaction.

Claude Cowork has been a huge help in creating growth forecasts for our paid media channels. I just plug in our metrics, tell it what goal I'm trying to achieve, and it's able to create an Excel sheet for me with exactly what I need. This saves me a bunch of time because I can create multiple scenarios just by chatting with Cowork. Step-by-step: 1. I gathered the paid-media metrics and the business goal the forecast needed to model. 2. I gave the inputs to Claude Cowork and asked it to build the forecast directly in Excel. 3. I reviewed the structure, assumptions, and outputs of the generated sheet. 4. I changed the assumptions conversationally to create additional scenarios. 5. I compared the scenarios without rebuilding the spreadsheet model by hand each time.

My fantasy baseball auction draft is around the corner, and I decided to try Claude Cowork for the planning and research efforts this year. I uploaded my league's settings, the players being kept across the league, and my own rambling of strategies and thoughts on my current players. Claude then performed a deep analysis of my current options and their projected values, provided strong recs on who I should prioritize, and gave me a detailed list of draft targets around the league, perfectly tailored to my needs and league format — also scouring the web for tons of articles that saved me the tedious manual searching. Step-by-step: 1. I uploaded the fantasy league settings and the full list of players being kept by other teams. 2. I added my own current players, draft strategy, and rough thoughts about possible approaches. 3. I asked Claude Cowork to analyze the available options and projected player values. 4. I had it search the web for relevant articles and incorporate that research into the recommendations. 5. I turned the result into a tailored list of priorities and draft targets for the auction.