🧱 Component testing in Playwright has a new shape: stories & galleries.
✍️ A story wraps your component in one scenario — props, providers, mock data — in a *.story.tsx file next to the component.
🖼️ A gallery page, served by your own dev server, renders stories on demand — React, Vue, Svelte, Solid, anything.
Using @playwright/experimental-ct-*? Give the new model a try and tell us how it goes:
👉 https://t.co/r2Q4aNjve1
Docs: https://t.co/TmJ1Q8zr6y
Anthropic just dropped 5 workshops, revealing the latest capabilities of Fable 5:
• 00:00 - deep look into Fable 5
• 11:22 - Fable 5 and the capability curve
• 30:54 - building managed agents with Fable 5
• 44:29 - real use cases of Fable 5 by teams
• 57:43 - how to deploy agents with Fable 5
These 1-hour of sessions will replace 100 articles on how to actually use Fable 5.
Watch them today, then read the best practices from the sessions in the article below.
Prompt engineering is dead.
Anthropic recently released the real playbook for building AI agents that actually work.
It’s a 30+ page deep dive called The Complete Guide to Building Skills for Claude and it quietly shifts the conversation from “prompt engineering” to real execution design.
Here’s the big idea:
A Skill isn’t just a prompt.
It’s a structured system.
You package instructions inside a SKILL .md file, optionally add scripts, references, and assets, and teach Claude a repeatable workflow once instead of re-explaining it every chat.
But the real unlock is something they call progressive disclosure.
Instead of dumping everything into context:
• A lightweight YAML frontmatter tells Claude when to use the skill
• Full instructions load only when relevant
• Extra files are accessed only if needed
Less context bloat. More precision.
They also introduce a powerful analogy:
MCP gives Claude the kitchen.
Skills give it the recipe.
Without skills: users connect tools and don’t know what to do next.
With skills: workflows trigger automatically, best practices are embedded, API calls become consistent.
They outline 3 major patterns:
1) Document & asset creation
2) Workflow automation
3) MCP enhancement
And they emphasize something most builders ignore: testing.
Trigger accuracy.
Tool call efficiency.
Failure rate.
Token usage.
This isn’t about clever wording.
It’s about designing an execution layer on top of LLMs.
Skills work across Claude, Claude Code, and the API. Build once, deploy everywhere.
The era of “just write a better prompt” is ending.
Anthropic just handed everyone a blueprint for turning chat into infrastructure.
Download the guide here: https://t.co/Bf3j0GFRGu