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

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

I ask Claude every month or so to be my Claude Code learning coach by simply typing the /insights command. It provides a hyper-personalized website report card with advice to help me use Claude Code better, with exact examples of where things go wrong, features, and prompts I should try. Step-by-step: 1. I ran the /insights command in Claude Code to analyze how I had been using the tool. 2. I reviewed the personalized website report card it generated, especially the examples of where my workflow was breaking down. 3. I pulled out the recommended features, prompts, and habits that were most relevant to the mistakes I was making. 4. I practiced those recommendations in my normal projects instead of treating the report as generic advice. 5. I repeat the exercise every month or so to see what changed and what I should learn next.

I used Claude to help my brother-in-law build a Shopify website for his e-commerce store. By sharing screenshots, design references, and business requirements, I had Claude generate Liquid code, troubleshoot theme issues, modify page layouts, and explain exactly where changes needed to be made within Shopify. Instead of digging through forums and documentation for every issue, Claude acted like an on-demand Shopify developer, helping with everything. It sped up development, allowing the site to move from concept to launch much faster. Step-by-step: 1. I shared screenshots, design references, and the business requirements for the Shopify store with Claude. 2. I asked it to generate the Liquid code needed for the theme and explain where each change belonged in Shopify. 3. I used it to modify page layouts and translate visual feedback into specific code changes. 4. When theme issues appeared, I brought the errors and screenshots back to Claude for troubleshooting. 5. I repeated that loop until the store moved from concept to a working launch.

Claude created my portfolio website in an instant. I prompted it with my links (LinkedIn and social), described what I wanted, and it built the entire thing in one sitting — design, deployment, DNS config, SEO, and Google indexing included. I made a handful of edits across the session, and it handled every single one without friction. When things broke during deployment, it debugged in real time and fixed them via desktop extension browser control. Zero code written by me. Step-by-step: 1. I gave Claude my LinkedIn and social links along with a description of the portfolio site I wanted. 2. I asked it to build the site’s design and content in one working session. 3. I reviewed the result and made a small number of edits through conversation rather than editing code. 4. I had Claude handle deployment, DNS configuration, SEO, and Google indexing. 5. When deployment broke, I used browser control to let Claude inspect the live problem and debug it in real time.

I've been taking topics I want to learn about (mostly coding docs for new technologies) and giving them to NotebookLM to create customized podcasts for my runs when there aren't interesting podcasts available from the channels I frequent. And it really is actually good and enjoyable, and not just AI slop. Step-by-step: 1. I chose a technical topic I wanted to learn and gathered the most useful documentation for it. 2. I added those sources to NotebookLM instead of relying on a generic podcast. 3. I asked NotebookLM to create a customized audio overview from the material. 4. I listened to the generated episode while running. 5. I repeated the workflow whenever I wanted an engaging podcast for a topic that existing shows had not covered.

I created an agent collaboration system called duo-agents that pairs Claude and Codex to work together on coding tasks... Claude acts as the implementer (coder), then Codex acts as the reviewer (checks and makes edits). They alternate in rounds, communicating through a shared file. The key difference: both agents actually edit files — the reviewer doesn't just leave comments, they make the fixes themselves. Describe your task and watch them iterate until the code is solid. Step-by-step: 1. I created a shared file that both coding agents could use to pass context and decisions back and forth. 2. I assigned Claude the implementer role and had it build the requested change directly in the codebase. 3. I assigned Codex the reviewer role and had it inspect the implementation for problems. 4. Instead of leaving comments, Codex edited the files and made the fixes itself. 5. I alternated the two agents in rounds until the shared task was complete and the code was solid.

I used /goal in OpenAI's Codex to build a Magic: The Gathering app so my brother and I can play asynchronously without needing to coordinate a call or awkwardly play over FaceTime. The idea is to let each of us take turns when we have time, track the board state cleanly, and keep a game going over days instead of trying to line up schedules. The command allowed Codex to continue running until everything was done, basically one-shotting exactly what I was looking for without any intervention. Step-by-step: 1. I defined the core problem: two people needed to play asynchronously without coordinating a call. 2. I described the app’s essential behavior, including turn-taking, persistent board state, and games that continue over multiple days. 3. I used /goal in Codex so the build could continue autonomously toward the finished result. 4. I let Codex implement the app and resolve the work without requiring step-by-step intervention. 5. I tested the finished flow to make sure each player could return later and continue from the correct state.

I'm always looking for ways to add cool motion design to our videos. Recently, I've been playing with Expressions, snippets of JavaScript that automate animations and link properties in After Effects. Previously, I had to dig through forums and Reddit to find the right snippet, but now I describe the effect to Claude, and it gives me options, explaining each line of code. Step-by-step: 1. I described the animation effect I wanted to create in After Effects. 2. I asked Claude for several JavaScript Expression options instead of searching forums and Reddit. 3. I had it explain every line so I understood what the expression controlled. 4. I pasted the best option into After Effects and tested it against the real composition. 5. I brought the result back to Claude for adjustments until the motion behaved correctly.