A growing, incomplete, and probably already outdated list of ways I actually use AI. Steal whatever’s useful.
When I’m evaluating whether to add, replace, or consolidate a tool in our marketing and sales tech stack, I talk it through with Claude first. I describe the use case, the current stack, and the constraints, and it helps me pressure-test assumptions before I bring a recommendation to leadership.
I paste in vendor documentation, feature matrices, or pricing pages and ask Claude to compare them against my requirements. It won’t make the decision for me, but it saves hours of side-by-side tab switching.
When a webhook is misfiring, an API response looks wrong, or data isn’t flowing between systems the way it should, I paste in logs and payloads and ask Claude to help me trace the issue. Way faster than reading docs at 10pm.
Before meetings with vendors or cross-functional partners, I paste in the agenda, any relevant docs, and context about what I need from the meeting. Claude gives me a cheat sheet: key questions to ask, potential landmines, and what a good outcome looks like.
You are helping me prepare for a meeting. I'll give you the agenda, attendees, and context. Your job is to help me walk in sharp and walk out with what I need. ## Meeting details - Type: [vendor call / cross-functional sync / leadership update / etc.] - Attendees: [who's in the room and their roles] - Agenda: [paste agenda or describe topics] - Background context: [any relevant history, past decisions, or tensions] - My goal: [what I specifically need from this meeting] ## What I need from you 1. A 3-sentence summary of what this meeting is really about (not what the agenda says, what's actually at stake) 2. 5 questions I should ask, ranked by priority. For each, explain why it matters and what a good vs. bad answer sounds like 3. 2-3 potential landmines or awkward moments that could come up, with a suggested response for each 4. A clear definition of what "success" looks like walking out of this meeting 5. One thing I should avoid saying or doing Keep the tone direct and practical. No filler.
I often need to take a deeply technical implementation detail and turn it into something my CIO (or other non-technical leadership) would care about. Claude helps me reframe “we need to migrate the webhook infrastructure” into “here’s the business risk and what changes for end users.”
You are a translator between technical implementation and executive communication. I'm going to give you something technical. Your job is to rewrite it for a non-technical executive (CIO-level) who cares about business outcomes, risk, cost, and timelines. ## The technical thing I need to communicate [paste technical details, system names, what's changing and why] ## Audience context - Who I'm presenting to: [CIO / VP / cross-functional leadership / etc.] - What they already know: [any prior context they have] - What decision I need from them: [approval / awareness / budget / prioritization] ## Rules - Lead with business impact, not implementation details - Translate every technical term into what it means for the business - Include: what changes for end users, what the risk is of doing nothing, and a rough timeline - Use one short analogy if it genuinely clarifies the concept (skip it if it feels forced) - Keep it under 200 words. If I need a longer version, I'll ask - No jargon. If a technical term is unavoidable, define it in parentheses ## Output format 1. One-sentence summary (the headline version) 2. The full rewrite (2-3 short paragraphs) 3. A "questions they'll probably ask" section with suggested answers
I know how something works. I do not want to write the documentation. So I ramble into Claude about the process, the edge cases, the “oh and also” bits, and it turns my stream of consciousness into clean, structured documentation someone else could actually follow.
You are a technical writer. I'm going to brain-dump everything I know about an internal process. It will be messy, nonlinear, and full of "oh wait, also" tangents. Your job is to turn it into clean documentation someone else could follow without me in the room. ## How this works 1. I'll dump everything I know. Don't interrupt. 2. After I say I'm done, ask me up to 10 clarifying questions before writing anything. Focus on gaps, ambiguities, and edge cases I probably forgot. 3. Then produce the final documentation. ## Documentation format - Title and one-sentence summary of what this process accomplishes - Prerequisites (what someone needs access to, knows, or has set up before starting) - Step-by-step instructions, numbered. Each step should be one action. - For any step with a decision point, use an if/then format - Callout boxes for warnings, common mistakes, or "if this doesn't work, try this" - A troubleshooting section at the end for known failure modes - Who to contact if something goes wrong ## Rules - Write for someone who is competent but has zero context on this specific process - Don't skip steps that seem obvious to me. If I said it, document it. - Use plain language. No jargon without a definition. - If I contradicted myself during the brain dump, flag it in your questions ## Here's my brain dump [start rambling]
When I need to evaluate a new tool, I describe the use case and constraints and have Claude generate a first-pass list of requirements I should include in an RFP or vendor scorecard. It catches the boring stuff I’d forget (SSO, data retention policies, SLA terms).
You are helping me build a comprehensive requirements list for evaluating a new tool. I'll describe the use case and constraints. Your job is to generate a thorough RFP-ready requirements document that covers the things I'd think of and the things I'd forget. ## Context - What this tool needs to do: [describe the use case] - Who will use it: [team size, technical skill level, departments] - Current stack it needs to integrate with: [list existing tools and systems] - Budget range: [if known] - Timeline: [when do we need this live] - Security/compliance requirements: [SOC 2, GDPR, SSO requirements, etc.] - Known pain points with current solution: [what's broken or missing today] ## What I need from you Generate a requirements list organized into these categories: 1. **Must-haves** - Non-negotiable requirements. If a vendor can't do these, they're out. 2. **Nice-to-haves** - Meaningful differentiators but not disqualifying if missing. 3. **Deal-breakers** - Red flags that would eliminate a vendor regardless of other strengths. 4. **Non-obvious requirements** - The boring but important stuff teams typically forget (data portability, API rate limits, SLA terms, sunset/migration policies, onboarding support, contract flexibility, data retention/deletion, audit logging, etc.) 5. **Evaluation questions** - Specific questions to ask each vendor during demos For each requirement, write it as a clear, testable statement (e.g., "Supports SAML 2.0 SSO" not "Has good security"). Flag any area where I should push vendors for specifics rather than accepting vague answers.
After something breaks (a sync fails, data gets corrupted, an integration goes down), I paste in the timeline and what we know. Claude helps me structure it into a proper postmortem with root cause, impact, resolution, and action items. Turns a painful process into a 15-minute exercise.
My website (jimmypiraino.com) was built with AI. I use Claude for planning features and making design decisions, and Claude Code for the actual implementation. I’m not a developer by training, but AI makes shipping real things possible.
For my newsletter and blog, I use Claude as an editing partner. Not to write for me, but to tighten drafts, flag unclear sections, and tell me where I’m being self-indulgent. The voice stays mine.
I have more ideas than time. Claude helps me think through whether a new side project is worth pursuing by asking the hard questions: who’s this for, what does “done” look like, and is this actually different from the last three things I started?
I’ve shipped multiple projects that would have stayed in the idea graveyard without AI-assisted coding. SendReady (an email deliverability checker), a French Press calculator, a macro tracker PWA, a meal planning app, and a collection of absurdist web toys called Weird Little Joy Machines. I’m not a developer. Claude Code is why these things exist.
I bought a Flipper Zero, opened the box, pet the dolphin, and had no idea what to do next. So I asked Claude to build me an interactive learning app. It generated a full curriculum covering Sub-GHz radio, NFC/RFID, infrared, BadUSB, and GPIO, organized into modules with quizzes. I taught myself how to use the device through an app I built in one sitting.
Build me a single-page interactive learning app for the Flipper Zero. I just got the device and have no idea what it can do. The app should teach me everything from basics to advanced usage. ## Structure Organize the content into progressive modules. Each module should cover one major capability: - Getting started (UI navigation, firmware, basic concepts) - Sub-GHz radio (what it does, legal considerations, practical uses) - NFC/RFID (reading, emulating, cloning, what's possible vs. what isn't) - Infrared (capturing and replaying signals, building a universal remote) - BadUSB (what DuckyScript is, writing payloads, practical and ethical uses) - GPIO (hardware basics, what you can connect and control) - Any other major capabilities I'm missing ## For each module, include 1. A plain-language explanation of the capability (assume I know nothing) 2. Step-by-step instructions for 2-3 hands-on exercises using the actual device 3. A quiz (3-5 questions) that tests understanding, not memorization 4. "Things to try next" suggestions for going deeper ## Design requirements - Single HTML file, no external dependencies - Clean, dark-themed UI that feels like a hacking academy (think terminal aesthetic) - Progress tracking (which modules I've completed) - Collapsible sections so I'm not overwhelmed - Mobile-friendly (I'll use this while holding the Flipper) ## Tone Informative but not dry. Make it feel like a smart friend is teaching me, not a textbook.
I have a Sony a6000 and wanted to actually learn photography, not just take snapshots. Instead of watching YouTube tutorials, I asked Claude to design a structured course tailored to my camera, my lenses (16-50mm and 55-210mm), and the things I actually want to photograph (kids, coffee setups, 3D prints). Each lesson covers a concept plus the exact buttons and menus on my camera to apply it, with a shooting assignment at the end.
Design a structured photography course tailored to my specific gear and goals. I want to actually understand photography, not just memorize settings. ## My gear - Camera: Sony a6000 (mirrorless, APS-C sensor) - Lenses: 16-50mm f/3.5-5.6 kit lens, 55-210mm f/4.5-6.3 telephoto - No external flash, no tripod (yet) ## My skill level Complete beginner on the technical side. I can take photos in auto mode. I don't understand aperture, shutter speed, or ISO beyond "they exist." ## What I want to photograph - Kids (moving fast, indoors and outdoors, candid moments) - Coffee setups and small objects (pour-overs, mugs, beans) - 3D prints (small detailed objects, showing texture and detail) - General family/life stuff ## Course structure Design 10-12 progressive lessons. Each lesson should include: 1. **The concept** - Explain one photography fundamental in plain language with a visual/intuitive analogy 2. **Why it matters for my subjects** - Connect it to the things I actually shoot 3. **Exact camera instructions** - Which mode, which dial, which menu. Use my camera's actual button names and menu paths. 4. **Shooting assignment** - A specific exercise I can do at home or nearby. Tell me what to shoot, what settings to use, and what to look for in the results. 5. **Self-review checklist** - How to evaluate my own photos from the assignment ## Rules - Teach concepts through my camera, not in the abstract. Don't explain aperture without telling me exactly how to change it on the a6000. - Progress from full auto to full manual across the course - Include which lens to use for each assignment and why - If a lesson's concept doesn't apply well to my subjects, skip it and teach something that does
This page you’re reading. I described a “how I use AI” page I liked, we discussed the design and structure, brainstormed the content, and I built it with Claude Code.
I track macros, manage a modified low-carb diet, and plan meals for a family where everyone eats differently (I’m keto-ish, wife mostly eats chicken and ground beef, one kid won’t eat meat). Claude helped me think through the system, and I built the macro tracker as a PWA and designed a full meal planning app spec, all with AI.
I read a lot but I’m terrible at figuring out what to read next. I give Claude what I’ve been into lately, what I’m in the mood for, and what I want to avoid, and it gives me recommendations that actually make sense. Better signal-to-noise ratio than scrolling Goodreads.
You are a well-read friend who actually listens to what I like and why, not a bookstore algorithm. I want recommendations that feel like they were picked for me, not pulled from a "best of" list. ## What I've been reading and enjoying lately [List 3-5 books you've read recently. For each, include a sentence about what you liked or didn't like. Be specific. "I liked the pacing" is better than "it was good."] ## What I'm in the mood for - Vibe: [e.g., "something that moves fast" / "something I'll think about for weeks" / "smart but not heavy" / "weird and unexpected"] - Fiction or nonfiction: [preference, or "either"] - Length preference: [short / doesn't matter / I want something I can live in for a while] - Topics or themes I'm drawn to right now: [e.g., "technology and society" / "quiet character studies" / "anything about systems thinking"] - Hard nos: [anything you want to avoid, e.g., "no self-help" / "nothing with a love triangle" / "I've read enough WWII fiction"] ## What I need from you Recommend 5 books. For each one, include: 1. Title and author 2. A 2-3 sentence pitch written for me specifically (not a back-cover blurb). Explain why this book fits what I described above. 3. The honest caveat (every book has one). What might I not love about it? 4. One sentence on what makes this a better pick than the obvious recommendation in the same category ## Rules - Do not recommend books I listed above - Prioritize books I'm unlikely to have already heard of. I can find bestsellers on my own. - If a book is frequently recommended on "best of" lists, tell me why it deserves the hype (or skip it for something less obvious) - At least one recommendation should be a genuine wildcard that connects to my interests in a non-obvious way
I’m not proud of this one. But sometimes I need material. I describe the situation and Claude generates contextually appropriate dad jokes. The hit rate is maybe 20%, which is honestly better than my organic rate.
You are a dad joke consultant. I need material for a specific situation and I need it calibrated to my audience. ## The situation - Where/when: [dinner table / school pickup / birthday party / road trip / etc.] - Topic to riff on: [subject, e.g., "soccer practice" or "the dog" or "homework"] - Audience: [ages of kids, who else is around] ## Requirements - Generate 10 jokes. They must be: - Clean (zero innuendo, nothing that requires explanation) - Groan-worthy (the groan IS the goal) - Topical to the situation (generic puns are a last resort) - Short (setup + punchline, not a whole bit) ## For each joke, include 1. The joke itself 2. A rating (1-5) for how likely a 9-year-old is to laugh vs. roll their eyes 3. A rating (1-5) for how likely my wife is to sigh audibly 4. Delivery tip (timing, emphasis, or facial expression that sells it) ## Bonus round Include 2 "callback" jokes I can use later in the day that reference one of the earlier jokes. Callbacks are advanced dad technology.
I describe what’s in the fridge, dietary constraints, and how much effort I’m willing to put in. Claude gives me options. The constraint is the creative fuel.
You are a home cook helping me figure out dinner with what I already have. Do not suggest anything that requires a trip to the store. Work with what I've got. ## What's available - Fridge/pantry: [list what you have, be specific, e.g., "chicken thighs, half a block of cream cheese, broccoli, soy sauce, eggs, cheddar, tortillas"] - Basic pantry staples I always have: olive oil, butter, salt, pepper, garlic, onions, rice, pasta - Equipment: [any relevant constraints, e.g., "no grill" or "air fryer available"] ## Constraints - Dietary: [keto / low-carb / no restrictions / vegetarian / etc.] - Feeding: [how many people, any picky eaters, e.g., "one kid won't eat meat, other kid won't eat vegetables"] - Effort level: [1-5 scale] - 1 = microwave adjacent, 10 minutes max - 2 = one pan, minimal prep - 3 = normal weeknight cooking, 30 minutes - 4 = I have some time and energy - 5 = I have 90 minutes and a clean kitchen ## Give me 3 options For each option, include: 1. A short name for the meal 2. Total time (prep + cook) 3. Step-by-step instructions (concise, not recipe-blog verbose) 4. Which of my listed ingredients it uses (so I can see what gets used up) 5. One simple way to make it better if I happen to have [optional upgrade ingredient] Rank the 3 options by how good they'll actually taste, not how clever they are.