A working preview makes it tempting to keep asking for features. But the first screen tells you little about who controls the database, how the application is structured, or what the next prompt might change. I developed this workflow by putting my best-practices guides to work on a client project, then separating the reusable process from that project’s architecture. This workflow is for AI app-building platforms, often called vibe-coding platforms, where you describe an application and the platform generates and runs a working prototype. It focuses on keeping control of the code, repository, backend, and platform connections. It is not a general guide to coding agents or AI-assisted editors. Anyone who has watched a code generator slowly degrade a clean codebase knows why the starting conditions matter. Before asking for features, establish what you own, what the tool may change, and how you will check its work. Step-by-step: 1. Set ownership before the first build prompt. Decide what the application needs and who controls it. If it needs a new database or backend, provision it in an account you control before asking the builder to create the app. An existing API is another option, not a requirement; some prototypes need neither. Confirm the repository destination, integration permissions, and recovery access. Keep production behind a reviewed release process. 2. Give each tool readable rules. Establish one authoritative set of architecture, coding, and design standards. Identify which files each tool may change and which it may only read. Naming a rules file in a prompt does nothing if the tool cannot access it. Assign responsibility for data, authentication, application logic, deployment, and recovery. One person can hold several roles, but a UI task does not grant permission to redesign the backend. 3. Build the framework before the features. Use the opening prompt to establish the framework, runtime, routes, layout, and state ownership. Ask for empty page shells first. Check that navigation uses real routes and that shared elements have a defined home. Keep design values in one designated place. Any temporary authentication placeholder must be clearly labeled and isolated from protected data. Real users require real authentication and authorization. 4. Inspect and preserve the foundation. Read the generated files and inspect the running scaffold. Check for unrequested services, dependencies, and structural changes. A green build alone does not tell you whether the tool followed your instructions. Once accepted, protect the foundation files from routine UI prompts. Record the accepted commit and preserve a recovery copy beyond the integration’s ability to modify or delete. 5. Set up a prompt factory. A prompt factory is an assistant configured to turn a plain-language request into a bounded implementation prompt. Give it the project rules, file map, technical references, and current capabilities. It checks whether the requested behavior is supported before producing instructions. If something is missing, it prepares a prerequisite request for the responsible owner instead of inventing data or behavior to make the screen look finished. Each prompt names the tool, permitted files, protected files, applicable standards, relevant data and interfaces, exact change, what must be preserved, and observable checks. The factory prepares instructions; it does not approve architecture or release changes. 6. Build one governed feature. Where data is involved, establish correct data behavior first. Follow with a separate placement and styling task. Inspect the changes and test the affected behavior. Apply the One Fix Rule: one repair prompt, one attempt. If it fails, the generator is done with that file. Move the repair to manual maintenance rather than feeding another round of guesses into the codebase. After acceptance, save the next recovery point and update the working rules. Preserve the reason behind each rule so a later cleanup does not remove the safeguard. The point is to make the next feature less likely to undo the work you already accepted. Your database, where needed. Your code. Your standards. You control the tether. Part 2 will cover cutover: leaving the development platform with a controlled release, verification, and a recovery plan. Download The AI Builder Playbook on GitHub: https://github.com/wildeyeai/ai-builder-playbook

I’m a nerd for deals, so I built a Personal Credit Card Optimizer in ChatGPT. I wanted a simpler way to figure out which store and card would save me the most money on any item I want to purchase. The workflow maintains a database of my credit and debit cards—recording their series, but not their exact numbers—along with their rewards, fees, and benefits. Whenever I want to buy something, I add a product link. It scans retailers for better prices, checks current bank offers against my specific cards, and compares instant discounts, cashback, reward points, and other benefits to determine where I should buy and which card will provide the most value. It’s now an ongoing skill in my ChatGPT project. No more manually checking a dozen bank offers or discovering at checkout that my card isn’t eligible. Step-by-step: 1. I add my credit and debit cards to a database by recording their series, rewards, fees, and benefits without entering their exact numbers. 2. When I want to purchase something, I provide a product link. 3. The workflow scans retailers for better prices on the product. 4. It checks current bank offers against my specific cards. 5. It compares instant discounts, cashback, reward points, and other benefits to determine the best retailer and card combination.

I built a custom web app that uses chance to combine random images and texts into new, unplanned pairings. It recreates a Dadaist technique I use often when making photobooks, which I previously did manually with physical prints. I used Replit to create a digital version of the game. It was easy to connect the app to Project Gutenberg for random texts and the Library of Congress photography archive for images. More importantly, I made it possible for users to work with their own image and text archives. So far, it has produced many new and interesting results, and other artists have used it too. Step-by-step: 1. I identified the manual process I use when making photobooks: combining printed images and texts by chance. 2. I used Replit to build a digital version of this process as a web app. 3. I connected the app to Project Gutenberg to pull random texts. 4. I connected it to the Library of Congress photography archive to pull images. 5. I allowed users to work with their own image and text archives. 6. I used the app to create new pairings and shared it with other artists, who used it as well.

I used a simple workflow to save several hundred dollars on veterinary bills while sitting in a veterinary urgent care clinic. This approach could also apply to many other purchases or services where I’m not an expert. I had already been chatting with ChatGPT about my pet’s symptoms and their likely causes. After I arrived at urgent care, I consulted the doctor about the likely diagnosis and the tests and treatment we should pursue. The clinic assistant then brought me a printed, itemized list of all the charges for the proposed plan. I resumed the ChatGPT conversation by dictating what the doctor had told me, photographing both pages of the charge list, and uploading them. I asked whether any charges were very likely unnecessary given the circumstances. ChatGPT identified four of the 24 charges and explained why they appeared to have very limited value. I crossed those four items off the list, handed it back to the assistant, and said, “I don’t think these are necessary at this point.” I could tell from the assistant’s facial expression that no one had done this before. When the doctor returned, I could tell I had caught her off guard. She agreed that two of the four tests likely offered no benefit and explained why we should keep the other two. At that point, I decided to trust the doctor more than the AI agent—perhaps partly to be polite, since I could tell her justification for keeping the tests was weak, although the cost wasn’t significant. Step-by-step: 1. I described my pet’s symptoms and their likely causes to ChatGPT before visiting the clinic. 2. I consulted the doctor about the likely diagnosis and the tests and treatment we should pursue. 3. I photographed the clinic’s two-page, itemized list of 24 charges and uploaded it to the existing ChatGPT conversation. 4. I dictated what the doctor had told me and asked ChatGPT whether any charges were very likely unnecessary in the circumstances. 5. I reviewed ChatGPT’s explanation of the four charges it identified as having very limited value. 6. I crossed those four items off the list and discussed them with the clinic assistant and doctor. 7. I kept two tests after the doctor explained why they should remain, while declining the other two. The process saved me $600.

I'm planning a housewarming party for about 70 people: 60 adults and 10 children. I knew I wanted to serve a large grazing board, along with a couple of big buckets of ice filled with canned beer, coolers, sparkling water, and other drinks. I told Claude about the party and asked it to create a shopping list based on the number of attendees. Claude produced a cohesive list with six cheeses and approximate quantities for each one. It did the same for the cured meats, crackers, bread, fruit, nuts, jams, and pickled items. It also suggested beverages, including a ratio of beer to coolers and nonalcoholic options. The list included juices and non-caffeinated sodas for the kids, along with a template showing how to lay out the grazing table. This was not a complex use case, but it was very helpful. Step-by-step: 1. I estimated the guest list at about 70 people: 60 adults and 10 children. 2. I described my plan to serve a large grazing board and drinks kept cold in a couple of big buckets of ice. 3. I asked Claude to create a shopping list based on the number of attendees. 4. I used Claude's recommendations for six cheeses, cured meats, crackers, bread, fruit, nuts, jams, and pickled items, including approximate quantities. 5. I reviewed its beverage suggestions, including the beer-to-cooler ratio, sparkling water, juices, and non-caffeinated sodas for the children. 6. I used the layout template to plan how to arrange the grazing table.

In my ongoing mission to go paperless, I created a web app that runs on tablets and replaces paper sign-in sheets. The admin console gives HR instant visibility and detailed reporting on employee and guest attendance across all our branches from a single pane of glass. In Phase 2, I’m expanding the app to eliminate even more paperwork by allowing employees and managers to request, approve, and manage PTO. Department calendars show everyone’s PTO balance and minimum coverage requirements. Step-by-step: 1. I created a web app that runs on tablets to replace paper sign-in sheets. 2. I added an admin console so HR can view and report on employee and guest attendance across all branches. 3. In Phase 2, I expanded the app to support employee and manager PTO requests, approvals, and management. 4. I added department calendars showing PTO balances and minimum coverage requirements.

I built a custom news agent that skips the Google News and Apple News walled gardens. Eight prompts turn Claude into a personal news editor that reads my trusted RSS feeds, scores every story with a decision model, and delivers a clean daily page for about a dime a month. Each week, pulling two or three good stories for my newsletter digest meant searching multiple sites by hand—hours of clicking and scrolling for a handful of usable links. RSS feeds already deliver that content; the missing piece was a judgment layer that could separate worthwhile stories from noise without the cost or latency of running everything through a full LLM. I used Claude Cowork, Jev from TypeSafe AI, Vercel AI Gateway, RSS feeds, Python, and SQLite. Jev is a decision model rather than a chatbot: it returns a probability and confidence score instead of prose, does not hallucinate facts, and scores a story in a fraction of a second. That makes an automated daily judgment call inexpensive enough to run continuously. Step-by-step: 1. I set up a Claude project to hold the scripts, taste guide, database, and page. 2. I defined the goal and sections, then had Claude interview me to create a short “taste guide” describing what counts as a good story. 3. I found and live-tested the RSS feed for each trusted source instead of guessing feed URLs. 4. I fetched all working feeds into a deduplicated SQLite database and logged failures. 5. I used Jev through Vercel AI Gateway to score every story: first filtering ads and promotions, then ranking stories by section against my taste guide. 6. I selected the winners for each section, with Jev identifying near-duplicate stories so they would not appear twice. 7. I generated one-line summaries and fact-checked them against the source so nothing was invented. 8. I rendered a simple HTML page and scheduled the entire workflow to run every morning. A few details matter. I used Cowork rather than a plain chat because several steps require Claude to work with files, run code, and access the network. I also created a Vercel account and AI Gateway API key manually before the scoring step. Finally, I saved everything to the Claude project instead of a local folder, which allows the morning run to happen in the cloud on its own schedule. Scoring costs roughly $0.10 per month with Jev, compared with a few dollars for a full LLM doing the same job. The workflow turns a two-hour weekly slog into a page that is ready every morning, with each link going directly to the original publisher rather than a Google or Apple aggregator. Full build walkthrough: onabetternote.substack.com/p/build-your-own-news-agent-with-claude — the Substack post includes the exact eight prompts to copy and paste, plus more detail on why a model like Jev matters for cost containment as agents become routine.

Subfox Industrial builds custom paperless shop-floor systems for specialist manufacturers that need accuracy, traceability and proof without the paperwork. Instead of a broad software rollout, we start with one workstation and prove it works before we scale. This is for manufacturers who want that kind of control over their floor. Here is how we approach it: 1. We map the real task, the checks and the decisions people make at that station. 2. We configure the workstation around that process. 3. We prove it on the floor. 4. Once it works, we scale to other workstations. Our workstations cover cutting, CNC machining, molding, quality control, maintenance and other process steps. They capture measurements and evidence as the work is done. Where it earns its place, AI adds extra checks and anomaly flags, and the customer keeps control of their data. An IRIS-certified rail parts factory runs on Subfox. The result is that measurements and evidence are captured as the work happens, not reconstructed afterward.

I built a backend operations system for my husband’s general contracting business. It manages new leads, bids and estimates, in-progress jobs, receipts, expense tracking, job photos, invoicing, and other functions he needs—all in one app built with ChatGPT and Base44. I rolled it out in phases. Phase one focused on tracking jobs and their status, phase two added financials, and phase three introduced executive functions. Phase four will cover marketing, although he does not need that right now because he is solidly booked for months. Step-by-step: 1. I built an all-in-one backend operations app using ChatGPT and Base44. 2. In phase one, I added tracking for jobs and their current status. 3. In phase two, I implemented financial functions, including receipts and expense tracking. 4. In phase three, I added executive functions along with other operational features such as leads, bids and estimates, job photos, and invoicing. 5. I planned marketing features for phase four, but postponed them because the business is solidly booked for months.

I’m Steven Alber, founder of ARENOMICS Institute (https://arenomics.institute), an independent research initiative exploring how autonomous AI agents can operate within accountable economic and institutional systems. One of our central research questions is simple: Who gives an AI agent the authority to act? I use ChatGPT and Claude as research and development tools to investigate this question through a structured workflow. 1. I identify an institutional problem, such as how an autonomous agent receives permission to make decisions or execute actions on behalf of a person or organization. 2. I use ChatGPT to examine relevant research, technical standards, and existing approaches to agent identity, authorization, delegation, and governance. 3. I develop conceptual frameworks that distinguish an agent’s technical identity from the authority it receives and the specific mandate under which it operates. 4. I use Claude to help structure the research into technical explanations, institutional models, educational materials, and website content. 5. I compare the models’ outputs, challenge assumptions, examine weaknesses, and refine the proposed architecture before publication. This research direction is part of what I call Mandate Engineering: investigating how human or organizational intentions can be translated into explicit, limited, and accountable authority for autonomous agents. The institute is still developing. My goal is not simply to produce more AI-generated content, but to explore practical and scientifically credible approaches to governing increasingly autonomous intelligence.

My partner and I were tired parents trying to help our child sleep better. We had spent hundreds of euros on expert services and courses, but because every child is different, we still hadn't found an approach that worked consistently. For months, we had talked about trying to improve her sleep. She was waking us up multiple times each night, so we used Gemini to develop a plan with stages. In the first stage, we helped her start sleeping in her own room, which she achieved within a week. The second stage focused on getting her to sleep in her bed for the whole night, and we saw great success after the first night. The game changer was having immediate help when things didn't go as planned. At 2 a.m., I described situations such as my child lying on the floor and refusing to move, asking me to stay, wanting to cuddle or be carried, waking up her sibling, or coming back to our room again. Gemini adjusted the plan and told my tired brain what to do next. My child came back from her room 10 times, and each time I described the situation to Gemini and received practical advice. She eventually slept through the night and woke up in the morning feeling proud and happy. To me, that showed that the techniques Gemini suggested had helped create a safe space for sleep. Step-by-step: 1. I described our child's sleep challenges and the approaches we had already tried, including expert services and courses. 2. I asked Gemini to develop a staged plan tailored to her individual needs. 3. I followed the first stage until she was sleeping in her own room, which took one week. 4. I moved on to the second stage: helping her sleep in her bed for the entire night. 5. When unexpected situations came up during the night, I described them to Gemini in real time. 6. I followed the adjusted advice each time she got out of bed, including when she returned 10 times. 7. I continued until she slept through the night and woke up proud and happy.

Midlifecurious is a newsletter for women navigating midlife—honest, funny, and allergic to being talked down to. Its Sunday issue, the Midlife Missive, is a roundup covering health, wellness, money, beauty, and family. My sister, Claire, edits it; I build the machine behind it. That machine is Missive, a five-part publishing intelligence system that runs the newsletter as one closed loop: scan → triage → publish → measure → remember. It monitors Reddit, search trends, and RSS to identify what midlife women are paying attention to before those topics reach our feeds. Discovery pulls in those sources, ranks every feed using a click-rate-based quality score, and lets Claire triage articles into the week’s issue. Curation composes Sunday’s newsletter and drafts the introduction in her voice. Performance reads the Mailchimp results back into the system and feeds them into the rankings, so strong sources rise and weak ones fall over time. Underneath all four stages is Memory: a vector-searchable corpus of every article, save, rejection, and the reasoning behind each decision. Memory is the real spine of the system. It lets Missive ask editorial questions such as “Have we covered this before?” and “Is this source still earning its slot?” instead of requiring one person to hold everything in her head. We’re a two-person operation: I build with Claude Code, and Claire edits. The system runs on one database for under $25 a month. I built it because the alternative was Claire drowning in a Feedly-and-spreadsheet routine that discarded everything as soon as an issue shipped. We had no record of what we had run and no feedback on what actually landed. My bet is that the corpus is the moat. Claire’s editorial taste—every save, rejection, and “cornerstone” stamp, with the reasoning stored alongside the decision—is a training set no one else has. A system that remembers turns her job from synthesizer into judge. Missive is deliberately internal-only: no SaaS and no customers, ever. That frees me to build for our exact workflow instead of a hypothetical buyer, and to build for 2028 instead of this quarter. The near-term payoff is a calmer Sunday. The long-term goal is a proprietary editorial-intelligence layer we could never buy off the shelf—the foundation for the research and audience products that come next. Step-by-step: 1. I monitor Reddit, search trends, and RSS for topics that midlife women are paying attention to. 2. I pull those sources into Missive and rank each feed using a click-rate-based quality score. 3. Claire triages the ranked articles into the week’s Midlife Missive. 4. Missive composes Sunday’s newsletter and drafts the introduction in Claire’s voice. 5. I import the Mailchimp results so the system can update source rankings based on performance. 6. Missive stores every article, save, rejection, “cornerstone” stamp, and the reasoning behind each decision in a vector-searchable corpus. 7. We use that memory to check whether a topic has already been covered and whether a source is still earning its place. 8. I build and maintain the internal system with Claude Code, while Claire handles editing, using one database that costs under $25 a month.

Sometimes AI produces an image you love without your having asked for that exact result. The colours work, the texture feels right, and the atmosphere is exactly what you wanted but could not quite describe. Before moving on, use that image to develop a reusable prompt. Step-by-step: 1. Show the image you are happy with to an AI tool and ask: “How would you describe the visual style of this image? Pay attention to colour, texture, lighting, shapes, composition, detail and atmosphere. Separate the style from the specific subject.” This helps turn “I love this” into something you can name. You are asking for a description of the visible result, not the exact process that originally produced it. 2. Read the description and compare it with the image. Check whether the AI noticed the qualities you love or focused on something incidental. Clarify ambiguous terms—for example, whether “soft” means gentle lighting, blurred edges, or muted colours. Correct the description where needed. You might write: “The uneven shapes and paper texture matter. The pastel palette does not. I want to keep the slightly strange atmosphere without making everything cute.” Your response turns a general description into a record of your taste. 3. Ask: “Write a reusable image prompt based on this description. Keep the visual qualities we identified, but make the subject replaceable. Distinguish essential features from optional ones.” The prompt should describe what makes the result useful to you rather than simply retell what is pictured. A woodland scene might contain the style you love, but that does not mean every future image needs a forest. 4. Apply the prompt to another source image or a different subject. This is the useful test: can the prompt carry the qualities you wanted into new material? A second version of almost the same scene may hide weaknesses in the prompt. A different subject makes them easier to see. 5. Compare the new result against your goal. Ask yourself: - Does this new result have the qualities I loved? - Does the style suit the new subject? - Did the prompt preserve what mattered in the new source? - Did it reproduce incidental details from the first image? - Would I actually use this result? A reusable prompt should transfer the visual direction while giving the new image room to remain itself. 6. If the result misses the mark, identify the specific difference and refine the prompt. For example: - Too smooth? Name the texture. - Too cute? Describe the shapes and expressions more precisely. - Too realistic? Clarify the degree of stylization. - Too similar to the first scene? Remove subject-specific details. Test again when those changes matter. Save the prompt alongside the original result and a successful test image. Note the tool or model used, since the same wording can behave differently elsewhere. One successful test is encouraging, but several varied tests give you a clearer sense of where the prompt works. An unexpected result can help you discover a preference you did not yet have words for. Describe it, decide what matters, turn those choices into instructions, and test whether they travel. You do not need to know the perfect prompt before making something you love. Sometimes the image comes first, and the language follows.

My basement radon fan was pulling outside air down an outdoor stairwell floor drain, which weakened the suction under the slab. I didn't know what part would fix it, so I worked through the problem with my AI assistant, Grok Bot. At first, I asked for "a drain plug that lets water through but keeps air out," and it suggested general waterless trap seals. Once I explained that the drain runs under the slab to the radon fan, it changed its answer to a part made for radon systems: a retrofit floor drain seal with a weighted valve that opens for water and stays shut against the fan's suction. I sent photos of the drain with a tape measure in the shot. Grok Bot asked about the pipe size, the bowl width, and how far the pipe drops straight down, then confirmed that the seal would fit my 2-inch pipe. It compared three suppliers and helped me complete the checkout. We passed control of the screen back and forth to fill in the forms, and it showed me the full total before anything was charged. Apple Pay didn't work from its computer, so we switched to PayPal. I signed in and approved the payment myself. The part cost about $30, or under $50 with shipping and tax, and it arrived within a week. Afterward, I had Grok Bot turn the whole exchange into a slide deck containing the photos, its questions, my prompts, and the checkout back-and-forth. I used that deck to train my facilities leadership team. My point was that you don't need to be a tech person to do this: take a picture, explain the problem the way you would to a coworker, answer the assistant's questions, and stay in charge of anything that costs money. Step-by-step: 1. Describe the problem in plain language, including why it matters—in this case, the radon fan pulling air through the drain. 2. Send photos with a tape measure in the shot for sizing. 3. Answer the assistant's follow-up questions instead of guessing at part numbers. 4. Ask it to compare suppliers with links and prices. 5. Let it fill in the checkout, but review the total and approve the payment yourself. 6. Have it turn the conversation into a slide deck to train others. My first description was too vague and produced a generic answer, so I learned to provide the full context up front. Payment methods that depend on your phone, such as Apple Pay, may not work when the assistant is checking out on its own computer. Since this drain is outdoors, check the valve after hard freezes and leaf fall.

As an agency, we have to report the work we do for our clients and how efficient it is. Building these presentations by hand is very time consuming and boring, and there is little value in making them. At Le Trefle à 5 Feuilles we decided to automate this recurring task. Before, it took about 3 hours to gather every stats report, make the presentation available to the client, and interpret the stats and recommend further actions. I keep a human in the loop, because someone has to read the report before it is sent. Since we work in Google Workspace, I built the workflow with several Gemini Gems: 1. Google Apps Script watches one folder on Google Drive and detects when a new statistics report is posted. 2. The first Gem decodes the report and inserts the variables into it. 3. The second Gem interprets and sums up all the statistics. 4. The third Gem merges those statistics into the template the workflow calculated. 5. I review the finished presentation before sending it to the client. It now takes only 3 minutes to produce the report, so the consultant can focus on the real value: their analysis of the campaign.

I built a job-offer net-net calculator to determine what a proposed job is actually worth to the employee’s household after taxes, employment-related expenses, benefit changes, commuting costs, and the economic value of commuting time. Gross salary should not be treated as household value. The calculator should interview me first and ask only for information that materially affects the calculation. If I do not know a number, it should identify it as an estimate and use a clearly labeled reasonable placeholder only with my permission. Step-by-step: 1. Collect the proposed annual gross salary. 2. Collect the employee’s state and locality, tax filing status, and other household taxable income when needed to estimate the incremental federal tax burden accurately. 3. Record the work arrangement: fully remote, hybrid, or on-site. 4. Record the number of commuting days per week and working weeks per year. 5. Collect the home location and job location, or the known one-way mileage. 6. Collect the vehicle make, model, year, drivetrain, and approximate MPG when available, along with current annual vehicle mileage if relevant. 7. Collect the gasoline price or ask permission to obtain a current local price. 8. Record tolls, parking, and the expected change in automobile insurance. If the insurance change is unknown, keep it as a clearly labeled placeholder rather than presenting it as fact. 9. Record employee medical, dental, and vision premiums under the proposed job, along with current household medical, dental, and vision expenses that would disappear if the employee accepts the job. 10. Record the employee’s current or previous annual compensation, or another hourly value to use for valuing commuting time. 11. Record any other recurring costs caused by accepting the job and any recurring household expenses that would disappear because of accepting it. 12. Estimate after-tax pay as follows: - Gross salary - Federal income tax - State and local income tax - Social Security - Medicare - Estimated after-tax salary Use current tax rules when web access is available, and distinguish estimated withholding from actual tax liability when relevant. 13. Calculate annual commute miles: - Round-trip miles × commuting days per week × working weeks per year 14. Estimate the incremental cash cost caused by commuting, including fuel, maintenance, oil and service, tires, repairs, tolls, parking, and the incremental auto-insurance premium when applicable. Do not double-count expenses. 15. Separately estimate additional depreciation and other mileage-related economic costs that were not already included. If using an all-in per-mile vehicle-cost benchmark, do not also add its constituent costs separately. Explicitly state which method was used. 16. Calculate annual commuting hours: - Estimated minutes each direction × 2 × commuting days per week × working weeks per year ÷ 60 17. Calculate the employee’s implied hourly value: - Annual benchmark compensation ÷ 2,080 Multiply annual commuting hours by the hourly value to calculate the economic value of commuting time. Treat this as an economic cost, not a cash expense. 18. Calculate the employee’s annual out-of-pocket premiums for medical, dental, vision, and other mandatory benefits. Separately calculate any current household expense that would disappear because the new employer provides that benefit. 19. Calculate the change from the current household baseline. Do not subtract an existing expense and then add the same expense back in the same scenario. 20. Calculate cash net as: - Estimated after-tax salary - Incremental cash commuting costs - Incremental insurance costs - Employee-paid benefit premiums - Other new cash expenses + Current household expenses eliminated by taking the job This represents the approximate improvement in household cash flow attributable to the job. 21. Calculate economic net-net as: - Cash net - Value of commuting time - Incremental vehicle depreciation or other non-cash economic costs not already counted This represents the broader economic value of the job. 22. Start the final output with only these numbers: - GROSS SALARY: $____ - ESTIMATED AFTER-TAX PAY: $____ - ANNUAL CASH NET: $____ - MONTHLY CASH NET: $____ - ANNUAL ECONOMIC NET-NET: $____ - MONTHLY ECONOMIC NET-NET: $____ 23. Then provide the calculation table. 24. Finally, provide the three largest cost items, the three assumptions with the greatest uncertainty, the break-even gross salary at which accepting the job would produce the target household net value I specify, and any information I should verify before making the decision.

I built a workflow to select music for a senior fitness class that suits the participants’ general age range and meets the program’s criteria of approximately 120 BPM. I also require the music to be danceable and have a 4/4 beat. After a successful summer using AI-suggested, danceable Motown songs from the 1970s, I continued using AI to help with music selection. I don’t have a music background or the knowledge to do this myself, so I appreciate the help. Yesterday, a participant commented on how enthusiastic she was about the music. Her response was simple: “I love the music.” Step-by-step: 1. I considered the general age range of the senior fitness class participants. 2. I used the program’s target of approximately 120 BPM as a selection criterion. 3. I added my own requirements that the songs be danceable and have a 4/4 beat. 4. I used AI to suggest songs that fit those criteria, including danceable Motown songs from the 1970s during the summer. 5. I used participant feedback to confirm that the music was well received.

I use ChatGPT to analyse and redesign the underlying structure of a messy computer archive. I first generate a folder tree locally with a Python script provided by ChatGPT and saved as a BAT file. The tree shows the hierarchy of folders and filenames, giving ChatGPT a broad view of how the archive is currently organised. From that structure, ChatGPT can identify where the organisation is too fragmented or too broad. For example, a client folder may contain ten nested subfolders with only a few text files in each, making the structure more complicated than the content requires. Elsewhere, hundreds of photos, screenshots, or documents may all sit in one folder, suggesting that more meaningful categories would help. ChatGPT can then propose a revised structure with more or fewer levels, depending on the actual content. It can also suggest more consistent naming conventions for folders and files, identify recurring subjects or topics of interest across the archive, and point out categories that already exist implicitly but have never been organised deliberately. For larger changes, I can ask ChatGPT to help create a copied version of the archive using the proposed structure rather than immediately reorganising the original files. This gives me a working prototype of the new system. I can browse it in Windows Explorer, see whether the categories make sense in practice, and adjust the structure before making any permanent changes. The result is not just a cleaner folder tree. It is a way to use AI to discover the information architecture hidden inside years of accumulated files and turn it into a structure that better reflects how the content is actually used. Step-by-step: 1. I use ChatGPT to generate a Python script that creates a folder tree locally, then save the script as a BAT file. 2. I use the folder tree to show ChatGPT the archive’s hierarchy of folders and filenames. 3. I ask ChatGPT to identify areas that are too fragmented or too broad, such as deeply nested client folders or folders containing hundreds of mixed files. 4. I ask ChatGPT to propose a revised structure with an appropriate number of levels, along with more consistent folder and file naming conventions. 5. I ask ChatGPT to identify recurring subjects and categories that already exist implicitly in the archive. 6. For larger changes, I ask ChatGPT to help create a copied version of the archive using the proposed structure instead of changing the original files immediately. 7. I browse the copied structure in Windows Explorer, assess whether the categories make sense in practice, and adjust the system before making permanent changes.

I use ChatGPT to turn a physical trading card collection into a structured digital inventory. I start by photographing the collection and uploading the images to Google Drive. I divide the cards into logical groups and store them in separate subfolders, creating a clear structure before identification begins. ChatGPT then works through the folders in manageable batches, using OCR and visual recognition to extract information from the cards. This avoids manually uploading and describing every card one by one. I use consistent processing rules to reduce mistakes: I limit the number of cards per batch, make sure every source image is accounted for, and use one central card per photo when identification could otherwise be ambiguous. For each card, ChatGPT helps identify and organize the information I want to keep: card name, set code, set or series, edition, rarity, language, quantity, approximate year or period, condition notes, confidence level, and the source image. The useful part is not just OCR or card recognition. It is the combination of a structured Google Drive archive, visual identification, consistency checks, and systematic data extraction across a large physical collection. When identification is uncertain, I record that uncertainty rather than silently guessing. Damaged or unusual cards can also receive specific notes, such as foil scratches, edge wear, folds, or other condition issues. Once all folders have been processed, I consolidate the separate batches into one central inventory so I can check duplicates, quantities, and inconsistencies more easily. I first used this workflow for a Yu-Gi-Oh! collection and plan to reuse the same process for a Harry Potter trading card collection. The result is a searchable, structured overview of a physical collection that can later be used for valuation, selling, insurance, cataloguing, or simply knowing what is actually in the boxes. Step-by-step: 1. I photograph the physical trading card collection. 2. I upload the images to Google Drive and divide them into logical groups stored in separate subfolders. 3. I process the folders with ChatGPT in manageable batches using OCR and visual recognition. 4. I limit the number of cards per batch, account for every source image, and use one central card per photo when needed to reduce ambiguity. 5. I extract each card’s name, set code, set or series, edition, rarity, language, quantity, approximate year or period, condition notes, confidence level, and source image. 6. I record uncertainty instead of silently guessing and add specific notes for damaged or unusual cards, such as foil scratches, edge wear, and folds. 7. I consolidate the processed batches into one central inventory to check duplicates, quantities, and inconsistencies. 8. I reuse the process for additional collections, including my planned Harry Potter trading card collection.

When I’m continuing a book series or a show season and have forgotten key plot points—especially in fictional stories with large casts—I use NotebookLM to research a spoiler-free refresher before starting the new season or latest book. I used this approach with the new *Murderbot* series and the latest science-fiction book by James S. A. Corey, who wrote *The Expanse* and the *Leviathan Wakes* series. After loading the sources, I ask NotebookLM to create a slide deck with illustrations of the key characters, their relationships, and a quick dossier for each one. This gives me a visual anchor for the characters and earlier plot lines without revealing future events. I also want a hero image designed as a slide, cover, or thumbnail to promote this workflow. It should use and represent the NotebookLM logo and the logos of any other relevant tools, track down their current branding where possible, and turn these .dcs into HTML slide decks.