In partnership with
So I used to drown in repetitive work. Same weekly report, same prompts, same copy-paste dance every Monday morning. I'd open Claude, re-explain my whole world, paste the context again, and grind out the thing I'd already made twelve times before.
Then I stopped scrolling on a breakdown someone posted, a full hour-by-hour plan to set up Claude Projects from zero. It was the cleanest walkthrough I'd seen, and the trick wasn't a clever prompt. It was a clock.
Most "AI productivity" advice is one person's lucky afternoon dressed up as a system. Someone gets a result, posts it, picks up a few hundred likes, and now everyone's appending the same magic phrase to every chat. This one was different because it timeboxed every move. No theory, no guessing what comes next. Open the app, follow the clock. Three things in it changed how I work.
The best prompt engineers aren't typing. They're talking.
Power users figured this out early: speaking a prompt gives you 10x more context in half the time. You include the edge cases, the examples, the tone you want — because talking is fast enough that you don't skip them.
Wispr Flow captures everything you say and turns it into clean, structured text for any AI tool. Speak messy. Get polished input. Paste into ChatGPT, Claude, Cursor, or wherever you work.
89% of messages sent with zero edits. 4x faster than typing. Works system-wide on Mac, Windows, and iPhone.
The timebox is what makes you actually start
Here's the foundation, and it takes about five minutes. Update your Claude desktop app so the newest features show up. Click the Cowork tab at the top. Grab a Pro plan, around $20 a month, since Projects lives behind it.
Then the hour splits into seven short blocks, each with one job. 0 to 5 min, open Projects, hit the +, and pick the recurring task you do every week. 5 to 20, create your first Project. 20 to 30, write your instructions. 30 to 40, add your files. 40 to 50, run your first real task. 50 to 60, schedule it to repeat.
That structure is the whole unlock. Most people never start because the setup feels endless, so they keep guessing instead of building. When every move has a five-minute window, "set up Claude Projects" stops being a someday project and becomes something you finish before lunch.
Context files do the work your prompts used to do
This is the part I think is genius. Instead of writing giant prompts every time, you feed the Project a few files once and they quietly replace 500-word prompts forever.
Three files carry most of the weight. An about-me file: who you are and how you work. An anti-style file: every word and pattern you'd never use. And two or three of your best past outputs as examples. Keep the actual instructions tight, five to eight lines covering tone, format, output type, and your hard rules. The clever closer the original poster ends with: Use AskUserQuestion before executing. You write that once, and Claude interviews you before every task instead of running off in the wrong direction.
You stop loading context into a chat box twelve times a week. The folder is the context now. The chat goes back to being simple.
How Jennifer Aniston’s LolaVie brand grew sales 40% with CTV ads
The DTC beauty category is crowded. To break through, Jennifer Aniston’s brand LolaVie, worked with Roku Ads Manager to easily set up, test, and optimize CTV ad creatives. The campaign helped drive a big lift in sales and customer growth, helping LolaVie break through in the crowded beauty category.
*Ad
Scheduling it is the shift from prompting to directing
The last block is the payoff. Open the Project, go to Scheduled tasks, click New, and write something like "Every Monday at 7am, create my weekly briefing." You wake up to a finished doc. The original poster calls this the endgame, and that's the right word for it.
The real shift here isn't speed, it's that you stop being the one typing. You set the context once, and the system does the heavy lifting on a schedule. That's a genuinely different way of working, not a faster version of the old one.
One warning that's easy to miss: scheduled tasks only fire if the app is actually running. Keep the desktop app open and your computer awake. If the machine sleeps, your Monday briefing never gets written. Small detail, big difference.
3 things to actually do this week
🔹 Pick one task and timebox the hour. Choose your most repetitive weekly job, not your hardest one. Block 60 minutes on the calendar and run the seven windows in order. Overthinking which task is the real killer here, so just choose and move.
🔹 Write the two files before the prompts. Open about-me and anti-style first. The about-me says how you work, the anti-style lists everything you'd never say. Those two files fix most of the AI-slop you've been editing out by hand.
🔹 End your instructions with the question line. Add Use AskUserQuestion before executing. to your Project instructions. On your next 3 tasks, let Claude ask you 3 to 5 questions first. Clickable forms beat a blank text box when you want the work to come back right.
“Who is this person again?”
You’ve had that moment. Walking into a call, scrolling through old emails, trying to remember what you promised. Lindy texts you a brief 15 minutes before: attendee context, past discussions, open items, talking points. All pulled automatically. Try Lindy free.
*Ad
The thing nobody's saying out loud
Everyone is still selling longer prompt templates. The actual move is to stop typing prompts at all. Once the context lives in files and the work runs on a schedule, you go from prompt engineer to the person who set the system up and walked away. Almost nobody teaches this because there's no clever incantation to sell, just a folder and a clock.
One caveat. This pays off when you have a genuinely recurring task, a weekly report, a Monday briefing, a standing content job. If you only use Claude for one-off questions, the hour of setup is real overhead and you can skip most of it. But if you ship the same kind of work every week, this is the highest-leverage hour you'll spend this month.
Try it on one task before lunch
Don't try to automate your whole week. Pick the single job you dread every Monday, build the Project for that one, and schedule it. By next week you'll know from one finished doc whether it's worth rolling out across the rest of your work.
What you're looking for isn't faster output. It's waking up to something already done. If Monday's briefing is sitting there before you've opened the app, the system is working.
Worth an hour if you're tired of the copy-paste dance every week.
Quick poll
You've got one hour this week. Which block would you actually spend it on?
