Oh yeah I think we talked at some point right? 😅

Subscribe. Someone who knows my pain.

At work we use Storybook with React Native Web for our design system library. Gave a talk about it here:

youtu.be/jkQOBlkAFfA?...

I like this slide

It was great seeing you there!!

Wow that's amazing! I love the video of how it was found

This one is better

i made a chart

I recently did something similar, open-meteo doesn't require an API key: open-meteo.com

This article has a lot of best practices, which have helped me out. I think it's really important to dig into the full capabilities of the tools you use.

www.anthropic.com/engineering/...

Custom slash commands dramatically improve the developer experience. You could maintain a document with useful prompts, but accessing them via /commands makes you more invested in creating reusable workflows. It's like using a prompt as a function.

You can still use images in the context of your conversation with Claude Code. I thought I'd lose the ability to use images switching to a terminal tool. But you can copy and paste images into Claude Code just like with Cursor.

Sub-agents solve the biggest friction with AI coding tools. The main friction is running out of context. Sub-agents let you parallelize work and save context since each has its own context. Just tell Claude to use sub-agents in your prompt.

Claude Code's planning approach is much better than Cursor. The way it responds in chat gives me confidence that it's breaking down work into tasks properly. Instead of jumping straight to implementation, it reads files first, thinks through the problem, and makes a plan.

Oh yeah, making a plan is great. You can ask the agent to keep improving and improving the plan, and it will give it some really nice rails to execute well on. I'm glad it was helpful!