We'll be spending a lot more time trying to understand the outputs of language models. A few thoughts, tips & tricks:
Writing. Something I've had success with: Ask your LLM to explain something in ASD-STE100, it's a controlled language specification originally developed for aerospace maintenance documentation. LLMs well-versed in this language and it comes with heavy constraints on clean writing style that I often find a lot more readable. Sometimes I've tried to soften it a bit e.g. ask for "80% of the way to ASD-STE100" because the spec is quite stringent. But even better:
Diagrams / images. Instead of writing, ask your LLM to create a diagram. These can be a lot easier to process, parse, and understand. But even better:
Web pages. Ask for output "in HTML" to get a beautiful, interactive webpage. LLMs are getting really good at frontend and can create beautiful experiences, animations, etc. But even better:
Explainer videos. The output format I am most bullish on is fully custom / bespoke explainer videos generated on any arbitrary topic. Experiment with things like "Create a 3b1b style video explainer on X. Use my ElevenLabs API key for audio narration". (you'd need an API key for the latter or you can ask your LLM to find you decent free alternatives that use your local compute). This is actually starting to work!
In summary:
- As LLMs get better, they will do more and more of the legwork autonomously, and a lot more of our work will rise up the abstractions into oversight and understanding.
- Luckily, LLMs can help here too because as intelligence and code are increasingly abundant, you can ask for large, custom, discardable software artifacts (e.g. web apps, video explainers) that would have never made sense to create before. Push the boundaries here and you'll be surprised.
mattpocock/skills v1.2 is out!
We're now the 19th most-starred repo of all time. 13.5m downloads on skills.sh. Thanks for your support!
Here's what's new:
- Docs: the community's biggest ask. Every skill documented, with explanations of the main flows + troubleshooting
- Claude Plugin: install via Claude's official marketplace
- Codex Support: full Codex support via agents/openai.yaml files
Updated Skills:
- /grilling now asks you questions in rounds, not one-by-one
- /prototype now uses HTML instead of a TUI for building logic prototypes - easier to share and far richer
- /writing-for-agents renamed from /writing-great-skills, use it for ANYTHING your agents read (AGENTS.md, system prompts, docs)
New Skills:
- /wizard: tired of provisioning infra? Get your agent to build you a TUI to walk you through it
- /to-questionnaire: hit a grilling question you can't answer? Turn the session into a doc you can walk through on a call with a colleague
- /wait-what: no idea what the model said? Refocus it in your domain language and simplify with ASD-STE100
Full changelog + docs below. Video soon!
Experimenting with a rare addition to my global CLAUDE.md:
"Always talk in ASD-STE100 Simplified Technical English. Always read CONTEXT.md files, and use their ubiquitous language."
Microsoft's Advanced Shader Delivery technology has now arrived on AMD RDNA 3 GPUs.
In testing with a Radeon RX 7600, Forza Horizon 6 now loads in just 4 seconds instead of the previous 90 seconds.
The feature precompiles shaders during game downloads and installation, bypassing the need for in-game shader compilation.
This cuts load times by up to 95% and virtually eliminates shader stutter for much smoother gameplay in supported titles.
Co-developed with AMD, ASD is enabled through the latest Adrenalin 26.5.2 drivers for RDNA 3, RDNA 3.5, and RDNA 4 GPUs. It requires Windows 11 24H2 and updated Xbox services.
All love and respect between Steve Nash, Grant Hill, and Mike D’Antoni as D’Antoni has been enshrined into the @Hoophall 🙌
Watch the Class of 2026 Enshrinement Ceremony on NBA TV and the NBA App.