Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Claude Code 2.1.63 dropped with a new built-in command: /simplify It reviews your changed code for three things: - Reuse opportunities (duplicated logic, extractable patterns) - Code quality (readability, naming, structure) - Efficiency (unnecessary complexity, redundant operations) Then it actually fixes what it finds. Not just suggestions, it edits....

dani_avila7's profile picture

Daniel San

33,057 subscribers

372,786 görüntüleme • 4 ay önce •via X (Twitter)

EğitimBilim & Teknoloji
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

How to make Claude Code 10x better: Connect it with a tool that reviews your code and generates prompts for Claude to fix any issues with it automatically. Here is what this looks like:
3:38

How to make Claude Code 10x better: Connect it with a tool that reviews your code and generates prompts for Claude to fix any issues with it automatically. Here is what this looks like:

Santiago

98,881 görüntüleme • 9 ay önce

We've added a new command to Claude Code called /insights When you run it, Claude Code will read your message history from the past month. It'll summarize your projects, how you use Claude Code, and give suggestions on how to improve your workflow.
0:39

We've added a new command to Claude Code called /insights When you run it, Claude Code will read your message history from the past month. It'll summarize your projects, how you use Claude Code, and give suggestions on how to improve your workflow.

Thariq

1,232,937 görüntüleme • 5 ay önce

Just built a custom Blogging Mode in VS Code using Copilot Chat ✍️ It fixes grammar, structures your post, and even suggests your next blog topic — all in Markdown. What will you use custom chat mode for?
0:55

Just built a custom Blogging Mode in VS Code using Copilot Chat ✍️ It fixes grammar, structures your post, and even suggests your next blog topic — all in Markdown. What will you use custom chat mode for?

Visual Studio Code

30,020 görüntüleme • 11 ay önce

This 1-hour workshop on why your Claude Code runs out of tokens so fast will teach you more about making your sessions last longer than everything you've scrolled past this year. Bookmark this & watch, no matter what. After watching this, I built a CLI tool in Zig using that fixes the problem using Minimax-M2.7 on Claude code Here's how I built it; install it, then read the guide below by hoeem 🧵
1:02:22

This 1-hour workshop on why your Claude Code runs out of tokens so fast will teach you more about making your sessions last longer than everything you've scrolled past this year. Bookmark this & watch, no matter what. After watching this, I built a CLI tool in Zig using that fixes the problem using Minimax-M2.7 on Claude code Here's how I built it; install it, then read the guide below by hoeem 🧵

Avid

18,938 görüntüleme • 3 ay önce

Introducing CodeRabbit Plugin for Claude Code! The CodeRabbit plugin for Claude Code creates an autonomous AI development workflow, helping you write and fix code without manual intervention. Type /coderabbit:review (or just say “review my code”) to get AI-powered fixes directly in your dev flow! Try it today, it’s free!
1:59

Introducing CodeRabbit Plugin for Claude Code! The CodeRabbit plugin for Claude Code creates an autonomous AI development workflow, helping you write and fix code without manual intervention. Type /coderabbit:review (or just say “review my code”) to get AI-powered fixes directly in your dev flow! Try it today, it’s free!

CodeRabbit

27,190 görüntüleme • 5 ay önce

Claude Code with Sonnet 4.5 is actually incredible I gave it a prompt for a super complex app, and it one shot the entire thing In this video I walk you through how to use Claude Code to build a prompt library app you can start using immediately (no coding experience required):
19:42

Claude Code with Sonnet 4.5 is actually incredible I gave it a prompt for a super complex app, and it one shot the entire thing In this video I walk you through how to use Claude Code to build a prompt library app you can start using immediately (no coding experience required):

Alex Finn

40,955 görüntüleme • 9 ay önce

Think of it as the Shopify of Claude Code, but for agents, commands, and MCPs 🚀 Pick what you need, “add to cart,” and… it’s 100% FREE. Just copy the command, paste it in your terminal, and instantly get the perfect Claude Code stack for your project. Built as an open-source project so the community can spin up, share, and install Claude Code stacks in seconds, no setup headaches, no paywalls. Here’s the video showing how I built this post… and yes, if you share the command, anyone can clone the exact same stack you’re using. Enjoy, share, and help others build faster with Claude Code ✨
0:59

Think of it as the Shopify of Claude Code, but for agents, commands, and MCPs 🚀 Pick what you need, “add to cart,” and… it’s 100% FREE. Just copy the command, paste it in your terminal, and instantly get the perfect Claude Code stack for your project. Built as an open-source project so the community can spin up, share, and install Claude Code stacks in seconds, no setup headaches, no paywalls. Here’s the video showing how I built this post… and yes, if you share the command, anyone can clone the exact same stack you’re using. Enjoy, share, and help others build faster with Claude Code ✨

Daniel San

124,913 görüntüleme • 11 ay önce

We just built Figma for Claude Code > Select any element on your local front-end > Edit it like you would in Figma > Apply the changes with Claude Code This is not a demo or waitlist. Try it today.
0:22

We just built Figma for Claude Code > Select any element on your local front-end > Edit it like you would in Figma > Apply the changes with Claude Code This is not a demo or waitlist. Try it today.

Quentin Romero Lauro

250,676 görüntüleme • 5 ay önce

The below video is real. No cuts. Founders + CTOs use this, and comapre it to Cursor + Claude Artifacts but prefer it because: - you can edit the code in your favorite IDE (two-way github sync) - automatically knows what npm package to use - picks up errors and fixes them - fast (built with rust)
1:47

The below video is real. No cuts. Founders + CTOs use this, and comapre it to Cursor + Claude Artifacts but prefer it because: - you can edit the code in your favorite IDE (two-way github sync) - automatically knows what npm package to use - picks up errors and fixes them - fast (built with rust)

Anton Osika

453,394 görüntüleme • 1 yıl önce

🚨 Just dropped my new video on how to build yourself a unified AI infrastructure on Claude Code Code for life and work management... - Why I built it - My system design philosophy - Step-by-step on the different components - How to customize it for your own needs
1:13:08

🚨 Just dropped my new video on how to build yourself a unified AI infrastructure on Claude Code Code for life and work management... - Why I built it - My system design philosophy - Step-by-step on the different components - How to customize it for your own needs

ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️

29,331 görüntüleme • 10 ay önce

I’ve been working on dunk. It’s a terminal diff reviewer where you mark issues inline, then let a coding agent fix them. It started as a fork of hunk, but I stripped it down to the loop I need: review → my comments → agent fixes I’m spending time reviewing code and leaving comments for agents rather than writing code myself. But in most tools, that feedback loop still feels broken. dunk is a simple way to make it work across Claude Code, Codex, Pi, etc.
3:48

I’ve been working on dunk. It’s a terminal diff reviewer where you mark issues inline, then let a coding agent fix them. It started as a fork of hunk, but I stripped it down to the loop I need: review → my comments → agent fixes I’m spending time reviewing code and leaving comments for agents rather than writing code myself. But in most tools, that feedback loop still feels broken. dunk is a simple way to make it work across Claude Code, Codex, Pi, etc.

Amir Salihefendić

13,134 görüntüleme • 2 ay önce

Holy shit...Google just dropped CodeMender an autonomous AI agent that finds and fixes security bugs in code by itself. This isn’t a static analysis tool. It’s a self-reasoning system that patches vulnerabilities and rewrites insecure code before humans even find it. Let’s break it down ↓
0:42

Holy shit...Google just dropped CodeMender an autonomous AI agent that finds and fixes security bugs in code by itself. This isn’t a static analysis tool. It’s a self-reasoning system that patches vulnerabilities and rewrites insecure code before humans even find it. Let’s break it down ↓

Hasan Toor

127,108 görüntüleme • 7 ay önce

Introducing Claude Code Templates 🚀 I originally built this to streamline how I set up new projects with Claude Code…just a small tool to make my own workflow smoother. No install, just run: npx claude-code-templates Right now, it configures Commands, Hooks, MCPs, and settings.json for JavaScript/TypeScript and Python projects. It made things so much easier for me that I decided to share it with the community. Open-source and open to ideas — feel free to contribute! Big thanks to the team at Anthropic and everyone behind Claude Code Community 🙌
0:50

Introducing Claude Code Templates 🚀 I originally built this to streamline how I set up new projects with Claude Code…just a small tool to make my own workflow smoother. No install, just run: npx claude-code-templates Right now, it configures Commands, Hooks, MCPs, and settings.json for JavaScript/TypeScript and Python projects. It made things so much easier for me that I decided to share it with the community. Open-source and open to ideas — feel free to contribute! Big thanks to the team at Anthropic and everyone behind Claude Code Community 🙌

Daniel San

28,410 görüntüleme • 1 yıl önce

I built a simple internal chatbot that answers your team's SOPs and FAQs using your existing Google Drive docs in the walkthrough, I show: – how it finds the right doc for any question – how your team can “@” specific files (like in Slack) – how to set it up and share it with your team in minutes reply “chatbot” and I’ll send the full video + code (must be following)
0:21

I built a simple internal chatbot that answers your team's SOPs and FAQs using your existing Google Drive docs in the walkthrough, I show: – how it finds the right doc for any question – how your team can “@” specific files (like in Slack) – how to set it up and share it with your team in minutes reply “chatbot” and I’ll send the full video + code (must be following)

Tyler

27,263 görüntüleme • 1 yıl önce

In Cursor you can *easily* turn comments into code. Just write in natural language what you want in your file. Then highlight it, use CMD+K, and ask the AI to translate it into code - and it will! Turn your thoughts right into apps.
6:50

In Cursor you can *easily* turn comments into code. Just write in natural language what you want in your file. Then highlight it, use CMD+K, and ask the AI to translate it into code - and it will! Turn your thoughts right into apps.

Mckay Wrigley

106,485 görüntüleme • 1 yıl önce

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this
13:23

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this

Yarchi

55,345 görüntüleme • 1 ay önce

there’s now a claude-code plugin to log your long running sessions on neatlogs. here’s how to use it :) try it out here
1:04

there’s now a claude-code plugin to log your long running sessions on neatlogs. here’s how to use it :) try it out here

simran sachdeva

26,029 görüntüleme • 10 gün önce