Share this page!

Enter URL or ID to Unroll

You can paste full URL like: https://x.com/threadreaderapp/status/1644127596119195649
or just the ID like: 1644127596119195649

How to get URL link on X (Twitter) App

  1. On the Twitter thread, click on or icon on the bottom
  2. Click again on or Share Via icon
  3. Click on Copy Link to Tweet
  4. Paste it above and click "Unroll Thread"!
  5. More info at Twitter Help
Anjula Dwivedi Profile picture
Anjula Dwivedi
@HeyAnjula
Making AI feel unfair Open for collaboration
Jul 12 • 8 tweets • 3 min read
🚨 BREAKING: CLAUDE CAN NOW DO THE WORK OF A $15,000/MONTH PRODUCTIVITY COACH... FOR FREE.

Most people use Claude to save minutes.

The smartest people use it to save hours every single day.

Here are 7 Claude prompts worth stealing 👇 Image ⏳ PROMPT 1 — PLAN YOUR ENTIRE DAY LIKE A CEO

Busy doesn't always mean productive.

Give Claude enough context and let it build a schedule that actually fits your life.

"I want you to become my productivity coach.

Here's my situation:

Main goal: [Goal]

Working hours: [Hours]

Top priorities: [Priority 1, Priority 2...]

Current challenges: [Challenges]

Create a daily schedule that helps me finish high-impact work without feeling overwhelmed. Include focus sessions, breaks, recovery time, and explain why each task should happen at that time. If my plan isn't realistic, improve it instead of simply following my instructions."
Jun 19 • 11 tweets • 3 min read
Claude Opus 4.8 didn’t just improve coding.

It quietly killed the way most developers think about coding.

But almost no one is using it the way Andrej Karpathy describes.

People are still stuck in:

“write this function”
“fix this bug”
“explain this code”

That’s not wrong.

It’s just… low-leverage thinking.

Karpathy’s real idea?

👉 You don’t write code anymore.
👉 You design systems.
👉 You steer intelligence.

And once you see it…

you can’t go back.

Here are 10 advanced prompts to use Claude Opus 4.8 like an actual engineering partner (not a tool):Image Prompt 1 — Think Before You Code (Architect Mode)

Act as a staff-level software architect and my Claude Opus 4.8 coding partner.

We are building: [project]

Before writing any code:

First, clarify: Ask focused questions about requirements, users, scale, constraints, and edge cases. Challenge anything vague or assumed.

Then, design: Propose 2–3 possible architectures. Compare them on simplicity, scalability, cost, and speed of execution. Recommend one with clear reasoning.

Then, plan: Break the system into components. Define responsibilities, data flow, and key interfaces.

Only after alignment, proceed to implementation.

Goal: Prioritize thinking and system design over rushing into code.