YsZ

[Alex Finn @AlexFinn]

Hermes is the most powerful AI agent on Earth right now

I've used it for over 100+ hours the last few months. NOBODY has used it more

In this video I cover EVERY single lesson learned. From which model to use, to best security practices

The only Hermes vid you'll ever need:

[Eliana @eliana_jordan]

they don’t know fable 5 is back

[Matt Pocock @mattpocockuk]

The "should you read code" debate is dumb because the real decision isn't binary, it's a scale:

1. Reading every line of every diff
2. Scanning every diff, reviewing important lines
3. Ignoring diffs but understanding the 'why' of every PR
4. Spot checking PR's instead of reading every one
5. Ignoring PR's, but doing regular spot checks on the codebase
6. Ignoring the code, but spot checking agent traces to help improve the system
7. Ignoring both the code and the system, let models handle everything

Where are you on the scale?

[ClaudeDevs @ClaudeDevs]

Boris sat down with Spotify VP of Engineering Niklas Gustavsson.

Spotify ships 4,500 production deploys a day, and 73% of PRs are now AI-assisted.

[Boris Cherny @bcherny]

As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes:

1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship
2. Builder: quickly turns a prototype/idea into production-grade product/infra
3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance
4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit
5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales

Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS.

A healthy team needs a mix of these, depending on the product:

- A product that is new and pre-PMF needs people that are strong at 1+2+3
- A product that is growing and has found PMF needs 2+3+4 and some 5
- A product that has strong PMF needs 3+4+5 and some 2

Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?

[Codez @0xCodez]

This is an official ANTHROPIC 33-page PDF blueprint for building "Effective AI Agents."

Not theory. Architecture patterns with real case studies from Claude, Coinbase, Stripe, Intercom, and others.

Perceive → Decide → Act → Evaluate → Repeat

Five patterns, from simple to complex:

• Single agent: one model in a loop. Handles 80% of use cases. Don't over-engineer.

• Sequential workflow: fixed steps, each agent hands off to the next. Predictable and auditable.

• Parallel workflow: fan out tasks across agents at once, merge results. Speed through concurrency.

• Hierarchical: a supervisor delegates to specialists. Like a team lead managing experts.

• Evaluator-optimizer: one agent generates, another pushes back. 2-4 cycles until quality is met.

The key insight:

multi-agent systems outperform single agents by 90.2% on complex tasks. Match complexity to value.

Read it now, then explore the article on agentic "Loop engineering" below.

[Codez @0xCodez]

Claude Code creator:

“100% of my code has been written by Claude since Opus 4.5.

most of my coding routine is automated by loops & dynamic workflows"

In this 40-minute video, Boris shares how to build a self-improving agentic setup from scratch.

Loops + dynamic workflows + auto mode + routines - that’s the secret.

Worth more than a $500 vibe-coding course.

Watch today, then read below to learn how to build the same workflow.

[Laravel News Links @LaravelLinks]

Composer Update Is Not Safe Anymore
https://t.co/lv4pw6pwm6

[Matt Pocock @mattpocockuk]

Announcing mattpocock/skills v1

- Achieved a 63% reduction in token cost for skill descriptions
- Split skills into model-invocable and user-invocable skills, adding /codebase-design, /domain-modeling, and /grilling
- (UPDATED) /writing-great-skills - rewritten from the ground up, encoding my skill-writing best practices
- (UPDATED) /diagnose -> /diagnosing-bugs - now model-invocable, awesome for fixing hard bugs
- (NEW) /ask-matt: a router skill that teaches you how all the engineering skills work together

[YsZ @ghostza1209]

@mattpocockuk Are you using Opus?

[Rahul @sairahul1]

https://t.co/uRsQBBhTcH

[Chrome @0xchromium]

Andrej Karpathy spent 2h showing how he actually uses AI day to day

he's a co-founder of OpenAI and led AI at Tesla, so when he shows how he works, it’s worth watching

and the whole session is just him telling the machine what he wants in simple terms, like he's briefing a coworker

watch what's actually happening the entire time:

> he describes the task in normal words
> it goes off and does the work
> he glances at the result and nudges it with one more sentence

that's the whole skill, and you've had it since you learned to talk

the only gap between that and a worker that runs on its own is handing that sentence a schedule and the tools to act

check his work, then build the version that keeps working when you stop

[darkzodchi @zodchiii]

Anthropic CEO Dario Amodei:

"The cheapest way to use Claude is also the smartest. Most devs do the exact opposite."

In 36 minutes, he breaks down the real economics behind every Claude model, and why running them all the same way is a mistake.

Watch the full interview, then save the config below 👇

[Ck Cheong @ckfastwork]

Not financial advice.

ผมเพิ่งขาย Micron ออกอีกครึ่งหนึ่ง ขาย Intel ออกครึ่งหนึ่ง ขาย AMD ออกครึ่งหนึ่ง และขาย Google ออก 25% เพื่อที่จะซื้อ BTC ในราคานี้ครับ

[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 this manually

watch the session, then save the guide below

[Rohit @heyrohitai]

🚨 Anthropic just showed a 27-minute workshop on how to actually do prompts for Claude.

Taught by the people who built it.

Free. No registration. No paywall.

I've seen $300 courses that don't cover what they teach in the first 8 minutes.

Watch it and bookmark it now.

[Addy Osmani @addyosmani]

https://t.co/jKCIAEzai7

[Laravel @laravel]

Your AI agent can only move as fast as what it can understand.

This is why @enunomaduro built Laravel PAO (PHP agent-optimized output). PAO gives PHPUnit, Pest, PHPStan, and Rector output as structured JSON so agents know exactly where to look.

Already building with Laravel? Install it with composer require 𝚕𝚊𝚛𝚊𝚟𝚎𝚕/𝚙𝚊𝚘 --𝚍𝚎𝚟. New Laravel apps include it by default.

https://t.co/wxtGcImls3

[dunik @dunik_7]

40% of the code Claude writes for you is wasted. you're paying for the rewrite.

a 65-line markdown file fixes it. 120,000 developers have starred it.

the author tested it on "30 codebases over 6 weeks" and reported a mistake rate drop from 41% to either 11% or 3%

depending on whether you read the headline or the body.

the irony is that the article is right.

CLAUDE.md is the most under-leveraged file in your stack.

65 lines of behavioral rules outperform a 4,000-token preferences dump.

"be careful" is useless. testable imperatives are gold.

"be senior" doesn't work Claude already thinks it is.

the 4 rules that ship the most leverage:

/ state assumptions, never guess silently
/ minimum code, nothing speculative
/ surgical changes, don't refactor adjacent code
/ define success, loop until verified

compliance: ~80%. mistake rate: from ~40% to single digits.

no human caught the contradicting numbers in the title.

nobody had to.

[Mayank Agarwal 💡 @TheAIWorld22]

Anthropic just showed a 24-minute workshop on how to actually prompt Claude.

Taught by the people who built it.

Free. No signup. No paywall.

I've watched $300 courses that don't cover what they teach in the first 8 minutes.