Yellareddy

Global Partner Delivery Community Leader, SAP BTP @SAP | Blogger | Photographer | Proud dad | Football & Cricket enthusiast | FPL Manager | Views are my own

[darkzodchi @zodchiii]

Boris Cherny, creator of Claude Code:

"Fable 5 does in a day what used to take your team a month. Most people will keep using it wrong."

In 12 minutes he explains why Fable 5 needs less prompting than any model before, and why your old detailed prompts now work against you.

Watch it, then save the exact config below 👇

[Anatoli Kopadze @AnatoliKopadze]

Anthropic engineer:

"You can build 5 assistants in one afternoon. Each one handles a task you've been doing manually every single day."

In 45 minutes he shows exactly how to do it from scratch, step by step.

Most people are still doing all of this by hand.

Watch the session, then save the guide below.

[Movez @0xMovez]

Ex-Google engineer explained AI agent loops, harness, evals in 20 minutes - better than 500$ courses.

trace every run → judge it with an LLM → diagnose → fix → ship.

That loop is how agents self-improve over time.

Agent loops + memory + harness + evals - thats the stack.

Watch it, then save the framework below.

[Yarchi @undefinedKi]

ANTHROPIC JUST OPEN-SOURCED 11 PLUGINS THAT TURN CLAUDE INTO YOUR WHOLE BACK OFFICE

These plugins turn Claude into an actual coworker for your job, whatever your job is.

Repo: /anthropics/knowledge-work-plugins

Anthropic built and shipped 11 plugins, the same ones inspired by how their own teams work. One for each role:

Sales, Marketing, Engineering, Data, Design, Product, HR, Support, Productivity, and more. Each one comes loaded with the real workflows that role needs.

The sales one researches prospects, preps your calls, reviews your pipeline, drafts outreach, builds competitive battlecards. The data one writes your SQL, explores datasets, builds dashboards. The productivity one learns your people, your projects, your shorthand, so you say "ask Todd to do the PSR for Oracle" and Claude knows exactly who and what you mean.

They work standalone right away, and get supercharged when you connect your tools (Slack, Notion, HubSpot, Linear, Figma, Snowflake, whatever you use).

This is straight from the people who build Claude. Not a third-party copy.

Bookmark this

[Rahul @sairahul1]

🚨 Anthropic's CEO: "software engineering will be fully automated in 12 months."

two types of people right now:

type 1: opens Claude, types something, gets an answer, closes the tab. thinks they're using AI.

type 2: knows the hidden features, settings, and shortcuts. runs Claude like a power tool.

type 1 gets surprised in 12 months.
type 2 built the advantage already.

bookmark this. read it today.

[Anatoli Kopadze @AnatoliKopadze]

Google Brain founder, Andrew Ng:

"100% of my tasks are done by ai agents, self-improving loops are next.

Give it 3-6 months and prompting is gone."

31 minutes of clear explanation on building self-improving agents from scratch.

Worth more than any $500 agentic course.

Watch it, then read the full guide on loops below.

[Anatoli Kopadze @AnatoliKopadze]

https://t.co/AAWIZD1pNL

[Rahul @sairahul1]

Andrej Karpathy: "90% of Claude's mistakes come from missing context, not a weak model."

41% mistake rate without a CLAUDE.md. 11% with the 4-rule baseline. 3% with the 12-rule version below

here are the 12 rules senior engineers settled on:

1. think before coding: state assumptions, don't guess. the model can't read your mind, stop hoping it will

2. simplicity first: minimum code, no speculative abstractions. the moment you let Claude add "for future flexibility," you've added 200 lines you'll delete next quarter

3. surgical changes: touch only what you must. don't let it improve adjacent code, that's how PRs blow up

4. goal-driven execution: define success criteria upfront, loop until verified. without them Claude either loops forever or stops too early

5. use the model only for judgment calls: classification, drafting, summarization, extraction. NOT routing, retries, status-code handling, deterministic transforms. if code can answer, code answers

6. token budgets are not advisory: per-task 4000, per-session 30000. by message 40 of a long debug, Claude is re-suggesting fixes you rejected at message 5

7. surface conflicts, don't average them: two patterns in the codebase? pick one. Claude blending them is how errors get swallowed twice

8. read before you write: read exports, callers, shared utilities. Claude will happily add a duplicate function next to an identical one it never read

9. tests verify intent, not just behavior: a test that can't fail when business logic changes is wrong. all 12 of Claude's tests can pass while the function returns a constant

10. checkpoint every significant step: Claude finished steps 5 and 6 on top of a broken state from step 4. nobody noticed for an hour

11. match the codebase conventions: class components? don't fork to hooks silently. testing patterns assumed componentDidMount, hooks broke them without surfacing

12. fail loud: "completed successfully" with 14% of records silently skipped is the worst class of bug. surface uncertainty, don't hide it

what actually compounds instead of the next framework:

- the CLAUDE.md file as institutional memory across sessions
- eval-driven changes, not vibe-driven
- checkpoints over speed
- explicit conflicts over silent blending
- discipline over framework, every time
- one repo, one rules file, no exceptions

you don't need a better AI

you need better context engineering

complete playbook below ↓

[Rahul @sairahul1]

Claude Code's creator said something that stopped me cold:

"I don't prompt Claude anymore. I write loops — and the loops do the work. My job is to write loops."

Most developers are still crafting the perfect prompt.

The person who built the tool moved past prompting entirely.

In 30 minutes Boris reveals his actual daily Claude Code setup.

Claude Code + loops + dynamic workflows.

Worth more than any $500 vibe-coding course.

Watch it.

Then read this - everything you need to know about loops to actually apply what he says ↓

Bookmark both. This is your weekend.

[Anatoli Kopadze @AnatoliKopadze]

Claude Code creator:

"I don't prompt Claude anymore. I have loops that figure out what to do. My job is to create loops."

in 30 minutes Boris breaks down his daily Claude Code setup, step by step

the person who built the tool doesn't use it the way most people think

no prompts, no chat box, just loops running on their own

I broke down 17 Claude features most people have never found

full guide in the post below

[Khairallah AL-Awady @eng_khairallah1]

Anthropic engineer:

"You're not supposed to prompt Claude. You're supposed to build a system that prompts itself."

this is one of the best workflows I've seen in a long time

in this video he breaks down exactly how most people are using Claude:

- the 14% you lose to CLAUDE.md before typing a word
- the plugins that 95% of users have never installed
- the caching setup that keeps it at 95% hit rate and almost free
- why starting every chat from zero is the slowest way to use Claude

if you've been using Claude for more than a month and never left the chat window, you've been using one project when you could be running a team of them

instead of another show tonight, watch this

make sure to bookmark it before it gets lost in your feed

full guide in the article below

[Khairallah AL-Awady @eng_khairallah1]

Anthropic engineer:

"You're not supposed to prompt Claude. You're supposed to build a system that prompts itself."

this is one of the best workflows I've seen in a long time

in this video she breaks down exactly how most people are using Claude:

- the 14% you lose to CLAUDE.md before typing a word
- the automation workflows most users don't know exist
- the daily task pipelines that run without touching the keyboard
- the daily workflows Anthropic's own engineers automated first

if you've been using Claude for more than a month and never left the chat window, you've been using one agent when you could be running a team of them

instead of another show tonight, watch this

make sure to bookmark it before it gets lost in your feed

the guide is in the article below

[‏عادل | مبرمج @AdelDeveloperX]

رئيس Google السابق قلب السوشيال ميديا في تصريحاته عن الذكاء الاصطناعي!🤯

الراجل اعترف بإن عمل الثروة دلوقتي بقى سهل جداً لو دخلت المجال ده!

لو قدامك 30 يوم بس عشان تبدأ وتنفذ النصيحة دي وتدخل المجال ده بقوة، دي الخريطة الكاملة والأدوات اللي هتحتاجها من الصفر وكلها مجانية 100%:

احفظ البوست ده فوراً عشان ما يضيعش منك!

- معمارية الـ Agents: عشان تفهم إزاي تبني عميل ذكاء اصطناعي ذكي ومستقل
https://t.co/b7wYpaeSKK

- كورس Claude Code 101: البداية الأساسية للتعامل مع أداة أنثروبيك البرمجية المرعبة
https://t.co/vMzkOO4nAw

- تطبيق عملي وتجارب حية للأداة (Claude Code في العمل)
https://t.co/GY1ZaolS2U

- هندسة الأوامر (الرسمي): الدليل الرسمي من أنثروبيك لكتابة برومبت احترافي
https://t.co/R6L7r8JiVN

- كورس البرومبت التفاعلي: تدريب عملي على الجيت هاب لتطوير مهاراتكhttps://t.co/zx1NZ8ciKG

- ملف CLAUDE.md وإضافة الذاكرة: إزاي تخلي Claude يفتكر سياق مشروعك وما ينساش
https://t.co/tIqsKA1fPX

- المهارات (Skills): علم كلوود خطوات تكرارية ووظائف مخصصة يعيد استخدامها
https://t.co/vmFzPWM2E4

- بروتوكول الـ MCP: اربط Claude بأدواتك اليومية زي Slack و GitHub و Google
https://t.co/5jIEYkFSo2

- الروتين (Routines): أتمتة كاملة للمهام والوظائف عشان تشتغل 24 ساعة في اليوم بدون تدخل منك
https://t.co/zp3r05voly

- الدليل الشامل لـ Claude Code: دليل جبار ومفتوح المصدر من مجتمع المطورين
https://t.co/TaUVI9gmWG

- مكتبة Awesome Claude Code: تجميعة لأفضل السكربتات، الـ Skills، والإضافات
https://t.co/O3iYIjahgF

- أكاديمية أنثروبيك: كل الكورسات الـ 13 الرسمية من الشركة مع شهادات مجانية
https://t.co/6f9KODMPr0

- الوثائق الرسمية بالكامل: المرجع الشامل والنهائي لكل صغيرة وكبيرة في Claude https://t.co/IYGo0G3keP

كل المصادر دي مجاني تماماً ومش هتكلفك دولار واحد.

لايك وفولو واحفظ البوست عشان يوصلك كل جديد!

[MindBranches @MindBranches]

this article currently has 185M views

How to fix your entire life in 1 day

article summary in 4k dark mode

[Khairallah AL-Awady @eng_khairallah1]

Anthropic engineer:

"You're not supposed to prompt Claude. You're supposed to build a system that prompts itself."

this is one of the best workflows I've seen in a long time

in this video she breaks down exactly how most people are using Claude:

- the 14% you lose to CLAUDE.md before typing a word
- the plugins that 95% of users have never installed
- the workflows that run without you typing a single prompt
- why typing one prompt and closing the tab is leaving 90% on the table

if you've been using Claude for months and still start every session from scratch, you have at least 28 untouched features. probably 30

instead of another show tonight, watch this

make sure to bookmark it before it gets lost in your feed

full guide in the article below

[darkzodchi @zodchiii]

Anthropic engineer:

"You can build 5 assistants in one afternoon. Each one handles a task you've been doing manually every single day."

In 45 minutes he builds 5 focused agents from scratch on camera.

Most people are still doing code review, testing, and documentation by hand every single day

Watch the session, then save all templates below 👇

[Yarchi @undefinedKi]

I FED CLAUDE 6 MONTHS OF REDDIT COMPLAINTS AND IT HANDED ME A PRODUCT NOBODY ELSE WAS BUILDING

The hardest part was never building. It was knowing what to build. And the answer is sitting in public while everyone else guesses

Here is the exact process:

1. Scrape. Claude Code plus Reddit's API (the PRAW library) pulls the top posts and comments from your target subreddits. Run it overnight

2. Store. Dump it raw into a JSON file for a few hundred comments, or SQLite if you are pulling thousands. This is the database Claude reads from

3. Segment. Point Claude at the file. It sorts every comment into pain, fear, need, objection, plus two lists, requested features and complaints about competitors. Output to a clean markdown doc

4. Portrait. From that doc, Claude writes a one-page customer profile in their exact words and tone

5. Edge. Claude pulls the 3 most-requested fixes from the complaints. That is your product spec, built from demand, not guesses

6. Ship. Claude Code builds the landing page from the portrait. Deploy free on Vercel

7. Validate. Real participation in the subreddits or a small ad to the page. Watch signups, or back to step one

Everyone builds first and hunts for customers after. Do it backwards

Bookmark this

[Mayank Agarwal 💡 @TheAIWorld22]

ANDREJ KARPATHY COULD HAVE CHARGED $2,000 FOR THIS COURSE.

He put it on YouTube.

The full training stack. Tokenization. Neural network internals. Hallucinations. Tool use. Reinforcement learning. RLHF. DeepSeek. AlphaGo.

3 hours of the most comprehensive LLM education that exists anywhere at any price.

Not how to use the tools.

How the entire system was built from the ground up and why it behaves the way it does.

The engineers who understand this build things the ones who only use the tools cannot even conceive of.

The gap between those two groups is not 3 hours.

It is everything those 3 hours quietly unlock for the rest of your career.

[0xMarioNawfal @RoundtableSpace]

ANTHROPIC DROPPED A 37 MINUTE GUIDE ON BUILDING PRODUCTION AI AGENTS

[Ai With Piyas @piyascode9]

🚨 SHOCKING: An ex-Anthropic researcher just leaked the exact internal prompting framework the team uses.

Most people treat Claude like a basic chatbot and leave 60–70% of its reasoning power on the table.

These 10 prompts are how the pros actually use it — tested internally for maximum clarity, honesty, and depth.

Copy-paste ready. Zero fluff.

Save this thread. Your Claude game is about to change forever.

(Pro tip: use them in order for compound results)