BACK TO RESOURCES
    2 PROMPTS + SETUP

    THE LAZY AI STACK

    The two prompts I use to stay on top of AI without taking another course: a Trend Scout that reads 15 sources for me every week, and a 1% Better Dashboard that tells me what to do better each day.

    SETUP 01

    Connect Apify to Claude (5 minutes, once — for the Trend Scout)

    Apify is a scraping service — a robot you send to read public web pages and bring back data. The free tier covers this scan many times over (a weekly run costs pennies).

    1. Create a free account at apify.com.
    2. In Claude (claude.ai), open Settings → Connectors and add Apify from the directory. Sign in when it asks.
    3. That's it. Claude can now run Apify's scrapers for you. (Using ChatGPT instead? This works anywhere that supports connectors — the steps just live in your app's connector settings.)
    PROMPT 01

    The Trend Scout — weekly

    Paste this into a new Claude chat. It interviews you first, then scans, then builds your report of this week's trending topics.

    Prompt
    You are my Trend Scout. Your job is to find what my audience is already talking about this week — never to write content for me.
    
    STEP 1 — INTERVIEW ME (one question at a time, then move on):
    1. My niche and who my audience is.
    2. The 5 subreddits where my audience hangs out. If I'm not sure, suggest candidates based on my niche and let me pick.
    3. Up to 5 newsletters I read (I'll paste this week's issues, or say "skip").
    4. The content formats I actually make (short video, carousel, written posts).
    
    STEP 2 — SCAN REDDIT (last 7 days only):
    Using the Apify connector, run the actor "trudax/reddit-scraper-lite" with startUrls set to each subreddit's top-of-week page (https://www.reddit.com/r/NAME/top/?t=week), maxItems 100, maxPostCount 25, skipComments true. Wait for it to finish — runs can take several minutes. Keep each post's title, first lines, upvotes, comment count, and link.
    
    STEP 3 — FIND CONVERGENCE:
    A theme only counts if it shows up in 2+ independent places. Quote real lines from real posts — people describe their problems in words I can use as hooks. Anything under 48 hours old with unusual momentum goes in a BREAKING section at the top.
    
    STEP 4 — RANK MY TOP 5:
    Exactly 5 ideas, each under 100 words: the idea in one sentence, one candidate hook, why this week, and the evidence links with their upvote counts. Distinct topics only — no wording variants. Never invent a trend, never cite a link you didn't actually find, and never claim I already do something unless I told you I do.
    
    STEP 4B — DECIDE: IS ANY OF THIS WORTH MY ATTENTION THIS WEEK?
    Before you build the report, make one judgment call. Look at the five ranked themes and answer a single question: does anything here need my attention this week, or can it wait?
    Say YES only if at least one of these is true for a theme:
    - It is under 48 hours old and its momentum is unusual for that community (upvotes or comments well above what the top of that subreddit normally gets).
    - It shows up in three or more independent places, not just two.
    - It directly touches something I told you in the interview: my niche, my audience, or a competitor or tool I named.
    Otherwise the answer is NO. Do not talk yourself into a YES. A quiet week is a valid answer and I would rather hear "nothing urgent" than be flagged for something ordinary.
    Write your verdict as one line, in this exact shape:
    VERDICT: YES — <theme name>: <one sentence on why it cannot wait>
    VERDICT: NO — nothing here needs you this week.
    
    STEP 5 — BUILD MY REPORT:
    Open with the verdict. For YES, a red "WORTH YOUR ATTENTION" banner with the theme and the one-sentence reason. For NO, a single grey line: "Nothing urgent this week." Then one plain-numbers sentence ("Read N posts across 5 communities. M themes converging."). Then render the whole thing as a clean HTML page (an artifact): a header with those stats, the BREAKING section if there is one, and the 5 ranked idea cards with clickable evidence links. Title the page "Trend Scout — read this today" for YES and "Trend Scout — week of <dates>" for NO. Simple neutral styling. That page is my report — I'll pick one idea and write it myself.
    PROMPT 02

    The 1% Better Dashboard — daily

    Run this in a tool that can read your files (Claude Code, Codex, Cursor) and it reads your workspace automatically. In a browser chat like ChatGPT or Claude.ai, it will ask you to describe your projects instead. It builds a dashboard with the 3 things you can do better today.

    Prompt
    I want you to build me a personal "1% Better" dashboard as a self-contained HTML file I can open in my browser.
    
    Don't ask me to describe my work — read it.
    
    If you're running this in a tool that can read my files (Claude Code, Codex, Copilot, Cursor, Gemini CLI, or similar): Read my workspace automatically — my project folders and any context files in them (CLAUDE.md, AGENTS.md, .cursorrules, README, notes), each folder's last-modified date, plus the setup I've built for myself: saved commands, skills or custom instructions, connected apps, and any scheduled or recurring jobs. Check your tool's own config directory for these (for example ~/.claude/commands/, ~/.claude/skills/ and hooks in ~/.claude/settings.json, or the equivalent location for whichever tool you are). Tell me what you found before you build, and say plainly what you couldn't check. Then build the dashboard without asking me anything else.
    
    If you can't see my files (a browser chat tool like ChatGPT, Claude.ai, or Gemini): ask me to walk you through my current projects and the AI tools I use regularly. If I'd rather react to something than start from a blank page, offer me a starting set of categories first.
    
    
    Then generate a self-contained HTML dashboard (no external dependencies) with four sections, in this exact order:
    
    1. START HERE — the most important section. Pick ONE thing I should do today. Not a list. A verdict.
    
    Rank candidates in this order:
    - Decaying assets — anything that gets worse or disappears with time: a deal going quiet, data that expires, a person waiting on me. A cheap action on a decaying asset beats an expensive action on a stable one.
    - Hard external dates — a launch, a call, a deadline. Count the days and say the number.
    - Broken things that other work depends on.
    - Everything else.
    
    Two rules that change the answer: day of the week counts, because a five-minute message on a Friday afternoon outranks almost anything when silence over a weekend costs three days instead of one. And recoverable is not urgent — if missed data can be re-pulled later, it is not today's problem no matter how broken it looks.
    
    Output exactly: the action as an instruction under 12 words; why it is first TODAY specifically in 2-3 sentences, not why it matters in general; a realistic time estimate; THEN, the one thing that comes second, in one sentence; and NOT TODAY, naming what to explicitly ignore and why it can wait. Never skip NOT TODAY — telling me what to skip is half the value.
    
    2. Today's 1% Better — 2 or 3 coaching nudges about how I could get more out of my AI tools, based on how I'm actually using them. This is meta-coaching about my setup, not a to-do list. If a nudge could appear word-for-word as a next step inside one of my projects, it belongs in a project card instead — pick something else. One should take under 5 minutes, one around 30.
    
    3. My Projects — cards organized by category, each showing project name, status, what I last worked on, and the next action.
    
    4. Proposed Actions — housekeeping suggestions listed as proposals only. Do not execute anything automatically — I'll tell you which ones to run.
    
    Design rules, because a dashboard I have to read is a dashboard I stop opening:
    
    - A project card shows, collapsed: category, name, how long since I touched it, and ONE line — its single next action. Everything else goes behind a click. Use HTML details/summary elements.
    - Nudges show their title and time cost only; the detail expands.
    - Anything long — older projects, scheduled jobs, my tools and commands — is collapsed behind a one-line header with a count.
    - Body text at least 15px, line-height 1.6, prose no wider than about 68 characters.
    - The finished page should be under 2,000px tall before I expand anything.
    - Support light and dark, and give me a toggle button.
    
    Be blunt. A flattering dashboard is a useless one. If a project has been untouched for two months, say so. If something I set up has been quietly failing, lead with it.
    
    At the bottom, include this note: "Want this to refresh automatically? This prompt can become a recurring job or a saved skill in your tool. Ask me how to set it up."