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

I tried using Claude and it lost context of the whole project quickly and became a nightmare of human in the loop meat proxying. It made the exercise far from autonomous.

I’m a nurse with no tech experience, but I’m curious and have many creative ideas. I used Claude to build a website that helps people plan which vegetables to grow based on their location, available space, and the time they have. Veggiegrowguide.com Step-by-step: 1. I identified an idea for helping people choose vegetables to grow based on their location, available space, and available time. 2. I used Claude to help me build a website for the idea. 3. I created Veggiegrowguide.com as a resource for people planning their vegetable gardens.

I used Astra to redesign my personal wardrobe. I want to dress better, but my absolute worst nightmare is having a closet full of clothes that creates more clutter in my brain. I already have enough to think about, so I built an app that decides what I should wear based on the season and local weather using GPT-6 Astra. I gave it a few full-body photos, my height, weight, sizes, and niche details such as having broad shoulders and needing to tailor my waist. I also shared the colors I like, added a master prompt, and asked it to build a site. The results were incredible. I'm the model in every photo, and Astra's virtual try-on is genuinely impressive. If I can't find a piece online, I update the model and regenerate the pictures. Step-by-step: 1. I opened ChatGPT desktop with GPT-6 Astra and Codex/Sites, then turned on Computer Use and image generation. 2. I started a new chat and uploaded four to eight full-body photos, one clear face photo, and closet photos when available. 3. I pasted the prompt below, filled in my name, city, and sizes, and let it work for one to two hours. 4. I sent a couple of correction passes instead of rebuilding the whole system. I removed things I would never wear and added things I actually wear. PROMPT: GOAL Build a working website called [YOUR NAME]'s Wardrobe. It blends two things: 1) A closed uniform system of exactly 30 looks 2) A personalized shopping portal where I am the model in every photo, Aritzia/Uniqlo catalog quality (seamless studio backdrop, full-body try-on, product-card grid) SITE NAME [YOUR NAME]'s Wardrobe THE ONLY INVENTORY - 7 summer outfits - 7 fall outfits - 7 winter outfits - 7 spring outfits - 1 gym outfit - 1 lounge outfit = 30 looks. Nothing else. Each look is complete: top + bottom or one-piece + shoes + at most 2 extras. Reuse pieces across the 7 looks in a season. Cap unique garments at 35–50 including shoes and outerwear. Throw everything else out. WHO I AM - Name: - Lives: [city] - Height: - Weight: - Sizes (top / bottom / shoe): - Body notes: - Work dress code: - Weekend life: - Style in 5 words: - Colors that work / colors I refuse: - Budget for gap-filling buys: - Hard constraints: Attached photos are the identity lock. Reproduce my real face AND real body in every try-on. Do not slim, lengthen, or beautify me. LIVE WEATHER (required, not a mock) On every page load, fetch live weather for [CITY] from Open-Meteo with no API key. Use the correct lat/long and timezone. Show on the homepage: - “Today in [CITY]” - apparent temperature, condition, rain yes/no - ONE recommended look from the 30 - why that look won - 1 weather swap (if rain starts / if it drops 5°C) Selection logic: - apparent temp ≥ 20°C and dry → Summer pool - 15–19°C dry → Spring pool Mar–May, Fall pool Sep–Nov, otherwise the closer season - 8–14°C → Fall pool, prefer the look that already includes a mid-layer - ≤ 7°C → Winter pool - rain now or daily precipitation ≥ 1mm → jacket + closed shoes, no white sneakers or silk - wind ≥ 25 km/h → prefer a layer - gym / lounge days use those uniforms, add a layer only if ≤ 10°C Never invent an outfit outside the 30. SITE STRUCTURE - Home: today + try-on + wear-this checklist - Summer / Fall / Winter / Spring: 7 look cards each, me wearing the full look - Gym / Lounge - Pieces: every unique garment on me, marked OWNED or BUY - Purge: sell / donate / trash for anything not in the system - Rotation: 4-week calendar per season. Weather can override, but it still has to be one of the 7 (or gym/lounge) VISUAL BAR Premium catalog photography. Gray/white seamless, even light, full body. Do not clone another brand’s logo. This is [YOUR NAME]'s Wardrobe. HOW TO BUILD Step-by-step: 1. Build the 30 looks from my photos, stats, climate, and closet photos. Use owned pieces first. 2. Generate consistent try-ons of me for every look and every piece. 3. Build a real clickable site. Hook live weather. Do not fake it. 4. If an image breaks my face or body, regenerate it before shipping. 5. No payments. Personal wardrobe OS only. OUTPUT Live site, the 30 looks, piece list (owned vs buy), ranked shopping list, purge list, weather mapping, and what you inferred vs what came from my photos. Start now. Make the call if a detail is missing. Only ask if the photos are unusable.

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

Turn scattered creative preferences into four living style books THE PROBLEM My taste was scattered across old conversations, clothing lists, search terms, saved images, handmade collages and experiments transforming my childhood drawings with AI. I wanted something I could use to make new work, rather than another archive of everything I had ever mentioned. A generic label like “colourful and whimsical” was not enough. My preferences also change with the application: a collage, an outfit, a room and a digital course do not need the same treatment. THE WORKFLOW 1. Bring together different kinds of source material. I used an earlier style conversation, a digital design style document, a list of search terms, photos of my own collages and the corrections I had made during image-generation experiments. Ask AI to read source texts fully, and distinguish your statements from suggestions made by an earlier assistant. 2. Analyse patterns, then correct the interpretation. The AI proposed connections involving colour, texture, shape, atmosphere, vintage objects and visual storytelling. I refined these through concrete examples. For instance, liking stilettos and being able to wear them comfortably are separate facts. Liking geometric structures does not mean I want triangular wallpaper. A technically imperfect image can still work when it preserves the atmosphere I intended. 3. Treat corrections as part of the research. “Too childish” may mean wrong for this drawing’s intended audience, rather than a universal dislike. A saved image may be intriguing without being something I want to keep encountering. An entire family of similar images may appeal to me without needing to rank every member. One especially useful correction: patterns visible in my collages do not prove I consciously planned them. I sort clippings into categories and sometimes colour groups; the collage itself develops while I make it. 4. Include my own categories. My clipping categories include texture, image, black-and-white, colour, background, small meaningful items, comics and words. “Colour” means a clipping kept mainly for its colour, not simply any colour photograph. “Texture” includes both natural surfaces and designed patterns. These definitions provided better starting points than generic categories imposed by the AI. Digital design and graphics also received a full category of their own, rather than being treated as an exception to my taste elsewhere. 5. Create four distinct outputs. • Style Book: precise preferences, boundaries, exceptions and provisional design principles. • Visual Atlas: image families connected across subjects, with actual examples and explanations of what might link them. • Prompt Bible: modular language for colour, material, light, composition, figures and atmosphere, plus reusable recipes and lessons from corrections. • Curatorial Map: connections between interests such as vintage objects, memory, surfaces, small living worlds, language and digital design. 6. Keep the books open to revision. Separate confirmed preferences, observations and hypotheses. When new material arrives, ask what it confirms, refines or contradicts. Add what changes the understanding instead of documenting every conversation. WHAT THIS PRODUCED Four separate first-draft HTML books, including a visual atlas with 14 photographs of my collages. They bring clothing, interiors, fragrance, digital design and creative work into the same research project while preserving their different requirements. WHY IT HELPED The process made my corrections useful. Instead of asking AI to define my taste once, I could respond to concrete interpretations until the descriptions became more accurate. The books support future making without prescribing how I must create. STARTER PROMPT “Use these sources to draft four separate living documents: a personal Style Book, a Visual Atlas, a modular Prompt Bible and a Curatorial Map of Fascinations. Read the source texts fully and distinguish my own statements from earlier AI suggestions. Find recurring patterns, exceptions and unexpected connections. Keep preferences specific to their application, including clothing, interiors, digital design and graphics. Treat my corrections as evidence. Label observations and hypotheses clearly, and do not invent conscious intentions behind intuitive work. Use supplied images in the atlas where available. Build useful first drafts rather than a complete archive, and translate each finding differently for each document’s purpose.”

What do you do when your wife says you talk about AI too much? You listen to her, and when she has a problem, you frantically write it down and build it with AI. My wife enjoys working with her plants in the warm sun and light breeze of the Carolina mountains. She’s new to gardening and learning more each day, but she was having trouble keeping track of everything. Which tree did she plant in the front yard last year? It seemed to be struggling—would it do better somewhere else? And would rain reach the potted flowering planters while we were out of town, or would she need to find someone to help? I used Claude Code and Fable to develop an app that my wife could run on her phone, with all the data stored locally. Now she’s excited about “her app” and the things she can add to it. She has even shared it with others, including people across the country, so we added climate zone settings to make it useful in other parts of the country. 😂 Step-by-step: 1. I listened to my wife’s gardening challenges and wrote down the problems she wanted to solve. 2. I used Claude Code and Fable to develop a gardening app for her phone. 3. I designed the app to keep all the data stored locally. 4. I built in a way to track plants, including which tree was planted in the front yard and how it was doing. 5. I accounted for questions about rain and the care of potted flowering planters while we were out of town. 6. After my wife shared the app with people across the country, I added climate zone settings so it could be useful in other regions.

At some point, my newsletters stopped feeling like reading and started feeling like debt. The information was good; I just couldn’t keep up. I wanted a way to turn that backlog back into something useful. So I built The Daily Nexus, a private tool that reads newsletters from a Gmail label and creates two editions: a podcast I can listen to and a separately written, two-page newspaper I can scan. It runs on demand or on a schedule, and it can publish the audio to a private RSS feed for Apple Podcasts. The project also became a hands-on experiment in building with coding agents. Claude Code and Codex helped me implement features, troubleshoot failures, review the design, and tighten security. The stack includes Python, the Gmail API, Antigravity, Kokoro, FFmpeg, Firebase, Cloudflare Workers, and GitHub Actions. The carousel shows the rest of the flow. It started as a personal tool, but I’m sharing the template for anyone who wants to adapt the idea. Each deployment uses its own accounts and credentials, and the design aims to avoid additional API costs by using an existing AI subscription and available free tiers. GitHub Repo Template: https://lnkd.in/eYceS4KR Step-by-step: 1. I label the newsletters I want to process in Gmail. 2. I run The Daily Nexus on demand or on a schedule so it can read the newsletters from that Gmail label. 3. The tool creates a podcast edition and a separately written, two-page newspaper edition. 4. I listen to the podcast or scan the newspaper, depending on how I want to catch up. 5. When needed, the audio is published to a private RSS feed for Apple Podcasts. 6. I use Claude Code and Codex to implement features, troubleshoot failures, review the design, and tighten security. 7. Each deployment uses its own accounts and credentials, with Python, the Gmail API, Antigravity, Kokoro, FFmpeg, Firebase, Cloudflare Workers, and GitHub Actions supporting the workflow.

I built a custom AI knowledge-transfer GPT designed to prevent institutional knowledge from walking out the door when an experienced employee leaves. The trigger was an experienced operations manager preparing to leave the organization. I realized that while we had procedures, files, emails and account documentation, a huge amount of operational knowledge existed only in that manager’s head: customer preferences, recurring staffing problems, site-specific quirks, key relationships, historical issues, workarounds, lessons learned and the small details that can take a replacement months to discover. My goal was to capture that knowledge and turn it into an interactive resource for the incoming operations manager. First, I conducted and recorded an in-depth interview with the departing manager. Instead of only asking standard turnover questions, I had them walk through the operation as if they were personally training their replacement. We discussed customers, employees, locations, scheduling, recurring problems, escalation procedures, communication preferences, historical decisions and things they believed a new manager might not realize immediately. I then transcribed the conversation and used AI to analyze the interview for knowledge gaps. I asked the AI to approach the transcript from the perspective of someone taking over the job and identify important questions that had not yet been answered. Using those gaps, I had AI create customized knowledge-transfer questionnaires specifically for the departing manager. These asked more targeted questions such as: What problems happen repeatedly? What customer preferences are not documented? What exceptions exist to normal procedures? What mistakes is a new manager likely to make? What information exists only in your memory? What would you make sure your replacement understood during their first 30 days? The departing manager completed those documents, giving me another layer of institutional knowledge that would normally be lost. Next, I organized the interview transcript, completed questionnaires, operational procedures, account information, contacts, historical notes and other relevant documents into a knowledge base. I uploaded that information into a custom GPT and instructed it to function as an operational knowledge-transfer assistant. The GPT was told to base answers on the captured information, not invent answers when information was missing, and clearly tell the user when something needed to be verified. The incoming operations manager can now interact with that knowledge conversationally. Instead of searching through folders or wondering who to ask, they can say things like, “I’m meeting with this customer tomorrow. What should I know?”, “Has this location had staffing problems before?”, “Why do we handle this account differently?”, or “What should I watch for during my first month?” The GPT is now being used by the incoming manager as an ongoing reference tool. The result is essentially a searchable, interactive version of the institutional knowledge that previously would have disappeared with the departing employee. It reduces the “I don’t know what I don’t know” period of starting a new position, shortens the learning curve, improves operational continuity and helps prevent the next person from having to relearn years of lessons through trial and error. The same workflow could be recreated for retiring executives, salespeople, plant managers, administrators, project managers, maintenance supervisors or anyone whose experience contains valuable institutional knowledge. The employee can leave. Their knowledge doesn’t have to.

I record calls with Granola and paste the transcript into Claude, but the action items it pulls are hit or miss. Sometimes it skips things that were clearly decided and sometimes it invents owners. I tried asking for a table with owner and due date but it still guessed. Looking for a prompt or workflow that's reliable enough I can trust it without rereading the whole transcript.

AI is good at generating polished answers, but polished answers are not always your answers. When people ask AI for help with writing, strategy, or difficult decisions, it can jump too quickly to a conclusion and fill in beliefs the user has not fully examined. I created a thought-partner agent that interviews me before producing recommendations or drafts. Its job is to ask probing questions, challenge weak assumptions, surface contradictions, and separate my actual views from ideas suggested by the AI. Instead of writing for me immediately, it helps me clarify my position first. Step-by-step: 1. I give the agent the topic, decision, or idea I want to explore. 2. I tell it not to draft the final output yet. Its first job is to interview me. 3. I have it ask one focused question at a time about my reasoning, evidence, assumptions, audience, and uncertainty. 4. I require it to challenge vague claims and point out contradictions or overlap with my previous thinking. 5. I ask it to clearly separate: - conclusions I stated - ideas the AI proposed - issues that remain unresolved 6. I continue until the central belief, argument, or decision becomes clear. 7. I have the agent create a structured synthesis containing the core thesis, supporting reasoning, counterarguments, open questions, and useful language from the discussion. 8. I pass that synthesis to a writing, planning, or execution agent. I end up with a position that reflects my actual thinking rather than a plausible answer generated by AI. The final writing or strategy is more original, more consistent, and easier for downstream agents to execute.

I built a daily AI story-scouting workflow that finds potentially viral stories for Instagram Reels, YouTube Shorts, and TikTok without recycling topics we’ve already covered. First, the workflow reviewed Rowan’s public short-form archive once to create a coverage map of past topics and editorial taste. It uses that map as a filter, helping distinguish a genuinely new angle from another version of the same AI launch, robot demo, or research story. Every morning, it scans priority sources, including AI and technology coverage from major newspapers and tech blogs, The Rundown newsletters, company announcements, research papers, and public updates from major AI and robotics companies. The workflow is not limited to same-day news. It also looks back over the past one to six weeks for stories that have not been extensively covered in the media. Each potential story is checked for four things: a clear visual hook, a technical idea that can be explained in 45–90 seconds, broad audience interest, and meaningful novelty compared with Rowan’s past coverage and the previous week’s recommendations. It keeps every story that clears the bar rather than forcing a fixed number. The final brief is ranked by strength and sent as one compact Slack DM at 10 AM each day. Step-by-step: 1. The workflow reviews Rowan’s public short-form archive once and builds a map of past topics and editorial taste. 2. Each morning, it scans priority sources, including major newspapers, tech blogs, The Rundown newsletters, company announcements, research papers, and public updates from major AI and robotics companies. 3. It searches both same-day news and stories from the previous one to six weeks that have not been extensively covered in the media. 4. It filters out topics that substantially repeat Rowan’s past coverage or the previous week’s recommendations, while identifying genuinely new angles. 5. It evaluates each potential story for a clear visual hook, a technical idea explainable in 45–90 seconds, broad audience interest, and meaningful novelty. 6. It keeps every story that meets those criteria instead of forcing a fixed number of recommendations. 7. It ranks the final brief by strength and sends it as one compact Slack DM at 10 AM each day.

I built a local memory system for Claude that is a bit different from others I have seen. The reason was familiar: repeated context loss and gaps, even within projects. I am not technical—I come from a healthcare background—so it was essentially vibe-coded, but I used a method I had not seen elsewhere. I started by interviewing Claude about what would be useful to it, rather than beginning with only what I wanted. The three biggest gaps were the rationale behind decisions, current versus historical states, and the difference between global and project-level detail. We also identified ways memory can go wrong, including stale facts being confidently asserted as truth and rejected ideas resurfacing. Claude’s built-in memory stores flat topics without entity links, captures what but not why, is not well temporally grounded, and is gated by Claude. I researched other memory builds, from homebrew systems to enterprise tools, and found that they generally fell into three groups: - Vector dumps, which lack rationale and supersession and can become stale - Plain Markdown with grep or embeddings, such as Basic Memory, which similarly lacks real temporal grounding and an entity graph - Heavyweight knowledge-graph stacks such as Neo4j, LangChain, and GraphRAG None of these did what I wanted. My store holds entities only, not transcripts. It stores decisions, observations, people, and projects connected by typed edges. Each entry has content, a scope—either portfolio-worthy or working detail for one project—a rationale, and information about where it came from. The system is also bitemporal, so it distinguishes what is current from what is not. Nothing is edited in place: a correction adds a new assertion instead of overwriting the old one. Underneath, it uses SQLite, with sqlite-vec for semantic search and FTS5 for keyword search. Nothing writes automatically. Claude has to propose a memory, and I have to approve it. This prevents the store from filling with noise, keeps it token-efficient, and acts as a governance lever. MCP links Claude to my server. It is local-only at present, although there is potential to add remote access in the future. The server provides instructions for making proposals, so the system is theoretically portable, and I also created a Claude skill to accompany it. I ran the build across multiple projects and created specialist projects for different roles: - A central development and oversight project served as the decision-maker and prompt-writer. - Cowork handled the building and tested each module inside a sandbox. It had no authority to change decisions, and I used a fresh project for each stage of the build. - I handled deployment separately by typing every command on the server and pasting the output back. - I repeated Claude’s Cowork-authored tests on the actual server. Real-world testing after deployment identified only minor issues, which were quick to fix. This separation was administratively heavy because I had to keep switching between projects as tasks started and finished, but it caught several errors in the rules and code. Despite my lack of technical knowledge, the project is now well documented and I have room to develop it further. I may eventually put it on GitHub. It has become a standard component of my workflows, my projects are tracked much better, and Claude and I are on the same page more often.

“Honey, do you remember where Ryan’s practice is? Do you remember our Wi-Fi password? Do you know my TSA PRE number? Remember who that painter was that we used last year?” If you have a family with children, you may hear questions like these all the time. In a large family, there always seem to be questions about the house, the kids, or technology that could be answered more easily. The information is usually stored in different places: password files, a Rolodex of business cards, or sheets of paper in junk drawers. I set out to build an app where anyone in my family could use voice to save something for the future or retrieve something they had already stored. I integrated AI to understand the meaning of each voice note. It might create a calendar event, store a password in a vault, or simply remember a phone number. Then anyone else in the family could access the information. The app uses multi-factor authentication for anything particularly secret. It is not intended to be a dedicated password protector; I would build in much more security if that were the goal. Instead, it is an everyday-life app for remembering the little things: How long is the warranty on this appliance? Which exact light bulbs did we use here last time? What was our daughter’s email address that we needed to set up on her phone? Being able to use voice to enter information or retrieve it was the key for me. I think that will save people time. As I started adding entries and validating the idea, my wife came up with the name. After a few weeks, I knew she was completely right, because I now use it about 10 times a day—and I hear that exact phrase every time. Step-by-step: 1. I identified recurring family questions about locations, passwords, identification numbers, contacts, warranties, and household items. 2. I built an app that lets family members use voice to save or retrieve information. 3. I integrated AI to interpret the meaning of each voice note and determine whether to create a calendar event, store a password in a vault, or remember a phone number. 4. I made the stored information accessible to other family members. 5. I added multi-factor authentication for information that is particularly secret, while keeping the app focused on everyday memory rather than dedicated password protection. 6. I added entries and validated the idea through regular use, eventually using the app about 10 times a day.

I regularly come across long articles, reports, papers, ebooks, and other documents that I want to understand but realistically don’t have time to read closely. Instead of letting them pile up in a reading queue, I change the format and turn them into audio I can consume during time that would otherwise be less productive. Step-by-step: 1. I choose a long article, report, paper, ebook, or other document that I want to understand but don’t have time to read closely. 2. I upload it to Google Notebook (formerly NotebookLM) and add it as a source so NotebookLM can work directly from the material. 3. I generate an Audio Overview. NotebookLM turns the source into a conversational, podcast-style discussion that summarizes and explains the major ideas. 4. I listen while walking, driving, working out, doing chores, or running errands. 5. I follow up on what matters. After listening, I know the main ideas, what I want to investigate further, whether the document is worth reading in full, and which sections deserve closer attention. The result is essentially a personal podcast generated from whatever I need to learn. What I like about this workflow is that it doesn’t require me to find more time. It lets me use time I already have differently. Because the material is turned into a conversational discussion rather than simply being read aloud, I find it easier to stay engaged with dense material. I don’t treat the podcast as a replacement for reading the source when the details really matter. I use it as a comprehension and triage layer. Even when I eventually go back and read the original, I’m starting with a mental model of what’s in it rather than approaching it cold. The broader lesson is that AI doesn’t always need to save time by doing the work for you. Sometimes it can save time simply by changing the form of the work so it fits into your life.

Organic social content is one of the best sources of ideas for ads, so I built a workflow that finds short-form videos performing well in my niches, analyzes why they work, and rewrites the strongest hooks for my brand. Apify scrapes Instagram Reels by hashtag and TikTok videos by keyword across three niches: AI, productivity, and career growth. The workflow filters for English-language videos posted within the last 15 days that are 15–90 seconds long and have more than 50,000 plays. It then ranks them by engagement rate rather than views alone. A simple log file tracks every video I’ve already analyzed, so the workflow doesn’t process the same video twice. ElevenLabs transcribes each video’s audio. Claude then extracts the exact opening line, identifies the hook formula and video structure, and writes a version of the hook for my brand. Everything is compiled into one dated document with the top three discoveries, the strongest hook from the run, and any new patterns I haven’t tried yet. With one command—"Run research"—I get about 20 proven hooks and video structures to test in ads for less than $1 per run. Step-by-step: 1. I use Apify to scrape Instagram Reels by hashtag and TikTok videos by keyword across the AI, productivity, and career growth niches. 2. I filter the results for English-language videos posted within the last 15 days, 15–90 seconds long, with more than 50,000 plays. 3. I rank the remaining videos by engagement rate instead of views alone. 4. I check a log file to skip videos I’ve already analyzed. 5. I use ElevenLabs to transcribe each video’s audio. 6. I ask Claude to extract each video’s exact opening line, hook formula, and structure, then rewrite the hook for my brand. 7. I compile the results into one dated document with the top three discoveries, the strongest hook from the run, and new patterns to test. 8. I run the workflow with the command "Run research" to generate about 20 hooks and video structures for ad testing at a cost of less than $1 per run.

AI agents are much more useful when they can remember important context across sessions. However, giving every agent access to one giant memory creates a different problem: irrelevant information accumulates, context becomes noisy, and agents waste time sorting through details that do not apply to their task. The challenge is not only giving AI memory. It is deciding what should be remembered, which agent should remember it, and where that memory belongs. I use a three-tier memory system that separates knowledge by scope: - Global memory: Information that should be available across the entire AI system - Agent memory: Knowledge specific to an individual specialist and how it should work - Project memory: Decisions, constraints, discoveries, and context that matter only within a particular project Instead of copying everything into every agent’s context, I store information at the narrowest level where it remains useful. Step-by-step: 1. Create a global memory layer for durable information that is useful across many agents and projects, such as important user preferences, shared conventions, and system-wide decisions. 2. Give each specialist its own memory. Store knowledge that helps a particular agent perform its role better, such as recurring preferences, domain lessons, and patterns learned from previous work. 3. Create project-specific memory for decisions, constraints, terminology, discoveries, current state, and other context that belongs with the project rather than in global memory. 4. Classify new information by scope. Whenever something worth remembering is learned, ask: - Does the whole system need this? - Does only this agent need it? - Does it matter only for this project? 5. Store the information at the narrowest useful level. Avoid promoting project-specific details into global memory unless they are genuinely reusable elsewhere. 6. Have agents load relevant memory before they work. A specialist can combine its accumulated knowledge with the current project context instead of starting every session cold. 7. Update memory as important decisions are made. Persist decisions and reusable lessons rather than relying on conversation history to remain available indefinitely. 8. Keep historical artifacts separate from active memory. Run logs, old handoffs, and detailed history can remain available for reference without automatically loading into every future interaction. Instead of treating memory as one giant bucket, I create a hierarchy: `Global → Agent → Project` Each agent gets the context it actually needs while unrelated information stays out of its working context. This provides better continuity across sessions, reduces repeated explanations, keeps context cleaner, and helps AI agents accumulate useful knowledge without requiring every agent to remember everything.

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.

I built a job application workflow that goes beyond finding vacancies and generating generic CVs. First, GPT helps me scan for vacancies that match my practical requirements, interests, skills, and preferred types of work. The more useful part starts when a vacancy looks genuinely promising. I connected GPT to Canva and created several “base CVs” for the sectors and roles I was interested in. Instead of using one universal template, I designed each CV to fit the visual and cultural tone of a particular type of work. For example, a front-desk role, a back-office administrative position, and an assistant role in a creative company may involve overlapping skills, but they communicate very different expectations. Each base CV therefore uses different layout choices, colour use, visual tone, and photo selection. For every version, I review several possible photos and choose the one that best matches the role and the impression I want to convey. When I apply for a specific vacancy, GPT helps turn the relevant base CV into a more personalized version. Instead of rewriting my entire work history, we emphasize the experience, tasks, strengths, and values that are genuinely most relevant to that role. The same applies to motivation letters. Rather than generating a generic corporate letter, GPT uses a tone of voice shaped through months of conversation with me. The goal is for the application to sound recognizably like me while still matching the language, priorities, and culture of the vacancy. Before building this workflow, I did everything manually. For a vacancy that felt worth applying to, I typically spent around two hours refining the CV and motivation letter alone, not including the time spent searching for the vacancy. Even a small typo in the final application email could undermine hours of careful work. Now, once I decide a vacancy is a good fit, the full personalization process takes around twenty minutes on average. That includes selecting the right base CV, adapting the emphasis, refining the letter, checking the tone, and preparing the final application. The workflow works across several layers: vacancy discovery, role and sector matching, base CV selection, adapting experience and values, adjusting visual tone, personalizing the letter, final review, and application. What I like about this approach is that personalization is not limited to inserting keywords from a vacancy. It includes content, visual identity, emphasis, tone, and context. The result is a small family of CVs rather than one document being stretched awkwardly across every possible job. Each version keeps the same underlying career history while presenting the parts that matter most for a particular type of role. The biggest improvement is not only speed but consistency. The workflow reduces repetitive manual rewriting while keeping each application specific, personal, and carefully matched to the role. It turns roughly two hours of manual polishing per strong vacancy into about twenty minutes of collaborative refinement, with fewer opportunities for small final-stage errors to spoil an otherwise strong application. Step-by-step: 1. I use GPT to scan for vacancies that match my practical requirements, interests, skills, and preferred types of work. 2. When a vacancy looks promising, I identify the relevant sector, role, and type of impression I want to convey. 3. I use Canva and GPT to create and maintain several base CVs, each with its own layout, colour use, visual tone, and photo selection. 4. For each base CV, I review several possible photos and choose the one that best fits the role and the impression I want to convey. 5. I select the base CV that best matches the vacancy. 6. I adapt the CV by emphasizing the experience, tasks, strengths, and values that are genuinely most relevant instead of rewriting my entire work history. 7. I use GPT to personalize the motivation letter in a tone shaped through months of conversation with me, while matching the vacancy’s language, priorities, and culture. 8. I check the tone, review the application for small errors such as typos, and prepare the final application. 9. I complete the personalization process in around twenty minutes on average instead of spending roughly two hours on manual polishing for a strong vacancy.