The obvious path for designers in the AI age is to move closer to code.
But the more valuable path may be upstream: closer to the customer, the business, and the problem.
If everyone can prompt agents to code, the scarce skill becomes knowing why, what, and how to build.
"There's a good looking guy with white hair looking down on us right now that's happy!" 🥹
Tommy Lloyd pays homage to the late Lute Olson in his postgame interview 🙏
#MarchMadness
For my friends who are still using UV and might be a little weary about recent compromises to PyPi packages, stick this in your pyproject.toml.
You can let all of those pip users find and report the compromises...
I put a lot of heart into my technical writing, I hope it's useful to you all.
📌 Here's a pinned thread of everything I've written.
(much of this will be posted on the Claude blog soon as well)
We're excited to announce duckdb-skills, a DuckDB plugin for Claude Code!
We think the embedded nature of DuckDB makes it a perfect companion for Claude in your local workflows.
The skills supported include:
+ read-file and query – uses DuckDB's CLI to query data locally, unlocking easy access to any file that DuckDB can read.
+ read-memories – a clever idea to store your Claude memories in DuckDB and query them at blazing speed.
These are powered by two additional skills:
+ attach-db – gives Claude a mechanism to manage DuckDB state through a .sql file linked to your project.
+ duckdb-docs – uses a remote DuckDB full-text search database to query the DuckDB docs and answer all of your (and Claude's own) questions.
https://t.co/EvM965jglL
yeah it is but everything in moderation. Internally we always talked about main quest and side quests.
Everyone should focus on the main quest, and moderately or not all on side quests.
Both quest lines feel productive but only one of them advances the main mission of the company.
Introducing the Google Workspace CLI: https://t.co/8yWtbxiVPp - built for humans and agents.
Google Drive, Gmail, Calendar, and every Workspace API. 40+ agent skills included.
Voice mode is rolling out now in Claude Code. It’s live for ~5% of users today, and will be ramping through the coming weeks.
You'll see a note on the welcome screen once you have access. /voice to toggle it on!
In the next version of Claude Code..
We're introducing two new Skills: /simplify and /batch. I have been using both daily, and am excited to share them with everyone.
Combined, these kills automate much of the work it used to take to (1) shepherd a pull request to production and (2) perform straightforward, parallelizable code migrations.
Announcing a new Claude Code feature: Remote Control. It's rolling out now to Max users in research preview. Try it with /remote-control
Start local sessions from the terminal, then continue them from your phone. Take a walk, see the sun, walk your dog without losing your flow.
Introducing: built-in git worktree support for Claude Code
Now, agents can run in parallel without interfering with one other. Each agent gets its own worktree and can work independently.
The Claude Code Desktop app has had built-in support for worktrees for a while, and now we're bringing it to CLI too.
Learn more about worktrees: https://t.co/JFkD2DrAmT
I'm Boris and I created Claude Code. I wanted to quickly share a few tips for using Claude Code, sourced directly from the Claude Code team. The way the team uses Claude is different than how I use it. Remember: there is no one right way to use Claude Code -- everyones' setup is different. You should experiment to see what works for you!