I used to drown in repetitive work. Same weekly report, same prompts, same copy-paste dance every single Monday. So when I stumbled onto a step-by-step breakdown from an AI professional on LinkedIn, I stopped scrolling. The original poster laid out a full one-hour plan to set up Claude Projects from zero, and it’s the cleanest walkthrough I’ve seen.
What I love about it is the structure. The creator timeboxes every move, so you’re never guessing what comes next. No theory, no fluff. Just open the app and follow the clock. Here’s the breakdown, rebuilt for you.
First, get the setup right
Before any of the steps, this expert is clear about the foundation. You need three things in place, and they take about five minutes total.
- Update your Claude desktop app so the newest features show up
- Click the Cowork tab at the top of the window
- Grab a Pro plan (around $20 a month) since Projects lives behind it
The author calls the Pro plan worth it, and after seeing what scheduled tasks can do, I get why.
The hour, broken into blocks
Here’s where the timeboxing kicks in. The original poster splits the full setup into seven short windows. Each one has a clear job and a reason behind it.
- 0 to 5 min, open Projects. Go to the Cowork tab, click Projects, then hit the ‘+’ button. You’ll get three choices: start from scratch, import an old Project, or use an existing folder. The creator’s advice is to pick the recurring task you do every week. This is where most people freeze up, so just choose and move on.
- 5 to 20 min, create your first Project. Each starting option does something different. Start from scratch spins up a brand new folder. Import a Claude Project pulls in old files plus instructions. Use existing folder taps into your Cowork memory and rules. The mind behind this says pick one and build more later. No need to do everything at once.
- 20 to 30 min, write your Project instructions. Keep them tight, five to eight lines max. The expert suggests covering tone, format, output type, and your hard rules. The clever closer: end with “Use AskUserQuestion before executing.” You write this once, and it runs every single time.
- 30 to 40 min, add files to the folder. This is the part I think is genius. Instead of writing giant prompts, you feed the Project context files. The author recommends an about-me file (who you are and how you work), an anti-style file (every word you’d never use), and two or three of your best past outputs as examples. These files quietly replace 500-word prompts forever.
- 40 to 50 min, run your first real task. Start with a setup prompt: “Read every file in this folder. Summarize what you know about this workspace.” Then follow with “I want to [your task]. Ask me questions first.” Claude generates clickable forms to guide you. The creator frames this as the shift from prompting to directing.
- 50 to 60 min, schedule a recurring task. Open the Project, go to Scheduled tasks, and click New. Try 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 honestly, that’s the whole payoff.
Why it matters: the real shift here isn’t speed, it’s that you stop being the one typing prompts. You set the context once, and the system does the heavy lifting on a schedule. That’s a different way of working entirely.
The pro tip you can’t skip
This contributor adds one warning that’s easy to miss. Scheduled tasks only fire if the app is actually running. So keep the desktop app open and your computer awake. If the machine sleeps, your Monday briefing never gets written. Small detail, big difference.
Why this approach clicks
The thing I appreciate about this savvy professional’s method is the rationale baked into every step. You’re never just clicking buttons. You learn why short instructions beat long ones, why context files outperform mega-prompts, and why ending with a question prompt keeps Claude from running off in the wrong direction.
A few takeaways worth holding onto:
- Pick one task first. Overthinking is the killer. Choose your most repetitive weekly job and build around that.
- Front-load your context. The about-me and example files do the work your prompts used to do.
- Let Claude ask you things. Clickable forms beat blank text boxes when you want accuracy.
- Automate the boring stuff. A recurring task means the work happens whether you remember it or not.
I think the timeboxing is what makes this stick. An hour feels doable. Most people never start because the setup feels endless, but this expert proves you can go from nothing to a self-running workspace before lunch.
Want the exact wording and the full flow? Check out the original LinkedIn post for the complete walkthrough.