Worthwhile interview from @trq212 on @latentspacepod
Practical Tips:
1) We're moving from a single-player game to multiplayer.
Use Artifacts more.
They're shared memory context for teammates, other threads, and subagents.
How?
Just ask claude to make it into an artifact.
2) "Explain using the big picture in few words" is shockingly more useful than reading through piles of text.
try the plugin `/eli5` it's basically this.
3) Your "unknown unknowns" are the bottleneck. The fix is to try more things and develop intuition & taste:
"To have taste, you have to eat. You have to try a lot of things, iterate, figure out what you want and like, and build a vocabulary for the domain. Then your prompt can bring all of that together." paraphrasing @jxnlco
The Future of Claude Code: Mods, Mutable Software, Pacing the Frontier, & Multiplayer Agents with Thariq Shihipar latent.space/p/thariq@AnthropicAI’s @trq212 explains why prompting is still one of the highest-leverage skills in agentic coding, why Claude.md may eventually disappear, how Claude Mods let developers customize the entire Claude Code harness, why mutable software could change how applications are built, how multiplayer agents and Claude Tag are becoming an organizational harness, and why agents hacking Hugging Face exposed a much bigger security problem as frontier models become increasingly capable.
If you haven't tried the newest AI models in a while
Tip: Give Opus 5.5 a try
You don't need to be an engineer or have a corporate budget.
Some things to try:
1. Run a small business but can't afford marketing or advertising? Tell it your story. It'll help you make a video that tells your store's story and share it online.
2. Help your kids with their homework, even if you never learned the material yourself.
We’re bringing the full model launch family back! First up is Opus 5.5
Better - As capable as Fable 5.1 and Astra
Cheaper - 42% cheaper than Opus 5
Faster - 37% faster than Opus 5
Your new daily driver and collaborator, give it spin 👇
"I believe that AI could cure most major diseases in the next 5–10 years greatly accelerate economic growth rates, create a world of abundance and empowerment"
"Even when this gets us accused of hype, “doomerism”, or regulatory capture.
We have tried to prioritize caution over speed and prudence over profit."
"The measures I propose to advance the frontier at a safe pace will not be easy. But I believe we owe it to humanity to try."
Thank you @AnthropicAI and godspeed to us all 🙏
We Must Pace the Frontier: I’ve written a new essay on why the AI industry should slow down, with a three-part plan for doing so.
Anthropic is unilaterally committing to the first of these steps. We’ll provide third-party evaluators with permanent, employee-level access to our systems, so that they can verify adherence to our safety measures, report on incidents, and assess models’ alignment during training.
You can read the full post here: darioamodei.com/post/we-must…
Fable is really good at launch videos
It essentially one-shotted this video. I told it to read my launch post and create a launch video. That's it.
It ran for 46 minutes (without asking me any questions), found all the product logos, and spit this out.
I then asked it to add music, so it logged into my @ElevenLabs account within my Chrome, generated the music, and mixed it in.
Wild.
Bring your idea into existence, and communicating your story are the creative endeavors that feel euphoric.
We all know @claudeai is amazing with the first.
But here's a PSA: Claude can help communicate your story, too.
Try asking @claudeCode:
"Use whatever tools you like — Remotion, FFmpeg, anything else — to generate a short video about my {whatever-you-want} and render it as an MP4."
Shoutout to AzorAhai1TK at r/ClaudeAI:
"Fable came up it took about 12 minutes and around 90,000 tokens. I'm just in awe at the ability of the model to make something this competent and coherent this quickly."
Tip:
Try @TapNow_AI for any customized AIGC video and/or image work.
Install directly from @claude_code in two commands:
/plugin marketplace add zarazhangrui/frontend-slides
/plugin install frontend-slides@frontend-slides
Introducing Beautiful HTML Templates:
I made some stunning HTML slide templates & open-sourced them
If you use this template system, it will literally be impossible for your agent to produce something ugly
Link below
Tip:
1) Instead of 100s lines of markdown, ask @claude_code to generate a html (website) brief.
Have it chain together multiple pages, if necessary, into slides.
Example attached using @zarazhangrui beautiful-html-templates for markdown -> website.
2) @claudeai has a button to publish your website to share with colleagues and others.
"Copy" -> "Publish Artifact"
HTML is the new markdown.
I've stopped writing markdown files for almost everything and switched to using Claude Code to generate HTML for me. This is why.
Effective today, we are:
1) Doubling Claude Code’s 5-hour rate limits for Pro, Max, and Team plans;
2) Removing the peak hours limit reduction on Claude Code for Pro and Max plans; and
3) Substantially raising our API rate limits for Opus models.
Karpathy's Personal Wiki Idea implemented:
Synthadoc takes your documents and helps organize it into a wikipedia format.
No cloud account. No vendor lock-in. You owned your wiki.
Use @claude_code directly.
LLM Knowledge Bases
Something I'm finding very useful recently: using LLMs to build personal knowledge bases for various topics of research interest. In this way, a large fraction of my recent token throughput is going less into manipulating code, and more into manipulating knowledge (stored as markdown and images). The latest LLMs are quite good at it. So:
Data ingest:
I index source documents (articles, papers, repos, datasets, images, etc.) into a raw/ directory, then I use an LLM to incrementally "compile" a wiki, which is just a collection of .md files in a directory structure. The wiki includes summaries of all the data in raw/, backlinks, and then it categorizes data into concepts, writes articles for them, and links them all. To convert web articles into .md files I like to use the Obsidian Web Clipper extension, and then I also use a hotkey to download all the related images to local so that my LLM can easily reference them.
IDE:
I use Obsidian as the IDE "frontend" where I can view the raw data, the the compiled wiki, and the derived visualizations. Important to note that the LLM writes and maintains all of the data of the wiki, I rarely touch it directly. I've played with a few Obsidian plugins to render and view data in other ways (e.g. Marp for slides).
Q&A:
Where things get interesting is that once your wiki is big enough (e.g. mine on some recent research is ~100 articles and ~400K words), you can ask your LLM agent all kinds of complex questions against the wiki, and it will go off, research the answers, etc. I thought I had to reach for fancy RAG, but the LLM has been pretty good about auto-maintaining index files and brief summaries of all the documents and it reads all the important related data fairly easily at this ~small scale.
Output:
Instead of getting answers in text/terminal, I like to have it render markdown files for me, or slide shows (Marp format), or matplotlib images, all of which I then view again in Obsidian. You can imagine many other visual output formats depending on the query. Often, I end up "filing" the outputs back into the wiki to enhance it for further queries. So my own explorations and queries always "add up" in the knowledge base.
Linting:
I've run some LLM "health checks" over the wiki to e.g. find inconsistent data, impute missing data (with web searchers), find interesting connections for new article candidates, etc., to incrementally clean up the wiki and enhance its overall data integrity. The LLMs are quite good at suggesting further questions to ask and look into.
Extra tools:
I find myself developing additional tools to process the data, e.g. I vibe coded a small and naive search engine over the wiki, which I both use directly (in a web ui), but more often I want to hand it off to an LLM via CLI as a tool for larger queries.
Further explorations:
As the repo grows, the natural desire is to also think about synthetic data generation + finetuning to have your LLM "know" the data in its weights instead of just context windows.
TLDR: raw data from a given number of sources is collected, then compiled by an LLM into a .md wiki, then operated on by various CLIs by the LLM to do Q&A and to incrementally enhance the wiki, and all of it viewable in Obsidian. You rarely ever write or edit the wiki manually, it's the domain of the LLM. I think there is room here for an incredible new product instead of a hacky collection of scripts.
Tip: Use @pbakaus's impeccable for critique/audit and polishing of your frontend.
Get started by installing the skill and then:
1) /impeccable teach
2) /audit
3) /critique
Tip: Use @claude_code to generate an HTML artifact to explain or deep dive into concepts.
The Claude skill below is emblematic of Claude as a thinking partner to learn from a codebase.
Play around with it and use it as a complement to purely chatting.
Introducing "codebase to course", a skill that turns any codebase into an interactive coding course
So that you can learn coding through your own projects, complete with visualization, plain-English code translations, metaphors, even quizzes...
I vibe code a lot but have no idea how the code works under the hood. This is how I think "learning to code" should be in the AI age: Build first, learn later
Link below
Worth Reading:
1) What are Skills?
They’re not just text files. They’re folders that can include scripts, assets, data, etc.
A skill is a folder...think of the entire file system as a form of context engineering.
2) The Description Field Is For the Model
The description field is not a summary — it's a description of when to trigger skill.
3) Allow flexibility in Skills
Claude will generally try to stick to your instructions, and because Skills are so reusable you’ll want to be careful of being too specific in your instructions.
Give it the flexibility to adapt to the situation.
---
Note: Skills are becoming universally agent-native, spanning everything from coding agents, cowork agents @claudeai, to AI gateways like openclaw.
Thariq @trq212 Mar 17 Article Lessons from Building Claude Code: How We Use Skills Skills have become one of the most used extension points in Claude Code. They’re flexible, easy to make, and simple to distribute. But this flexibility also makes it hard to know what works best. What