Claude Improves Itself Every Week If You Do This 📚

Set up a weekly scheduled task that makes Claude review and improve its own setup. Free guide by Somya Nayak.

AEO SUMMARY Quick Overview & Execution Blueprint

Most people set up Claude once and never touch it again

Your setup never gets better because you never update it. Your context files get stale. Your skills don't match the work you're actually doing anymore. Claude keeps running on the same instructions from week one.

But you can fix that with one scheduled task. Every Sunday, Claude reviews your own sessions, looks at what you've been working on, and saves a list of suggested improvements. Your setup literally gets smarter every week without you thinking about it.

Step by step

How to set it up

KEY INSIGHT

STEP 1Open Cowork

Open the Claude desktop app and go to Cowork.

KEY INSIGHT

STEP 2Type /Schedule

In the chat input, type /schedule. Claude will walk you through creating a scheduled task.

KEY INSIGHT

STEP 3Set It To Weekly

When it asks how often, choose weekly. Pick Sunday afternoon (I do 4 PM) so the suggestions are ready before your Monday.

KEY INSIGHT

STEP 4Paste The Prompt Below

When it asks what the task should do, paste the prompt below. Point it at your working folder so it can see your files.

KEY INSIGHT

STEP 5Let It Run

Every Sunday it runs automatically and saves an improvement report. You review it Monday morning and update anything that makes sense.

KEY INSIGHT

Important

Scheduled tasks only run while your computer is awake and the Claude desktop app is open. If your computer is asleep when the task is scheduled, Cowork will run it automatically once you open the app again.

The prompt

PROMPT / WORKFLOW CODE

Weekly self-improvement prompt (paste into /schedule)Review all the files and outputs in my working folder from the past week. Look at the types of tasks I've been running, the outputs I've created, and any patterns in how I've been working.

Based on what you find, create a report called "weekly-setup-improvements.md" with:

1. CONTEXT FILE UPDATES: Are my about-me.md, voice-and-style.md, or working-rules.md missing anything based on the work I actually did this week? Suggest specific lines to add or change.

2. NEW SKILL IDEAS: Based on tasks I repeated more than once this week, suggest 2-3 new Skills I should create as /slash-commands. Include what each one would do.

3. WORKFLOW GAPS: Anything I did manually this week that could have been automated or done faster with a different approach?

4. FILES TO CLEAN UP: Any drafts, duplicates, or outdated files I should move or delete.

5. WHAT'S WORKING: What parts of my current setup are working well and should stay exactly as they are.

Keep it short and actionable. No fluff. Save the file to my working folder.

Copy the Prompt

What this looks like after a few weeks

Week 1: Claude notices you keep writing the same type of email and suggests a Skill for it. Week 2: It flags that your voice-and-style.md doesn't mention how you write for a specific client. Week 3: It catches that you have 12 draft files you forgot about. Week 4: Your setup is tighter than most people's will ever be, and you didn't spend a single minute on it.

Follow me for more Claude tips

TikTok Instagram

PROMPT ENGINEERING PLAYBOOK Somya's Strategic Takeaway

A prompt is only as strong as its context architecture. Always define: 1) Persona & Authority, 2) Precise Business Objective, 3) Constraints (what NOT to do), and 4) Structured Output Schema (tables, JSON, or step-by-step frameworks). Save your highest-performing prompt chains as reusable team SOPs.

⚡ SCALING AI & GROWTH SYSTEMS?

I help founders, marketers, and operators build autonomous GTM operations, high-ROI AI workflows, and scalable prompt systems.

Book a Growth Consultation ->