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

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.

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

I’m Jesús Núñez, an artist and the owner of J. Nunez Gallery, an independent contemporary art gallery with locations in Summit and Millburn, New Jersey. Founded in 2020, the gallery presents original abstract and figurative art, landscapes, still life, and photography. We help people discover artwork for their homes and work with interior designers on residential projects. Alongside running the gallery, I’m exploring how ChatGPT can help a small business improve its operations, marketing, and decision-making. I manage the business myself, so the practical question is how to turn existing information into useful, completed work. The workflow starts with real source material: website content, spreadsheets, analytics exports, screenshots, and the gallery’s business rules. I use focused conversations to examine one area, prepare concrete changes, and review the results. The work includes website improvements, artwork catalog organization, marketing analysis, audience segmentation, and outreach preparation. For example, AI-assisted troubleshooting helped identify duplicate website page-view tracking and guided its correction, which we checked against live analytics. That is an operational improvement; it is not evidence of increased sales. Another small-business owner can recreate the approach as follows. Step-by-step: 1. Record the business context: customers, products, geographic market, budget, brand preferences, and operating constraints. 2. Choose one specific task and define what completion means. Provide the relevant source material. 3. Require the AI to distinguish verified facts, interpretations, missing information, and proposed actions. It should not guess prices, contact details, or results. 4. Ask for a concrete deliverable, such as revised website copy, a classification table, implementation instructions, or an outreach draft. 5. Review the work and verify the actual result after implementation. Keep preparation, implementation, verification, and blocked work clearly identified. 6. Preserve approved decisions and completed actions in a current record so later sessions can continue from the existing work. 7. Measure qualified inquiries, appointments, proposals, and sales alongside marketing activity. This is an ongoing project. AI can repeat recommendations or lose track of previous decisions, so human review and continuity remain essential. I have not established a measured revenue increase or time-saving figure. I’m testing whether this approach can build a stronger business while allowing more attention for art, artists, and clients. If this example makes you curious about the gallery, you can browse available artwork and find information about our Summit and Millburn locations at https://www.jnunezgallery.com. You are welcome to explore the collection or contact us through the website for help choosing art. Jesús Núñez Artist and Owner, J. Nunez Gallery Summit and Millburn, New Jersey https://www.jnunezgallery.com

I built WarrantKit, an open-source (Apache-2.0) kill switch for AI agents. Each agent run receives a Warrant: a typed contract that specifies what the agent may do, for how long, and under which policy. A gateway checks every action before it reaches the outside world. When containment triggers, the runtime’s epoch advances, immediately invalidating every Warrant issued under the old epoch instead of allowing it to linger until a timer expires. Evidence of what happened remains separate from authority, and receipts can be verified offline with a standalone Python script. I designed the architecture and threat model, then used AI coding assistants for most of the implementation. I reviewed everything against an adversarial test suite and a real-host enforcement demo that others can run themselves. Before writing the mechanisms, I wrote tests for the attacks: replayed runtime reports, tampered event sequences, evidence attempting to upgrade itself into authority, and authority carried across execution boundaries. The suite has 202 passing tests, and several core behaviors exist because a test caught the system trusting too much. One example is a recovered runtime carrying a stale report into a new epoch. I then proved enforcement on a real Linux host with a cgroup-v2 real-kill demo before claiming it. The no-root demo is simulated, and the README says so. It also lists what WarrantKit is not. The architecture is layered: WarrantKit owns the authority lifecycle and verification; AgentContainment owns the enforcement boundary; and Warden, DProvenanceKit, and ClaimProofKit record evidence independently. Step-by-step: 1. I defined a Warrant as a typed contract specifying an agent’s permitted actions, duration, and governing policy. 2. I placed a gateway in front of the outside world so it checks every agent action before allowing it through. 3. I made containment advance the runtime’s epoch, invalidating every Warrant issued under the previous epoch immediately. 4. I kept evidence separate from authority and made receipts verifiable offline with a standalone Python script. 5. I wrote adversarial tests for replayed runtime reports, tampered event sequences, evidence attempting to become authority, authority crossing execution boundaries, and stale reports carried into a new epoch. 6. I implemented the system with help from AI coding assistants and reviewed the implementation against the test suite and a real-host enforcement demo. 7. I validated enforcement on a real Linux host with a cgroup-v2 real-kill demo, while clearly labeling the no-root demo as simulated in the README. 8. I kept authority lifecycle, enforcement, and evidence recording in separate architectural layers using WarrantKit, AgentContainment, Warden, DProvenanceKit, and ClaimProofKit.

I’m designing a publishing system that keeps producing value without requiring constant output. This workflow started with frustration about the usual content model: publish constantly, stay visible, feed the algorithm, and repeat. That model works poorly when my energy varies, my interests shift, and forcing output quickly turns creativity into maintenance. Instead of asking, “How do I post more?” I’m asking: “How can content keep moving without requiring me to keep producing at the same pace?” The system is built around uneven energy. During high-energy periods, I can generate ideas, draft pieces, collect fragments, or prepare several posts at once. During low-energy periods, existing material does not become a failure state. It can sit, mature, be lightly edited, be reused, or simply wait. Ideas can exist in different stages: a note, a half-developed thought, a finished piece, something worth revisiting later, or something that can be repurposed in another format. Older material is not automatically “used up” after publication. A long-form idea can become a short post. A workflow can become a case study. A conversation fragment can become an essay seed. A previous post can return later from a different angle. The goal is not to build a machine that constantly demands feeding. It is to create a content reservoir I can draw from when I have the capacity. This workflow has not been fully implemented yet, but the design principle is useful: > Build around energy reality, not around imaginary consistency. Content should fit into life. Life should not be reorganized to serve the content treadmill. Step-by-step: 1. I design the publishing system around variable energy rather than a constant production schedule. 2. During high-energy periods, I generate ideas, draft pieces, collect fragments, and prepare several posts at once. 3. During low-energy periods, I let existing material sit, mature, receive light edits, be reused, or wait. 4. I allow ideas to remain in different stages, from notes and half-developed thoughts to finished pieces and material worth revisiting later. 5. I repurpose older material across formats, such as turning a long-form idea into a short post, a workflow into a case study, a conversation fragment into an essay seed, or a previous post into a new angle. 6. I draw from the resulting content reservoir when I have the capacity instead of constantly feeding a content treadmill.

Today's Rundown reported that Anthropic spent the past year consulting religious scholars from different faiths to help shape Claude's morals. I use a different approach for Bible study, research, and writing Bible study books with Claude. I wrote a set of Bible study principles that Claude reads before any work begins and follows throughout the process. The main tenets are: - The Bible is the sole authority. No commentary, tradition, or scholar outranks the text. - Scripture interprets Scripture. When a passage is unclear, the answer comes from another passage, not from a theological system. - First ask what the text actually says before asking what it means. - Ask who is speaking, to whom, and under what circumstances. - Quote every verse word for word. Never paraphrase it. - Separate what the text states from what we infer, and say "I don't know" where the Bible is silent. The difference shows in the outcome. The books contain no man-made doctrines, denominational vocabulary, or creeds—only what the Bible says, with the passage shown for every claim. When a draft goes beyond the text, these principles catch it. My experience is that the moral standard an AI needs is already written down, and an AI can be held to it. The principles, along with 23 free books and studies, are available at noblemind.study. Step-by-step: 1. I wrote a set of Bible study principles for my own Bible study, research, and Bible study books. 2. I have Claude read the principles before any work begins. 3. I require Claude to follow the principles throughout the work. 4. I use the principles to keep claims grounded in the biblical text, quote verses word for word, and distinguish statements from inferences. 5. I review drafts for man-made doctrines, denominational vocabulary, creeds, and claims that go beyond the text.

I built a voice-activated air traffic control simulator featuring one of the approaches for Hamad International Airport’s Runway 34R in Doha, Qatar. I downloaded the waypoints for one of the STARs for Runway 34R. The aircraft can climb, descend, fly assigned headings, or go directly to waypoints. Once an aircraft is established on final, it automatically contacts the tower at a certain point. The simulator is voice-activated by transmitting through the F5 microphone button on a Mac. Step-by-step: 1. I selected one of the approaches for Runway 34R at Hamad International Airport in Doha, Qatar. 2. I downloaded the waypoints for one of the STARs serving Runway 34R. 3. I configured the aircraft to climb, descend, fly headings, and go directly to waypoints. 4. I set the aircraft to automatically contact the tower at a certain point after becoming established on final. 5. I enabled voice activation by transmitting through the F5 microphone button on a Mac.

I use ChatGPT to help me prepare for appointments with the healthcare professionals who already follow me, especially when several conditions or symptom patterns overlap. I have recurring neurological symptoms as well as diabetes, and I am followed by different professionals. The difficult part is often not noticing that something has changed. It is deciding which changes are relevant, which clinician is the right person to tell, and what information will be useful during a short appointment. Before an appointment, I give ChatGPT the questions and observations I have collected. I ask which details are likely to matter most to that type of specialist, which questions belong with my neurologist, GP, endocrinology team, or another professional, whether I am missing information that would make the situation easier to assess, and which observations are background information versus points to mention early in the consultation. The useful part is prioritization. I might arrive with ten observations, and ChatGPT helps me reduce them to the few that are most relevant. Occasionally, it promotes a detail from “somewhere in my notes” to “mention this near the beginning because it may deserve investigation.” When an appointment is still weeks away, I sometimes use ChatGPT to design a small, temporary tracking routine. Instead of logging everything, I might record three specific parameters in the morning and evening, or note the time, duration, circumstances, and possible trigger whenever a particular symptom occurs. This gives me a compact record to bring to the clinician instead of relying on memory. The division of roles stays clear: I provide the lived experience and observations, ChatGPT helps organize and translate them, and the healthcare professional interprets their medical significance and decides what should be investigated or treated. As a result, appointments become less about reconstructing several weeks of symptoms from memory and more about giving the clinician a concise, usable picture of what has actually been happening. Step-by-step: 1. I collect my questions and observations before an appointment. 2. I give them to ChatGPT and ask it to identify the details most relevant to the type of specialist I will see. 3. I ask which questions belong with my neurologist, GP, endocrinology team, or another healthcare professional. 4. I ask whether any information is missing and which observations should be mentioned early in the consultation. 5. I reduce a longer list of observations to the points most relevant to the appointment. 6. If the appointment is still weeks away, I use ChatGPT to design a small temporary tracking routine, such as recording three parameters in the morning and evening or noting a symptom’s time, duration, circumstances, and possible trigger. 7. I bring the compact record to the clinician, who interprets the medical significance and decides what should be investigated or treated.

For years, I kept lists of things I wanted to look up someday: names, historical references, places, traditions, techniques, unfamiliar concepts, and strange terms I encountered along the way. Most of them lived in Google Keep. They were little bookmarks for my attention: > “I don’t know what this is yet, but something about it caught me.” The problem was returning to them. Looking everything up separately takes effort, especially when I cannot remember why I saved a particular term. So I use AI to turn a batch of those notes into small doors I can open. The basic idea I give AI a list of terms and ask for short, accessible introductions—just enough to understand what each thing is and decide whether I want to learn more. Then I react. Some entries get a quiet “interesting.” Others get: > “OOOH. Tell me more about THIS one.” That reaction determines the next branch. Step-by-step: 1. I copy a manageable batch from my notes. The items do not need to belong to the same subject. A batch might contain an artist, a religious figure, an architectural technique, a place, and an unfamiliar philosophical term. 2. I keep any context I recorded, such as where I encountered the item, what caught my attention, or whether there was a picture, quotation, object, or question attached. That context can help AI interpret an ambiguous name and reconnect me with the original curiosity. 3. I ask for small introductions. My request is roughly: > “Give me a short, accessible introduction to each item. Explain what it is, what makes it interesting, and a few directions I could explore. Flag ambiguous names or uncertain identifications. Keep the first pass light so I can choose what pulls me.” The first pass should make choosing easy. A deep report on every entry would bury the interesting parts under another backlog. 4. I read the introductions and respond naturally: “More about this one,” “How did that tradition begin?”, “Show me what it looks like,” “Why does that material behave like that?”, or “Wait, is this connected to the thing we discussed earlier?” I do not have to justify why one item suddenly becomes fascinating. The other entries can stay for later. 5. Once something catches, I follow the question that appears. An explanation introduces a new term, an image reveals a detail, the detail raises a question, and the question leads somewhere unexpected. For example, a visit to a small chapel prompted questions about a Madonna statue represented in the style associated with Lourdes. That opened into saints, prophets, religious imagery, and how particular figures become visually recognizable. The chapel provided the first door; the next questions appeared while I explored. 6. I use AI suggestions as invitations. AI can suggest entries I might enjoy based on interests that have emerged in our conversations, helping me notice an unfamiliar item I might otherwise skip. My response still steers the exploration. I can follow the suggestion, ignore it, or become absorbed in something completely different. The useful feedback is often immediate: “Yes, more of that,” “Too technical,” “I want the historical story,” or “The visual part is what interests me.” 7. I keep only what I want to return to. Sometimes I save a useful explanation, source, image reference, or new question. Some discoveries later feed into my creative research database. Sometimes the conversation itself is enough. There is no requirement to turn the discovery into a project, course, post, or finished piece. Learning something because it was interesting already counts. If I save a trace, I keep what will help me reconnect later: what it was, what interested me, and where I could continue. 8. I leave room for changing curiosity. An item that feels dull today may become fascinating after another encounter gives it context. Unchosen entries therefore remain available. A backlog is a reservoir, not a queue I must finish. This also makes mixed lists useful: the next interesting connection may come from crossing subjects rather than staying inside one category. The workflow in one line Collect loose curiosities → ask AI for small introductions → notice what pulls → follow emerging questions → save useful traces → return when something feels alive again. Why I use it This workflow makes the first encounter with an unfamiliar subject easy enough that I actually begin. I do not need a polished research question. I can arrive with a strange word from a note written three years ago and say: > “What was this little creature again?” AI helps open the door. My curiosity decides how far we wander. 😅📚

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

I'm building a small family property-management app using ChatGPT for requirements and Codex desktop on Linux for implementation, with TypeScript, PostgreSQL/Supabase and Vercel. It covers renovation forecasts, quotes, costs/payments, operating income and expenses, and family loans. The app is already in use. We have automated checks, isolated synthetic data, financial reconciliation and controlled releases. The next challenge is making development repeatable while keeping everyday forms, mobile workflows and reporting clear for non-technical family users. I'd value practical experience from people who have maintained an AI-built financial or admin app beyond its prototype: 1. How do you keep requirements, acceptance tests, candidate versions and deployed releases aligned across long Codex threads and workspaces? 2. What browser-testing and release-evidence workflow has reliably caught failures that builds and unit tests missed? 3. Which narrowly scoped GitHub skills, agent packages or UI references have improved your results without adding conflicting instructions or excessive process? 4. What broke after deployment, and what did you change? Links to maintained repositories, runbooks, example acceptance records or fictional-data screen recordings would be especially useful. I'm looking to improve the existing app and workflow rather than rebuild it or add a large agent framework.

I had a ChatGPT subscription that I knew I would not use during the coming month, so I wanted to find a productive use for the tokens I would otherwise pay for without using. I created a team of specialized agents on Raft that works persistently in the background. They continue working until all my allotted tokens are used, wait for the tokens to reset, and then continue. I assigned them a project: searching a stretch of LiDAR-mapped dense forest in Slovenia for archaeological discoveries. The agents scan the dataset for meaningful anomalies that could point to potential findings. Anything they identify will be handed over to the Slovenian authorities for further investigation. Even if they find nothing, that result is valuable in its own right. I encourage anyone with an idle AI subscription to use it for something beneficial. There are many publicly available datasets containing potential discoveries that no human would ever have time to examine manually. Step-by-step: 1. I identified a ChatGPT subscription that I would not be using during the coming month. 2. I created a team of specialized agents on Raft to work persistently in the background. 3. I configured the team to work until my allotted tokens were used, wait for the reset, and then continue. 4. I directed the agents to scan LiDAR data from a dense forest in Slovenia for meaningful anomalies. 5. I planned to hand any potential discoveries over to the Slovenian authorities for further investigation. 6. I treated a lack of findings as valuable information as well, since the dataset would still have been examined.

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.

I started with ChatGPT to analyze video content and recreated a paper-based research process as a useful PWA (Progressive Web App) for Rundown AI readers. ChatGPT created a skill set for Claude, and Claude coded the app and helped package it for Google Play. A service worker makes the app work offline and installable. Life 168 | Balance 24*7 is a six-part interactive survey that maps your average week across 16 strategic areas of life. You rate each area for time, importance, and satisfaction. The PWA charts your portfolio and shows where your hours, priorities, and goals have drifted apart. It also produces one-page and 30/60/90-day action plans to use with AI. I'm a research analyst with an MBA. The app is built on Dr. Rainer Strack's strategic life portfolio, “Use Strategic Thinking to Create the Life You Want” (TED / Harvard Business Review). I built the instrument; he built the thinking behind it. The result is Life 168 | Balance 24*7, and it's live now: https://app.life168.org/. It's free to use. Try it and start today. Step-by-step: 1. I used ChatGPT to analyze video content and recreate a paper-based research process. 2. I had ChatGPT create a skill set for Claude. 3. Claude coded the PWA and helped package it for Google Play. 4. I added a service worker so the app would work offline and be installable. 5. I structured the app as a six-part survey covering 16 areas of life, with ratings for time, importance, and satisfaction. 6. I used the survey results to chart each user's life portfolio, identify gaps between hours, priorities, and goals, and create one-page and 30/60/90-day action plans for use with AI. Life 168 | Balance 24*7 is live at https://app.life168.org/ and free to use.

I design songs by giving different vocal parts different emotional jobs rather than writing one continuous lyric and deciding afterward who sings each section. I start with contrast. One voice might carry rhythm, detail, tension, or narrative through rap, while another opens the song emotionally through a melodic chorus. A sung section can create space after a dense verse, and a rap section can sharpen the story after a more atmospheric refrain. The contrast is functional as well as musical. Different voices can represent different perspectives, emotional registers, or levels of intimacy. The chorus can express the feeling that the verse struggles to name, while the verse can complicate what the chorus makes sound simple. A bridge can temporarily change the relationship between them. This is why songs that combine rap and fully sung passages can work: the parts are doing different jobs instead of simply stitching two styles together. The song “Airplanes” is useful as a structural inspiration because of its contrast between rhythmic narrative and a melodic, emotionally open refrain. The goal, however, is not imitation. It is to understand why that contrast works and build a new song around its own voices, themes, and emotional architecture. AI can help me develop lyrics, transitions, vocal roles, perspective shifts, and the points where the song needs to open up or contract. The result is a song designed not only around verses and choruses, but also around the relationship between different ways of speaking and singing. Step-by-step: 1. I identify the different vocal modes the song will use, such as rap, melodic singing, or a bridge. 2. I assign each vocal part a distinct emotional or narrative job, such as carrying rhythm, creating tension, opening emotionally, or introducing another perspective. 3. I use contrast to create movement: a sung section can follow a dense verse, while a rap section can sharpen the story after an atmospheric refrain. 4. I decide how the voices relate to one another, including what the chorus expresses, what the verse complicates, and whether the bridge changes their relationship. 5. I study the contrast between rhythmic narrative and melodic refrain in “Airplanes” as structural inspiration without imitating it. 6. I use AI to develop lyrics, transitions, vocal roles, perspective shifts, and the points where the song should open up or contract. 7. I shape the final song around the relationship between its different ways of speaking and singing, not only around its verses and choruses.

I’m creating a film set in the cyber world—a mix of fiction, adventure, mystery, action, and thriller. My AI world-building will continue over a long period of time.

I wanted a publicly viewable leaderboard on the web, with input coming from creators. I prompted Gemini: " Can you design good looking leaderboards using Google documents. I want three: all time, rolling 30 days and rolling 90 days. They should be different tabs on the same document. They should be easy to administer/update. Show me a mockup and describe how it would work." After I was satisfied that it would be easy to launch and maintain, I got more specific. Because it was for creative types, I wanted more than a basic spreadsheet ranking. Gemini responded: "It features profile avatars, gamified badges, high-contrast dark visual styling, and clear ranking tabs for All-Time, Rolling 30 Days, and Rolling 90 Days..." That's what AI calls creative, I guess. Later in the chat, Gemini suggested achievement levels with a more creative feel: - 👑 Century Virtuoso / Platinum Mic - 🔥 Monthly On-Fire / Speedster - 🎙️ Heartstring Weaver - 🌟 Smile Architect For the podium treatment, rows 1, 2, and 3 feature custom metallic highlights—Warm Gold, Silver Slate, and Bronze Copper—with circular numerical rank badges to make top contributors stand out instantly. Gemini heavily integrated Google Docs and Google Sheets. The system uses Google Apps Script to update the leaderboard in real time based on creator activity. Step-by-step: 1. I asked Gemini to design three leaderboards—All-Time, Rolling 30 Days, and Rolling 90 Days—as separate tabs in the same Google document. 2. I asked for the leaderboards to be easy to administer and update, along with a mockup and an explanation of how they would work. 3. After reviewing the initial concept, I clarified that the leaderboard was for creative types and should be more distinctive than a basic spreadsheet ranking. 4. Gemini added profile avatars, gamified badges, high-contrast dark visual styling, and clear ranking tabs. 5. I incorporated creative achievement levels, including Century Virtuoso / Platinum Mic, Monthly On-Fire / Speedster, Heartstring Weaver, and Smile Architect. 6. I used Warm Gold, Silver Slate, and Bronze Copper highlights for the top three rows, along with circular numerical rank badges. 7. I connected the system to Google Docs and Google Sheets and used Google Apps Script to update it in real time based on creator activity.

I’m the Export and Operations Manager at Supreme Poultry & Chickens, an Australian poultry processing business. My original request to ChatGPT was straightforward: find and track grants that could help us grow our business. As we worked together, I began to see the potential to build a management system that could organise our operations and help us prepare a business case when an opportunity arose. That led me to discover Sites and the possibility of building our own system. We already use SafetyCulture for inspections. It also offers maintenance functionality, but that system didn’t connect with the other parts of our management processes in the way we needed. We wanted our records, schedules, and actions connected across the business. Over roughly ten weeks, working with ChatGPT and Sites, we progressively developed the Supreme Poultry Management System (SPMS). It brings together: * Export enquiries, customers, and shipping schedules * Purchase orders and approvals * Vehicles, registration, insurance, and inspection dates * Assets, maintenance schedules, and job history * Supplier certificates and HACCP records * Environmental compliance and complaints * Water management and daily processing records * Dashboards and operational reporting * A central 45-day action calendar * A system backup module Behind SPMS, we also built a database that stores the records and supports the system. It provides a shared foundation for the different modules, allowing information to be linked across our management processes. The database stores the underlying records and history, while SPMS makes that information accessible through screens, reports, and the action calendar. Water management is a particularly important example. Water is one of the most critical factors in our poultry processing business. SPMS receives tank-level readings from a laser-operated monitoring device that transmits data over the 4G network. We placed a water management widget at the top of every SPMS page, keeping that information visible wherever we’re working and helping us stay on top of our water supply throughout the day. The process hasn’t been without setbacks. At one stage, we nearly lost the whole system, and I had to rebuild it using screenshots I had saved. That experience made backups a priority. We’ve since built a dedicated backup module and now back up the system regularly. For anyone following a similar path, I recommend establishing backups early. The most useful part has been turning our actual business rules and priorities into system behaviour. An export order needs to remain visible until it ships. Completing a recurring maintenance job should preserve its history and its next scheduled occurrence. Supplier certificates need expiry tracking and a record of whether replacements have been requested. Critical operational information, such as water management, needs to stay visible across the system. We developed the system progressively: describe a problem or process, build the workflow, use it in daily operations, and then refine it. Here’s how someone else could recreate the approach: Step-by-step: 1. Start with a real business need. Ours was finding grants. 2. Gather the records, spreadsheets, and forms you already use. 3. Explain how the process works, including responsibilities, deadlines, and exceptions. 4. Use ChatGPT and Sites to build one manageable module, with a database to store its records. 5. Establish regular backups early and check that you can restore them. 6. Check the module against real examples and refine it through daily use. 7. Add related modules, connecting shared database records and actions. 8. Identify your most critical operational information and keep it visible wherever people work in the system. This is the starting prompt I used: “Help me build a management system for my business using Sites, backed by a database for our records. Start with [workflow]. These are our current records and business rules. Identify missing information, help me build the first module and its database structure, and check it against real examples. Include a backup and recovery process, and a shared widget across pages for [critical operational information].” SPMS is still evolving. What started as a grant search has become a practical tool for managing our business and building an organised foundation to support future growth.

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

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