Delba's banner
Delba's profile picture

Delba

@delba_oliveira101,538 subscribers

For the love of the craft. Claude Code • @ClaudeDevs @AnthropicAI | Prev. @Vercel

Shorts

Smol tip: 𝙲𝚝𝚛𝚕+𝙾 to search a long Claude Code conversation • / to search for a term • 𝚗 to step through the matches • } to hop between your own prompts

Smol tip: 𝙲𝚝𝚛𝚕+𝙾 to search a long Claude Code conversation • / to search for a term • 𝚗 to step through the matches • } to hop between your own prompts

40,355 görüntüleme

Smol tip: /𝚌𝚍 moves your running Claude Code session to another directory without restarting. Your conversation and context come with you, and Claude picks up the new project's CLAUDE.md.

Smol tip: /𝚌𝚍 moves your running Claude Code session to another directory without restarting. Your conversation and context come with you, and Claude picks up the new project's CLAUDE.md.

207,961 görüntüleme

Smol tip: /𝚏𝚘𝚛𝚔 is perfect for mid-task side quests. It spawns a subagent that inherits the whole conversation, runs in the background while you keep working on your main quest, and comes back with an update.

Smol tip: /𝚏𝚘𝚛𝚔 is perfect for mid-task side quests. It spawns a subagent that inherits the whole conversation, runs in the background while you keep working on your main quest, and comes back with an update.

107,773 görüntüleme

Smol tip: pasting long text into Claude Code collapses it into [Pasted text #1]. If you need to edit it you can paste again to expand. Or, Ctrl+G to open the whole prompt in your code editor. Saved changes sync back to Claude's input field.

Smol tip: pasting long text into Claude Code collapses it into [Pasted text #1]. If you need to edit it you can paste again to expand. Or, Ctrl+G to open the whole prompt in your code editor. Saved changes sync back to Claude's input field.

89,057 görüntüleme

How I use Claude Code and Remotion to make animated diagrams. Sorry, it's not a single prompt. 1. Find an input language the model knows well. For example, Mermaid for flowcharts. Claude writes it fluently, so it's my entry point. 2. Use Claude to build components that take that input and bake in the guardrails: design system, animation patterns, layout rules. 3. Now I can describe what I want in plain English e.g. "create a flowchart for the tier check section in the script", and Claude translates it to our input language: ``` flowchart TD t1[Tier 1 read-only] t2[Tier 2 in-project writes] t3[Tier 3 everything else] action[Action] --> t1 action --> t2 action --> t3 t1 --> skip([Skips classifier]) t2 --> skip t3 --> classifier{Classifier} classifier --> approve[Approve] classifier --> deny[Deny] ``` The component handles the rest: layout, styling, node and edge reveals. It also takes events for follow-ups like the trace dot that follows a path and lights up nodes. 4. To finish it off, I wrapped the board in a separate CRT shader component. It really helps to have a shared vocabulary with your agent. When I say "rise in fast on enter", it knows I mean fade in while translating up, from a set offset, faster than the default duration, with a specific bezier curve. For common language inspo: look into Matt Pocock `/grill-with-docs` and by Emil Kowalski and Glenn Hitchcock.

How I use Claude Code and Remotion to make animated diagrams. Sorry, it's not a single prompt. 1. Find an input language the model knows well. For example, Mermaid for flowcharts. Claude writes it fluently, so it's my entry point. 2. Use Claude to build components that take that input and bake in the guardrails: design system, animation patterns, layout rules. 3. Now I can describe what I want in plain English e.g. "create a flowchart for the tier check section in the script", and Claude translates it to our input language: ``` flowchart TD t1[Tier 1 read-only] t2[Tier 2 in-project writes] t3[Tier 3 everything else] action[Action] --> t1 action --> t2 action --> t3 t1 --> skip([Skips classifier]) t2 --> skip t3 --> classifier{Classifier} classifier --> approve[Approve] classifier --> deny[Deny] ``` The component handles the rest: layout, styling, node and edge reveals. It also takes events for follow-ups like the trace dot that follows a path and lights up nodes. 4. To finish it off, I wrapped the board in a separate CRT shader component. It really helps to have a shared vocabulary with your agent. When I say "rise in fast on enter", it knows I mean fade in while translating up, from a set offset, faster than the default duration, with a specific bezier curve. For common language inspo: look into Matt Pocock `/grill-with-docs` and by Emil Kowalski and Glenn Hitchcock.

60,407 görüntüleme

Hi. I'm back. Next.js 16: 𝚌𝚊𝚌𝚑𝚎𝙻𝚒𝚏𝚎 Configure how long: • prefetched data can be reused on the client without refetching • prerendered data can be reused on the server without rerendering

Hi. I'm back. Next.js 16: 𝚌𝚊𝚌𝚑𝚎𝙻𝚒𝚏𝚎 Configure how long: • prefetched data can be reused on the client without refetching • prerendered data can be reused on the server without rerendering

94,520 görüntüleme

Vercel pricing update: CPU billing is now based on active usage, not function duration. This means you no longer pay for time spent waiting on external services such as databases, APIs, or LLMs.

Vercel pricing update: CPU billing is now based on active usage, not function duration. This means you no longer pay for time spent waiting on external services such as databases, APIs, or LLMs.

107,354 görüntüleme

👩‍🔬 <AnimatedFilesystem />

👩‍🔬 <AnimatedFilesystem />

42,096 görüntüleme

TIL multiple CSS transform functions of the same type are additive. I used it to add a turbulence effect that doesn't overwrite existing or in-progress transforms.

TIL multiple CSS transform functions of the same type are additive. I used it to add a turbulence effect that doesn't overwrite existing or in-progress transforms.

67,911 görüntüleme

Next.js 15.2 (canary preview): Node.js middleware The quest to fully support Node.js in middleware continues. You can now configure `middleware.js` to use the Node.js runtime. This means you can use any node module or npm package in your middleware.

Next.js 15.2 (canary preview): Node.js middleware The quest to fully support Node.js in middleware continues. You can now configure `middleware.js` to use the Node.js runtime. This means you can use any node module or npm package in your middleware.

66,730 görüntüleme

Next.js 15.1: Easier error debugging ✓ Hide¹ stack frames for dependency code ✓ Surface source of the error in your code Video: Terminal output² of a Zod parsing error

Next.js 15.1: Easier error debugging ✓ Hide¹ stack frames for dependency code ✓ Surface source of the error in your code Video: Terminal output² of a Zod parsing error

49,768 görüntüleme

New Next.js e-commerce template by Blazity: ◆ Built with v0, shadcn UI, and Turborepo ◆ AI (search, image captioning) ◆ Enterprise-ready (A/B testing, scalable redirects, tests, etc) ◆ And more Try it out: `npm create commerce`

New Next.js e-commerce template by Blazity: ◆ Built with v0, shadcn UI, and Turborepo ◆ AI (search, image captioning) ◆ Enterprise-ready (A/B testing, scalable redirects, tests, etc) ◆ And more Try it out: `npm create commerce`

60,102 görüntüleme

Videos

delba_oliveira's profile picture

React visually explained: 'use client'

Delba

747,015 görüntüleme • 1 yıl önce

delba_oliveira's profile picture

Preview: The Future of Next.js... in 100 seconds.

Delba

129,897 görüntüleme • 1 yıl önce

delba_oliveira's profile picture

Next.js 15 next.config.js → next.config.ts

Delba

86,251 görüntüleme • 1 yıl önce

delba_oliveira's profile picture

Static vs. Dynamic rendering in Next.js

Delba

105,387 görüntüleme • 2 yıl önce

delba_oliveira's profile picture

👩‍🔬 AI teleprompter ft.

Delba

15,005 görüntüleme • 5 ay önce

delba_oliveira's profile picture

React tip: "use client" misconceptions (2/5) 🚫 "You cannot nest Server Components inside Client Components because "use client" turns everything into Client Components." ✅ We can pass the rendered result of Server Components to Client Components as props. Simple example: (Server Component) (Client Component) (Server Component) is designed for the client. It needs to instantly open and close when clicked. is designed for the server. It uses packages that don't work in the browser and needs to fetch data close to where it's stored without exposing credentials. So, how can we nest a component that uses server APIs inside a component that uses client APIs... without using `import`? React props to the rescue! --- (0:00) 1-4: Reminder: Importing code forms a module dependency graph. Adding dependencies to a server or client bundle. (0:23) 5-6: Reminder: Using components eventually forms a rendered component tree. (0:37) 9: Oh no! We get an error when trying to `import` a client API (useState) into a server module. (0:44) 10: We know the trick by now: Add "use client" to mark `2.js` as a client entry point. This moves the module to the client bundle and allows us to use client APIs like `useState.` (0:51) 11: But we get a new error! "use client" moved all imported dependencies into the client bundle, including our ORM package, which doesn't work in the browser. (0:59) 13: Let's refactor without changing our rendered component hierarchy. First, we move the `Cart` import to the parent file that imports `Modal`. This moves `Cart` outside the "use client" boundary and consequently the client bundle. (1:11) 15: Then, we pass down the rendered result of `Cart` as a prop to `Modal`. This allows `Cart` to be entirely rendered on the server as a Server Component before being passed down. `Modal` has no knowledge of what the `cart` prop is. Its only responsibility is placing whatever it receives into the `{cart}` slot. (1:15) 16: Finally, it's common to use the special `children` prop for a component's primary content. The key insight is that we were able to use props to retain our desired component hierarchy even though we changed our module dependency graph.

Delba

43,989 görüntüleme • 2 yıl önce