Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

How to build a $25K website with AI, every click from zero (Claude Code + n8n, beginner guide) An agency would charge about twenty-five thousand dollars for this website. Here's how you build it with AI, from zero, every click, and wire it so every good lead gets a...

pro.glitch's profile picture

Professor Glitch

114,300 subscribers

20,000 Aufrufe • vor 28 Tagen •via TikTok

BildungFinanzenWissenschaft & Technologie#claudecode#n8n#aiautomation#vibecoding
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Claude Code doesn't replace n8n. Here's one project built with both People think Claude Code replaces n8n. So here's one real project: a returns desk for a small online shop, built with both. Step 1: Claude Code builds the app. The owner says one sentence ("Build me a returns page"). Claude Code does three things: It reads CLAUDE.md, the shop's handbook of name, colours and rules, which loads every session. It pulls the refund-policy skill. Skills are loaded only when they're needed. It writes the code, hits an error, fixes it, and ships a real returns page. Step 2: n8n wires it into the business. Every return fires a webhook, and the same route runs every time: the label goes out through Gmail a row is added to the spreadsheet a note is posted in Slack the refund goes through Stripe when the parcel is scanned back in Every run is logged, and it runs 24/7. Step 3: a routine does the thinking. Every night at 11, a Claude Code routine runs in Anthropic's cloud with the laptop closed. It reads the day's returns, spots that 6 of 9 mention the same seam, and writes the owner a report. The handoffs: Claude Code wrote the n8n workflow, and n8n calls Claude when a return doesn't fit any route. Claude Code builds and thinks. n8n runs the same routes all day. Together they run the business. #claudecode #aiautomation #aiagent #n8n
2:31

Claude Code doesn't replace n8n. Here's one project built with both People think Claude Code replaces n8n. So here's one real project: a returns desk for a small online shop, built with both. Step 1: Claude Code builds the app. The owner says one sentence ("Build me a returns page"). Claude Code does three things: It reads CLAUDE.md, the shop's handbook of name, colours and rules, which loads every session. It pulls the refund-policy skill. Skills are loaded only when they're needed. It writes the code, hits an error, fixes it, and ships a real returns page. Step 2: n8n wires it into the business. Every return fires a webhook, and the same route runs every time: the label goes out through Gmail a row is added to the spreadsheet a note is posted in Slack the refund goes through Stripe when the parcel is scanned back in Every run is logged, and it runs 24/7. Step 3: a routine does the thinking. Every night at 11, a Claude Code routine runs in Anthropic's cloud with the laptop closed. It reads the day's returns, spots that 6 of 9 mention the same seam, and writes the owner a report. The handoffs: Claude Code wrote the n8n workflow, and n8n calls Claude when a return doesn't fit any route. Claude Code builds and thinks. n8n runs the same routes all day. Together they run the business. #claudecode #aiautomation #aiagent #n8n

Professor Glitch

10,200 Aufrufe • vor 1 Monat

MCP explained in one drawing: how your AI gets inside your apps (Claude, n8n, Gmail) Here's how your AI actually gets inside your apps. It's called MCP, and it fits in one drawing. On its own, an AI is a brain in a box. It can talk and think, but it can't open your email or build anything in n8n. It has no hands. 1. The door is the API. Most apps have a door for other software: Gmail has one, GitHub has one, n8n has one. Every door is a different shape, with its own rules and its own key. 2. The plug is MCP. It's one standard shape. On one side is the AI. On the other side is a small program called an MCP server, one per app, and it knows that app's door. The AI plugs in, and the server does the walking through the door. 3. The menu is the list of tools. When the AI plugs in, it sees every tool the app offers, in plain words. Gmail's server offers create a draft, search mail and read a message. n8n's server offers list workflows, create a workflow and test it. The AI reads the list like a menu, picks a tool and calls it. That's how Claude builds a whole workflow inside n8n, node by node, and checks its own work, while you never open n8n. 4. Connecting one takes one sentence. In Claude Code, say: "Connect yourself to my n8n, here's the address and a key I made just for you." Claude writes a small settings file with the server's name and the key. Type /mcp and it says connected. That's the setup for most apps. Some, like Gmail, you just sign in to instead. 5. The key is the important part. An MCP server can only use the tools on its menu, and only as far as its key allows. So make a key that can do the job and nothing more. If the app lets you limit a key, make it read only when reading is all you need. If it doesn't, use a test account. And if a key ever leaks, cancel it inside the app. One click, and nobody can use it, the AI included. One honest line: MCP doesn't make the AI smarter. It gives a smart thing a way to act, and everything it does through that plug, it does as you. So you still check the work, like you would a new hire's. If you're starting from scratch, I have step-by-step lessons for all of this inside my community. There are eight courses, in order, from the basics of AI to automations, building websites and apps, and AI agents. If you're interested, the link is in my profile. #mcp #cli ##aiagents #aiautomation #claudecode
2:56

MCP explained in one drawing: how your AI gets inside your apps (Claude, n8n, Gmail) Here's how your AI actually gets inside your apps. It's called MCP, and it fits in one drawing. On its own, an AI is a brain in a box. It can talk and think, but it can't open your email or build anything in n8n. It has no hands. 1. The door is the API. Most apps have a door for other software: Gmail has one, GitHub has one, n8n has one. Every door is a different shape, with its own rules and its own key. 2. The plug is MCP. It's one standard shape. On one side is the AI. On the other side is a small program called an MCP server, one per app, and it knows that app's door. The AI plugs in, and the server does the walking through the door. 3. The menu is the list of tools. When the AI plugs in, it sees every tool the app offers, in plain words. Gmail's server offers create a draft, search mail and read a message. n8n's server offers list workflows, create a workflow and test it. The AI reads the list like a menu, picks a tool and calls it. That's how Claude builds a whole workflow inside n8n, node by node, and checks its own work, while you never open n8n. 4. Connecting one takes one sentence. In Claude Code, say: "Connect yourself to my n8n, here's the address and a key I made just for you." Claude writes a small settings file with the server's name and the key. Type /mcp and it says connected. That's the setup for most apps. Some, like Gmail, you just sign in to instead. 5. The key is the important part. An MCP server can only use the tools on its menu, and only as far as its key allows. So make a key that can do the job and nothing more. If the app lets you limit a key, make it read only when reading is all you need. If it doesn't, use a test account. And if a key ever leaks, cancel it inside the app. One click, and nobody can use it, the AI included. One honest line: MCP doesn't make the AI smarter. It gives a smart thing a way to act, and everything it does through that plug, it does as you. So you still check the work, like you would a new hire's. If you're starting from scratch, I have step-by-step lessons for all of this inside my community. There are eight courses, in order, from the basics of AI to automations, building websites and apps, and AI agents. If you're interested, the link is in my profile. #mcp #cli ##aiagents #aiautomation #claudecode

Professor Glitch

18,500 Aufrufe • vor 26 Tagen

How to put an AI agent to work this week: AI agents explained for beginners, n8n vs Claude Code How to put an AI agent to work this week, drawn start to finish: what an AI agent is, what it's made of, and which tool to build it in. AI agent vs chatbot vs automation: - An automation is a sprinkler on a timer. Six in the morning, every day, same water, even when it's raining. That's a workflow: same trigger, same steps. - A chatbot is a smart friend on the phone. Great advice, but you're still the one under the sink holding the wrench. - An AI agent is the handyman you let into the house. You hand over the job and he does the work, in a loop: goal, plan, act, check, repeat, until the job is done or he needs you. The four pieces of every AI agent you'd trust with real work: 1. The brain: the AI model inside Claude, ChatGPT or Gemini. It reads, reasons and picks the next step. 2. Context: instructions (the job sheet), memory (notes from last time) and knowledge (your price list, services and documents). This is the piece people skip, and it's why their agent writes like a stranger. 3. Tools: the keys you hand over, like your email, calendar and files. Only the keys this job needs. 4. Guardrails: house rules. Anything that leaves the house (an email, a payment, a deletion) waits for your approval. Human in the loop. One real example, end to end. The goal, in one sentence: follow up on today's client call. The AI agent reads the call notes in Google Drive, checks Google Calendar for an open slot (your client notes say she likes mornings), drafts the follow-up email in Gmail with the price sheet linked, and updates your client sheet in Google Sheets. Then it stops, so you can read it and hit send. n8n vs Claude Code, the doorbell and the desk: - n8n is the doorbell: a visual workflow automation tool that connects your apps and waits for a trigger. A call note lands in a Google Drive folder and the follow-up gets drafted, day or night. For the step that needs judgment, the n8n AI Agent node holds the same four pieces and runs the same loop. - Claude Code is the desk: an AI agent that works next to you, on your computer, in your files. It reads CLAUDE.md (the job sheet), uses skills (your steps written down once) and reaches Gmail and your calendar through MCP (the keys). - Doorbell jobs go in n8n: something happens, same steps, every time. Desk jobs go to Claude Code: messy, different every time, or living in your files. They work together, too: n8n has a built-in MCP server, so Claude Code can build n8n workflows for you. How to put an AI agent to work this week: 1. Pick one job you do every week that starts the same way (follow-ups, quote requests, the Monday report). 2. Write the context: one page with the job, how you like it done, and three good examples. 3. Hand it one key, drafts only. It reads and drafts, and nothing sends. 4. Two weeks of yeses. It drafts, you send, and every fix goes into that one page. That's your first agent: one job, one page, one key, two weeks of yeses. The only part left is the setup: n8n, Claude Code, and the keys wired into your real tools. I teach all of it inside my community, course by course, in that order. If you're interested, the link is in my profile. #claudecode #aiagents #n8n #aiautomation
4:21

How to put an AI agent to work this week: AI agents explained for beginners, n8n vs Claude Code How to put an AI agent to work this week, drawn start to finish: what an AI agent is, what it's made of, and which tool to build it in. AI agent vs chatbot vs automation: - An automation is a sprinkler on a timer. Six in the morning, every day, same water, even when it's raining. That's a workflow: same trigger, same steps. - A chatbot is a smart friend on the phone. Great advice, but you're still the one under the sink holding the wrench. - An AI agent is the handyman you let into the house. You hand over the job and he does the work, in a loop: goal, plan, act, check, repeat, until the job is done or he needs you. The four pieces of every AI agent you'd trust with real work: 1. The brain: the AI model inside Claude, ChatGPT or Gemini. It reads, reasons and picks the next step. 2. Context: instructions (the job sheet), memory (notes from last time) and knowledge (your price list, services and documents). This is the piece people skip, and it's why their agent writes like a stranger. 3. Tools: the keys you hand over, like your email, calendar and files. Only the keys this job needs. 4. Guardrails: house rules. Anything that leaves the house (an email, a payment, a deletion) waits for your approval. Human in the loop. One real example, end to end. The goal, in one sentence: follow up on today's client call. The AI agent reads the call notes in Google Drive, checks Google Calendar for an open slot (your client notes say she likes mornings), drafts the follow-up email in Gmail with the price sheet linked, and updates your client sheet in Google Sheets. Then it stops, so you can read it and hit send. n8n vs Claude Code, the doorbell and the desk: - n8n is the doorbell: a visual workflow automation tool that connects your apps and waits for a trigger. A call note lands in a Google Drive folder and the follow-up gets drafted, day or night. For the step that needs judgment, the n8n AI Agent node holds the same four pieces and runs the same loop. - Claude Code is the desk: an AI agent that works next to you, on your computer, in your files. It reads CLAUDE.md (the job sheet), uses skills (your steps written down once) and reaches Gmail and your calendar through MCP (the keys). - Doorbell jobs go in n8n: something happens, same steps, every time. Desk jobs go to Claude Code: messy, different every time, or living in your files. They work together, too: n8n has a built-in MCP server, so Claude Code can build n8n workflows for you. How to put an AI agent to work this week: 1. Pick one job you do every week that starts the same way (follow-ups, quote requests, the Monday report). 2. Write the context: one page with the job, how you like it done, and three good examples. 3. Hand it one key, drafts only. It reads and drafts, and nothing sends. 4. Two weeks of yeses. It drafts, you send, and every fix goes into that one page. That's your first agent: one job, one page, one key, two weeks of yeses. The only part left is the setup: n8n, Claude Code, and the keys wired into your real tools. I teach all of it inside my community, course by course, in that order. If you're interested, the link is in my profile. #claudecode #aiagents #n8n #aiautomation

Professor Glitch

18,500 Aufrufe • vor 28 Tagen

How to build a complete app with AI (no code, the whole picture) How to build a complete app with AI when you don't know how to code: login, a database, photos, invoices, and a real link your customers open on their phone. We follow one client, Priya, through a client portal for a kitchen remodeler. She logs in and sees her project's stage, her photos and her invoice. Every step answers a real beginner question about how apps work. 1. Your workshop: VS Code with the Claude Code extension, an empty folder 2. Describe the app in plain English (plus three technical lines you can copy) 3. The front end, and why localhost means only you can see it 4. The database: the refresh test, and what tables are 5. Login: why your password is stored only as a hash, and what a session cookie does 6. The one rule every app needs: each customer sees only their own data, proven with a test 7. Move the database online: from a file on your laptop to a hosted Postgres database on Supabase, with secret keys in a private .env.local file 8. GitHub: put your code online in a private repository 9. Vercel: deploy, add environment variables, and get a live link (honest costs: Vercel Pro for a business, Supabase Pro) 10. Your own domain with DNS and HTTPS, then a security audit before real clients log in Works for any small business app: client portals, booking apps, customer dashboards, internal tools. AI app builder, vibe coding, no-code app, full stack app with Claude Code. I have an entire course on building apps with AI from zero in my community. If you're interested, the link is in my profile. #vibecoding#aiapp #claudecode#aiagent
7:28

How to build a complete app with AI (no code, the whole picture) How to build a complete app with AI when you don't know how to code: login, a database, photos, invoices, and a real link your customers open on their phone. We follow one client, Priya, through a client portal for a kitchen remodeler. She logs in and sees her project's stage, her photos and her invoice. Every step answers a real beginner question about how apps work. 1. Your workshop: VS Code with the Claude Code extension, an empty folder 2. Describe the app in plain English (plus three technical lines you can copy) 3. The front end, and why localhost means only you can see it 4. The database: the refresh test, and what tables are 5. Login: why your password is stored only as a hash, and what a session cookie does 6. The one rule every app needs: each customer sees only their own data, proven with a test 7. Move the database online: from a file on your laptop to a hosted Postgres database on Supabase, with secret keys in a private .env.local file 8. GitHub: put your code online in a private repository 9. Vercel: deploy, add environment variables, and get a live link (honest costs: Vercel Pro for a business, Supabase Pro) 10. Your own domain with DNS and HTTPS, then a security audit before real clients log in Works for any small business app: client portals, booking apps, customer dashboards, internal tools. AI app builder, vibe coding, no-code app, full stack app with Claude Code. I have an entire course on building apps with AI from zero in my community. If you're interested, the link is in my profile. #vibecoding#aiapp #claudecode#aiagent

Professor Glitch

106,000 Aufrufe • vor 4 Tagen

Every automation expert has shipped a workflow, then found out it broke when the client did. APIs time out. Credentials expire. A node gets a value it wasn't built for. The question was never "will it fail," it's "how fast do I find out." So I built a self-fixing system for n8n. When any workflow fails, Claude Code reads the broken workflow, finds the root cause, and sends me a Slack message with 4 buttons: → Auto Fix: Claude applies the fix it proposed, validates it, and saves → Replay: direct links to re-run a workflow that just hit a temporary glitch → Custom Fix: a form where I type the change in plain English and Claude applies it → Decline: logs the error, changes nothing THE STACK - n8n Error Trigger to catch every failure - Claude Code with the n8n-mcp server for full workflow access - ngrok to connect n8n cloud to my machine - Slack as the approval layer The result: workflows that diagnose and repair themselves while I sleep, with me still approving every change before it goes live. Watch the full video here: The complete PDF guide are linked in the video description, ready to download. You can also drop a comment and I'll send them over. If this is useful, a like, follow, and subscribe goes a long way. Follow for more on building production AI automation. #n8n #Automation #AIAgents #ClaudeAI #BuildInPublic
7:55

Every automation expert has shipped a workflow, then found out it broke when the client did. APIs time out. Credentials expire. A node gets a value it wasn't built for. The question was never "will it fail," it's "how fast do I find out." So I built a self-fixing system for n8n. When any workflow fails, Claude Code reads the broken workflow, finds the root cause, and sends me a Slack message with 4 buttons: → Auto Fix: Claude applies the fix it proposed, validates it, and saves → Replay: direct links to re-run a workflow that just hit a temporary glitch → Custom Fix: a form where I type the change in plain English and Claude applies it → Decline: logs the error, changes nothing THE STACK - n8n Error Trigger to catch every failure - Claude Code with the n8n-mcp server for full workflow access - ngrok to connect n8n cloud to my machine - Slack as the approval layer The result: workflows that diagnose and repair themselves while I sleep, with me still approving every change before it goes live. Watch the full video here: The complete PDF guide are linked in the video description, ready to download. You can also drop a comment and I'll send them over. If this is useful, a like, follow, and subscribe goes a long way. Follow for more on building production AI automation. #n8n #Automation #AIAgents #ClaudeAI #BuildInPublic

Gbenga Akindolani |AI Engineer | Automation Expert

46,436 Aufrufe • vor 5 Monaten

Build your first AI agent with Claude Code (step by step) Most people's first "agent" is a chatbot they have to babysit. This one does a real job: the 40 minutes you lose every morning working out what needs you today. Here's the whole build in Claude Code, in the desktop app and in the terminal: Dump everything on your plate and let Claude find the job that repeats. Let it interview you and write CLAUDE.md, the file it reads every time it starts. Know the difference: an automation repeats steps, an agent decides them. Write the scope: it reads, it never sends, it never deletes. Turn the job into a skill, written down once. Connect only the tools it needs (Gmail and Google Calendar). Set permissions: allow reading, ask before sending, deny deleting. Put it on a schedule, every weekday at 7. Then watch it for a week. When it gets something wrong, fix the skill, not the output. Everything on screen is real Claude Code output on made-up business data. Save this for when you build your first one. #aiagents #aiautomation #claude #aiemployee
4:11

Build your first AI agent with Claude Code (step by step) Most people's first "agent" is a chatbot they have to babysit. This one does a real job: the 40 minutes you lose every morning working out what needs you today. Here's the whole build in Claude Code, in the desktop app and in the terminal: Dump everything on your plate and let Claude find the job that repeats. Let it interview you and write CLAUDE.md, the file it reads every time it starts. Know the difference: an automation repeats steps, an agent decides them. Write the scope: it reads, it never sends, it never deletes. Turn the job into a skill, written down once. Connect only the tools it needs (Gmail and Google Calendar). Set permissions: allow reading, ask before sending, deny deleting. Put it on a schedule, every weekday at 7. Then watch it for a week. When it gets something wrong, fix the skill, not the output. Everything on screen is real Claude Code output on made-up business data. Save this for when you build your first one. #aiagents #aiautomation #claude #aiemployee

Professor Glitch

25,600 Aufrufe • vor 19 Tagen

How to become the AI person on your team Most people use AI at work like a smarter search bar: paste something in, ask, copy the answer out. Soon that's as common as knowing email. The people getting noticed build with it. They connect AI to the tools their team already uses. Here's one real example, the weekly sales report that eats someone's Monday morning: The doors. Almost every work app (HubSpot, Jira, Google Sheets, Slack) has an API, a door other software can use. No code needed. n8n. Each door becomes a box on a canvas. A schedule trigger fires every Monday at 7, HubSpot pulls last week's deals, Jira counts open tickets, Sheets brings the target, and one AI step has Claude write the report. Context. Give Claude one page about your team: who reads the report, the quarterly target, and that your manager wants bad news first. Now it sounds like your team, not a stranger. Approval. The draft comes to you in Slack first. Tap approve and it posts to the team at 8. Claude Code. For questions that need judgment ("why did the Acme deal slip?"), plug the same tools into Claude Code. It checks HubSpot, Jira and Slack by itself and answers with sources. The rule to keep: if the steps never change, build it in n8n. If the work needs judgment, give it to Claude Code. It takes a few weekends: learn how APIs work, learn one tool all the way down, then connect your first chore. I teach all of it from zero inside my community, seven courses in order. If you're interested, the link is in my profile. #aiautomation #aiagent #n8n #claudecode
2:09

How to become the AI person on your team Most people use AI at work like a smarter search bar: paste something in, ask, copy the answer out. Soon that's as common as knowing email. The people getting noticed build with it. They connect AI to the tools their team already uses. Here's one real example, the weekly sales report that eats someone's Monday morning: The doors. Almost every work app (HubSpot, Jira, Google Sheets, Slack) has an API, a door other software can use. No code needed. n8n. Each door becomes a box on a canvas. A schedule trigger fires every Monday at 7, HubSpot pulls last week's deals, Jira counts open tickets, Sheets brings the target, and one AI step has Claude write the report. Context. Give Claude one page about your team: who reads the report, the quarterly target, and that your manager wants bad news first. Now it sounds like your team, not a stranger. Approval. The draft comes to you in Slack first. Tap approve and it posts to the team at 8. Claude Code. For questions that need judgment ("why did the Acme deal slip?"), plug the same tools into Claude Code. It checks HubSpot, Jira and Slack by itself and answers with sources. The rule to keep: if the steps never change, build it in n8n. If the work needs judgment, give it to Claude Code. It takes a few weekends: learn how APIs work, learn one tool all the way down, then connect your first chore. I teach all of it from zero inside my community, seven courses in order. If you're interested, the link is in my profile. #aiautomation #aiagent #n8n #claudecode

Professor Glitch

25,200 Aufrufe • vor 1 Monat

Here's how to build a Brand Brain in Claude in 5 steps: 1. Create a project. Open Claude and create a new project called Brand Brain. 2. Build your brand kit. Upload your existing colours, logos and fonts. If you don't have any, ask Claude to build you a complete design system. 3. Build your brand voice. Upload anything your business has ever written, like your website, emails or newsletter, then ask Claude to turn it into voice rules: how you sound, the words you use and the words you'd never say. 4. Write your Brand DNA doc. Who your customer is, what problem you solve and what makes you different. Screenshot the template in the video if you don't know what to put in it. 5. Start creating. Open a chat inside your Brand Brain and ask for an ad, a landing page or a social media post. Claude can now build anything for your business and it will actually match your brand. Comment BRAND and I'll send you the complete guide. #claude #claudeai #aitools #branding #nocode
1:04

Here's how to build a Brand Brain in Claude in 5 steps: 1. Create a project. Open Claude and create a new project called Brand Brain. 2. Build your brand kit. Upload your existing colours, logos and fonts. If you don't have any, ask Claude to build you a complete design system. 3. Build your brand voice. Upload anything your business has ever written, like your website, emails or newsletter, then ask Claude to turn it into voice rules: how you sound, the words you use and the words you'd never say. 4. Write your Brand DNA doc. Who your customer is, what problem you solve and what makes you different. Screenshot the template in the video if you don't know what to put in it. 5. Start creating. Open a chat inside your Brand Brain and ask for an ad, a landing page or a social media post. Claude can now build anything for your business and it will actually match your brand. Comment BRAND and I'll send you the complete guide. #claude #claudeai #aitools #branding #nocode

nocode.joshua

14,800 Aufrufe • vor 1 Monat

Why your AI gets dumber the longer you chat (context rot): the one Claude Code file, plus one habit, that fixes it How context rot works: 1. Everything in your chat sits in the AI's working memory, the context window: every message, every file it opened, every answer it gave. The model reads through all of it before every reply. 2. Anthropic, the company behind Claude, says the more tokens you pile into the context window, the worse the model gets at recalling any one thing in it. They call it an attention budget, and every new token spends a little of it. 3. When the window fills up, Claude Code compacts: it replaces the conversation with a summary. If a rule only lived in the chat, it can get lost in that summary. The fix is one file, CLAUDE.md, plus one habit. 4. CLAUDE.md is a plain text file in your project folder. Claude Code reads it at the start of every session, and after compaction it re-reads it from the file. Think of it as a sign bolted above the whiteboard: wipe the board all you want, the sign stays. 5. How to create a CLAUDE.md: open Claude Code in your project folder and type /init. It writes a first draft. Then add what it can't guess: who you are, who the client is, and your rules ("never change a headline without asking", "prices come from column D of the Google Sheet", "dates are day, month, year"). 6. Keep CLAUDE.md short. Anthropic's Claude Code guide says to aim for under 200 lines, because a bloated file gets ignored too. For every line, ask: would it make a mistake without this? If not, cut it. The other half of the fix is how you work: 7. One job, one session. Type /clear when you switch jobs: the board's wiped, and the sign (CLAUDE.md) is still up. 8. If you've corrected the AI twice on the same thing, skip round three in capitals. Clear it, put the rule in CLAUDE.md, and start again. This is context engineering for people who don't code: an AI assistant that remembers your business rules, your clients and your formats, for client work, reports, content, spreadsheets and proposals, whether you're a freelancer, an agency or a small business. #claudecode #aiagents #contextengineering #learnai
2:23

Why your AI gets dumber the longer you chat (context rot): the one Claude Code file, plus one habit, that fixes it How context rot works: 1. Everything in your chat sits in the AI's working memory, the context window: every message, every file it opened, every answer it gave. The model reads through all of it before every reply. 2. Anthropic, the company behind Claude, says the more tokens you pile into the context window, the worse the model gets at recalling any one thing in it. They call it an attention budget, and every new token spends a little of it. 3. When the window fills up, Claude Code compacts: it replaces the conversation with a summary. If a rule only lived in the chat, it can get lost in that summary. The fix is one file, CLAUDE.md, plus one habit. 4. CLAUDE.md is a plain text file in your project folder. Claude Code reads it at the start of every session, and after compaction it re-reads it from the file. Think of it as a sign bolted above the whiteboard: wipe the board all you want, the sign stays. 5. How to create a CLAUDE.md: open Claude Code in your project folder and type /init. It writes a first draft. Then add what it can't guess: who you are, who the client is, and your rules ("never change a headline without asking", "prices come from column D of the Google Sheet", "dates are day, month, year"). 6. Keep CLAUDE.md short. Anthropic's Claude Code guide says to aim for under 200 lines, because a bloated file gets ignored too. For every line, ask: would it make a mistake without this? If not, cut it. The other half of the fix is how you work: 7. One job, one session. Type /clear when you switch jobs: the board's wiped, and the sign (CLAUDE.md) is still up. 8. If you've corrected the AI twice on the same thing, skip round three in capitals. Clear it, put the rule in CLAUDE.md, and start again. This is context engineering for people who don't code: an AI assistant that remembers your business rules, your clients and your formats, for client work, reports, content, spreadsheets and proposals, whether you're a freelancer, an agency or a small business. #claudecode #aiagents #contextengineering #learnai

Professor Glitch

12,200 Aufrufe • vor 28 Tagen

I can't f*cking believe people still use Claude Code like a chat bot. the ones getting real work out of it gave it a folder, tools and a map of everything it knows. that map is graphify. you point it at a folder and it builds a knowledge graph of everything inside. code, docs, PDFs, images, even video. then your agent searches the graph instead of opening files one by one. 134k stars on GitHub. backed by Y Combinator. and most people still haven't tried it. what makes it different: -> the code part runs fully on your machine. nothing gets uploaded -> no vector database, no embeddings. it's a real graph your agent walks through -> every connection is labeled: read straight from the source, or figured out by graphify. you always know which -> you get 3 files: a clickable map you open in your browser, a report with the key ideas and surprising links, and the full graph your agent queries anytime on a public memory benchmark it found the right answer in its top 10 results about half the time. mem0 managed under 5%. and building the graph cost 0 model credits. here's the full setup around it: > create a folder called AGENT, open Claude Code inside it, and add a CLAUDE.md with one line: "save every decision, person and project to memory/" > run uv tool install graphifyy, then graphify install, then type /graphify . and the whole folder becomes a map Claude can search in seconds > run npm install -g @googleworkspace/cli, then gws auth setup and gws auth login. Claude can now read your Gmail, Calendar and Drive > run claude mcp add playwright npx @playwright/mcp@latest. it gets its own browser for sites, forms and data > run npm i -g jev-guard, then jev-guard key "...", then jev-guard install claude. Jev checks every action before it runs. rm -rf gets blocked, emails with hidden instructions get flagged, about 4 cents per 1,000 checks > type /schedule and say "every morning at 7:30, send me what came in, what you drafted and what needs my yes" one folder. 15 minutes. and Claude finally knows where everything is. all the repos: -> -> -> -> bookmark this and try graphify first. it's the piece everyone skips.
0:21

I can't f*cking believe people still use Claude Code like a chat bot. the ones getting real work out of it gave it a folder, tools and a map of everything it knows. that map is graphify. you point it at a folder and it builds a knowledge graph of everything inside. code, docs, PDFs, images, even video. then your agent searches the graph instead of opening files one by one. 134k stars on GitHub. backed by Y Combinator. and most people still haven't tried it. what makes it different: -> the code part runs fully on your machine. nothing gets uploaded -> no vector database, no embeddings. it's a real graph your agent walks through -> every connection is labeled: read straight from the source, or figured out by graphify. you always know which -> you get 3 files: a clickable map you open in your browser, a report with the key ideas and surprising links, and the full graph your agent queries anytime on a public memory benchmark it found the right answer in its top 10 results about half the time. mem0 managed under 5%. and building the graph cost 0 model credits. here's the full setup around it: > create a folder called AGENT, open Claude Code inside it, and add a CLAUDE.md with one line: "save every decision, person and project to memory/" > run uv tool install graphifyy, then graphify install, then type /graphify . and the whole folder becomes a map Claude can search in seconds > run npm install -g @googleworkspace/cli, then gws auth setup and gws auth login. Claude can now read your Gmail, Calendar and Drive > run claude mcp add playwright npx @playwright/mcp@latest. it gets its own browser for sites, forms and data > run npm i -g jev-guard, then jev-guard key "...", then jev-guard install claude. Jev checks every action before it runs. rm -rf gets blocked, emails with hidden instructions get flagged, about 4 cents per 1,000 checks > type /schedule and say "every morning at 7:30, send me what came in, what you drafted and what needs my yes" one folder. 15 minutes. and Claude finally knows where everything is. all the repos: -> -> -> -> bookmark this and try graphify first. it's the piece everyone skips.

kiosa

31,514 Aufrufe • vor 18 Tagen

How to build an entire app with AI, the kind a developer charges $10,000 for You don't need to know how to code to build a real app. You need one idea first: every app has two halves. The restaurant: Front end = the dining room. Everything the customer sees and touches: the menu, the buttons, the booking form. In your app, that's the screens. Back end = the kitchen. The customer never walks in, but that's where the work happens: check the time slot is free, take the payment, save the booking, send the text. Database = the pantry. It stores every customer, every dog, every booking. Close the app, come back next week, and it's all still there. API = the waiter carrying orders between them. The screen asks, the back end answers. Most people only describe the dining room when they ask AI to build something. They get a beautiful app that forgets everything the second they hit refresh. The build, in Claude Code (a dog groomer's booking app): Plan: who it's for, the screens, what the kitchen does and what goes in the pantry, written to a plan file before any code. Front end: the booking page and owner dashboard, previewed in your browser. Point at what's off and it fixes it in seconds. Back end: a free Supabase project gives you two things, a web address for your database and a key. Keys go in one private file called .env: the key drawer in your back office. Then Claude Code connects the booking form and builds the tables. Log-in: email and Google, with Supabase handling the passwords. One rule, row level security: every customer only sees their own bookings. Test it by logging in as two different people. Getting paid: Stripe in test mode (play money). Copy the secret key into the drawer, ask for a $25 deposit with Stripe Checkout, test with 4242 4242 4242 4242. A webhook is Stripe calling your kitchen back to say "paid". The text reminder plugs in the same way with Twilio. Every outside service connects like this: account, key, drawer, sentence. Go live: push to GitHub, import into Vercel, paste the same keys into its settings, deploy. Buy your domain, add it in Vercel, copy two DNS lines into your domain company, and it's live on your own name with the padlock. Before real customers: point the webhook at the new address and swap test keys for live keys. After that, adding more is one sentence: Google Calendar sync, a loyalty card, review requests, or an automation that drops every new booking into your CRM. Your job becomes the owner who tests every button like a customer would. #buildwithai #claudecode #aiagent
4:42

How to build an entire app with AI, the kind a developer charges $10,000 for You don't need to know how to code to build a real app. You need one idea first: every app has two halves. The restaurant: Front end = the dining room. Everything the customer sees and touches: the menu, the buttons, the booking form. In your app, that's the screens. Back end = the kitchen. The customer never walks in, but that's where the work happens: check the time slot is free, take the payment, save the booking, send the text. Database = the pantry. It stores every customer, every dog, every booking. Close the app, come back next week, and it's all still there. API = the waiter carrying orders between them. The screen asks, the back end answers. Most people only describe the dining room when they ask AI to build something. They get a beautiful app that forgets everything the second they hit refresh. The build, in Claude Code (a dog groomer's booking app): Plan: who it's for, the screens, what the kitchen does and what goes in the pantry, written to a plan file before any code. Front end: the booking page and owner dashboard, previewed in your browser. Point at what's off and it fixes it in seconds. Back end: a free Supabase project gives you two things, a web address for your database and a key. Keys go in one private file called .env: the key drawer in your back office. Then Claude Code connects the booking form and builds the tables. Log-in: email and Google, with Supabase handling the passwords. One rule, row level security: every customer only sees their own bookings. Test it by logging in as two different people. Getting paid: Stripe in test mode (play money). Copy the secret key into the drawer, ask for a $25 deposit with Stripe Checkout, test with 4242 4242 4242 4242. A webhook is Stripe calling your kitchen back to say "paid". The text reminder plugs in the same way with Twilio. Every outside service connects like this: account, key, drawer, sentence. Go live: push to GitHub, import into Vercel, paste the same keys into its settings, deploy. Buy your domain, add it in Vercel, copy two DNS lines into your domain company, and it's live on your own name with the padlock. Before real customers: point the webhook at the new address and swap test keys for live keys. After that, adding more is one sentence: Google Calendar sync, a loyalty card, review requests, or an automation that drops every new booking into your CRM. Your job becomes the owner who tests every button like a customer would. #buildwithai #claudecode #aiagent

Professor Glitch

255,900 Aufrufe • vor 1 Monat

How Claude actually gets to know you (7 layers) Every new chat, Claude starts fresh. It only knows what's in front of it. So most people are talking to a stranger every morning. Here's how you change that, one layer at a time: 1. Memory: Claude keeps notes from your chats, and you can open them, read them and fix them. 2. A project: your instructions and your files in one place. Every chat inside it starts with all of it. 3. Skills: write each weekly job down once. Claude reads every skill's name and opens the one that matches. 4. Connectors: your email, calendar and drive, so "prep me for tomorrow" uses your real meetings. 5. Claude Code: a folder on your computer with a CLAUDE.md file. Your business, your rules. Then it makes the files and checks its own work. 6. Schedules: the morning brief is ready at 7. 7. A team: each job gets its own lane, its own tools, its own rules. Then the deep part: leads, sales, onboarding, support and invoicing as one system. One source of truth, events that start the next step, automations for fixed steps, an agent for the messy ones, and guardrails: logs, approvals, alerts. The people who get the most out of Claude are the ones who set it up. #aiagents #claudecode #aiautomation #aiemployee
4:27

How Claude actually gets to know you (7 layers) Every new chat, Claude starts fresh. It only knows what's in front of it. So most people are talking to a stranger every morning. Here's how you change that, one layer at a time: 1. Memory: Claude keeps notes from your chats, and you can open them, read them and fix them. 2. A project: your instructions and your files in one place. Every chat inside it starts with all of it. 3. Skills: write each weekly job down once. Claude reads every skill's name and opens the one that matches. 4. Connectors: your email, calendar and drive, so "prep me for tomorrow" uses your real meetings. 5. Claude Code: a folder on your computer with a CLAUDE.md file. Your business, your rules. Then it makes the files and checks its own work. 6. Schedules: the morning brief is ready at 7. 7. A team: each job gets its own lane, its own tools, its own rules. Then the deep part: leads, sales, onboarding, support and invoicing as one system. One source of truth, events that start the next step, automations for fixed steps, an agent for the messy ones, and guardrails: logs, approvals, alerts. The people who get the most out of Claude are the ones who set it up. #aiagents #claudecode #aiautomation #aiemployee

Professor Glitch

14,300 Aufrufe • vor 18 Tagen

HOLY F*CKING SH*T you waste 20 minutes every morning re-explaining your project to Claude like it has never heard of you, and Karpathy showed you the fix a year ago Andrej Karpathy, co-founder of OpenAI, posted one idea that pulled 16 million views: stop using AI to write code. use it to build a second brain You point Claude Code to a folder, drop any source in there (article, transcript, PDF) and Claude reads it, links it, and saves it into a living wiki of everything you know. it compounds like interest: the more you feed it, the sharper every answer gets Here is the gist: → install Obsidian, create a vault, open it in Claude Code → paste Karpathy's wiki prompt and tell Claude to build it → Claude creates 3 folders: raw for sources, wiki for its pages, CLAUDE.md that runs everything → drop any source into raw and say "ingest this" → ask anything across all of it, forever 5 minutes to set up. and you never open a blank Claude chat again the full step-by-step is in the article below bookmark this before you waste another monday
0:21

HOLY F*CKING SH*T you waste 20 minutes every morning re-explaining your project to Claude like it has never heard of you, and Karpathy showed you the fix a year ago Andrej Karpathy, co-founder of OpenAI, posted one idea that pulled 16 million views: stop using AI to write code. use it to build a second brain You point Claude Code to a folder, drop any source in there (article, transcript, PDF) and Claude reads it, links it, and saves it into a living wiki of everything you know. it compounds like interest: the more you feed it, the sharper every answer gets Here is the gist: → install Obsidian, create a vault, open it in Claude Code → paste Karpathy's wiki prompt and tell Claude to build it → Claude creates 3 folders: raw for sources, wiki for its pages, CLAUDE.md that runs everything → drop any source into raw and say "ingest this" → ask anything across all of it, forever 5 minutes to set up. and you never open a blank Claude chat again the full step-by-step is in the article below bookmark this before you waste another monday

mojesko

98,648 Aufrufe • vor 13 Tagen

i built a small playable game in Unreal Engine with Claude Opus 5.5... no blueprints by hand, Claude worked inside the running editor the trick is the live connection, but there's a smart way to set it up: - step 1: Unreal Engine 5.8 + a Third Person project, under source control - step 2: enable Unreal MCP and AllToolsets, start the server - step 3: install Epic's free plugin for Claude Code and start Claude in the project folder - step 4: build a greybox level first: a path, a walled village, a tower you can see from the start - step 5: add the rules: 3 orbs, a locked gate, "You made it", R to restart - step 6: add one enemy, then health, then your attack, one feature per prompt - step 7: only then make it look good: your character, real assets, lighting and every prompt follows the same 4 rules... - say what "done" means - say what must not change - ask for a list of everything it touched - no silent workarounds: if it can't do it, it stops and says so the full course is in the article 👇🏻
0:27

i built a small playable game in Unreal Engine with Claude Opus 5.5... no blueprints by hand, Claude worked inside the running editor the trick is the live connection, but there's a smart way to set it up: - step 1: Unreal Engine 5.8 + a Third Person project, under source control - step 2: enable Unreal MCP and AllToolsets, start the server - step 3: install Epic's free plugin for Claude Code and start Claude in the project folder - step 4: build a greybox level first: a path, a walled village, a tower you can see from the start - step 5: add the rules: 3 orbs, a locked gate, "You made it", R to restart - step 6: add one enemy, then health, then your attack, one feature per prompt - step 7: only then make it look good: your character, real assets, lighting and every prompt follows the same 4 rules... - say what "done" means - say what must not change - ask for a list of everything it touched - no silent workarounds: if it can't do it, it stops and says so the full course is in the article 👇🏻

rewind

63,322 Aufrufe • vor 1 Monat

How to turn any app idea into a real app with AI, step by step (no developer) How to build a complete app from an idea with AI, no coding, step by step. 1. Shrink the idea: one sentence (who it's for, the one job, how they pay). Cut everything else for version one. 2. Plan before code: in Claude Code, talk it through and have it write a plan file (screens, back end checks, database, AI in the middle). 3. Screens first, with fake data. Click through it like each user. 4. Make it real: a free Supabase project for the database and logins. Keep the secret key private. 5. Money: connect Stripe and test with test cards first. 6. Break it on purpose: duplicate names, declined cards, abandoned checkouts. Have Claude Code write tests and fix what fails. 7. Go live: GitHub → Vercel → your own domain. Heads-up: a business taking payments needs Vercel Pro ($20/month), not the free plan. 8. Five real users. Watch where they get stuck. This is the three-minute version. The full walkthrough is in my vibe coding course, inside a community of 800+ people, from complete beginners to people who have been in tech for years. Check my profile. #vibecoding #buildwithai #claudecode #aiagents #aiemployee #aiautomation
3:21

How to turn any app idea into a real app with AI, step by step (no developer) How to build a complete app from an idea with AI, no coding, step by step. 1. Shrink the idea: one sentence (who it's for, the one job, how they pay). Cut everything else for version one. 2. Plan before code: in Claude Code, talk it through and have it write a plan file (screens, back end checks, database, AI in the middle). 3. Screens first, with fake data. Click through it like each user. 4. Make it real: a free Supabase project for the database and logins. Keep the secret key private. 5. Money: connect Stripe and test with test cards first. 6. Break it on purpose: duplicate names, declined cards, abandoned checkouts. Have Claude Code write tests and fix what fails. 7. Go live: GitHub → Vercel → your own domain. Heads-up: a business taking payments needs Vercel Pro ($20/month), not the free plan. 8. Five real users. Watch where they get stuck. This is the three-minute version. The full walkthrough is in my vibe coding course, inside a community of 800+ people, from complete beginners to people who have been in tech for years. Check my profile. #vibecoding #buildwithai #claudecode #aiagents #aiemployee #aiautomation

Professor Glitch

10,700 Aufrufe • vor 1 Tag

are video editors cooked? I had claude code edit a video about editing with claude code, and I didn't touch a single cut. that's the edit playing on the review page where I leave notes. here's the setup it walks through: 1. download the claude desktop app and open claude code so it can work on the files on your computer. 2. grab my video editor agent. it's a public repo on my GitHub. open the folder in claude code, hand it the GitHub link and say "help me set this up". 3. give it a style. send it a reel you love and it turns the editing into a style guide you can reuse. 4. film like you normally would, drop the raw footage in a folder and ask claude code to edit it. it cuts the dead space and adds the captions, motion graphics, sound effects and ai music. 5. before it renders anything it shows you a storyboard of every line. 6. it puts the cut on a review page. you leave notes on the exact second you want changed and it builds the next version. I think video editors might be cooked. was the edit awesome or was it slop?
1:48

are video editors cooked? I had claude code edit a video about editing with claude code, and I didn't touch a single cut. that's the edit playing on the review page where I leave notes. here's the setup it walks through: 1. download the claude desktop app and open claude code so it can work on the files on your computer. 2. grab my video editor agent. it's a public repo on my GitHub. open the folder in claude code, hand it the GitHub link and say "help me set this up". 3. give it a style. send it a reel you love and it turns the editing into a style guide you can reuse. 4. film like you normally would, drop the raw footage in a folder and ask claude code to edit it. it cuts the dead space and adds the captions, motion graphics, sound effects and ai music. 5. before it renders anything it shows you a storyboard of every line. 6. it puts the cut on a review page. you leave notes on the exact second you want changed and it builds the next version. I think video editors might be cooked. was the edit awesome or was it slop?

Mr. Paid Social

235,700 Aufrufe • vor 13 Tagen

We spent months building this so you don't have to figure it out alone. A free 7-day course that takes you from zero to building real things with AI, no coding background, no expensive tools, no fluff, just results. From 0 -> to Claude code expert, completely free: > In 7 days, you’ll learn vibe coding, set up Claude Code, build your first AI app, create a prompt-built website, automate a task with n8n, and deploy it live to a real URL. No theory, no filler, just a real project you can show people by the end of the week. For those who want to go further, we spent even longer building another one, designed for people who are genuinely interested in AI deep learning and launching products. From Expert to Your First $10k Product {You can find it on the link above as well} The complete masterclass, full-stack AI apps, Supabase, n8n automations, AI agents, Telegram bots, SaaS products built from scratch, Stripe, subscriptions, client work, freelancing, pricing and scaling. This is the course that turns the skill into actual income. Me and Noisy put everything we know into both of these, you can start free, build something real, then decide how far you want to take it.
0:21

We spent months building this so you don't have to figure it out alone. A free 7-day course that takes you from zero to building real things with AI, no coding background, no expensive tools, no fluff, just results. From 0 -> to Claude code expert, completely free: > In 7 days, you’ll learn vibe coding, set up Claude Code, build your first AI app, create a prompt-built website, automate a task with n8n, and deploy it live to a real URL. No theory, no filler, just a real project you can show people by the end of the week. For those who want to go further, we spent even longer building another one, designed for people who are genuinely interested in AI deep learning and launching products. From Expert to Your First $10k Product {You can find it on the link above as well} The complete masterclass, full-stack AI apps, Supabase, n8n automations, AI agents, Telegram bots, SaaS products built from scratch, Stripe, subscriptions, client work, freelancing, pricing and scaling. This is the course that turns the skill into actual income. Me and Noisy put everything we know into both of these, you can start free, build something real, then decide how far you want to take it.

Defileo🔮

695,073 Aufrufe • vor 6 Monaten

This is the holy grail for building n8n workflows with Claude... Just discovered n8n-MCP and it is literally game-changing... It gives Claude deep knowledge of all 525+ n8n nodes instantly. Your AI goes from guessing to deeply understanding how n8n works. Video setup guide + git repo below 👇
3:24

This is the holy grail for building n8n workflows with Claude... Just discovered n8n-MCP and it is literally game-changing... It gives Claude deep knowledge of all 525+ n8n nodes instantly. Your AI goes from guessing to deeply understanding how n8n works. Video setup guide + git repo below 👇

Tom

172,130 Aufrufe • vor 1 Jahr

It is becoming f*cking dangerous: when Anthropic shipped CLAUDE.md, they didn't even realize they were opening a Pandora's box 1. Make an empty folder on your computer, call it SECOND BRAIN 2. Open Claude Code inside it 3. Add subfolders: MEMORY/, notes/, people/, projects/ 4. Drop a CLAUDE.md in the root with one rule: save every key fact to MEMORY, one topic per file 5. Add @-links in CLAUDE.md so key files load into context every session 6. Run claude mcp add to connect Playwright MCP, now Claude controls a real browser 7. Build a skill in .claude/skills/ so one command runs the entire routine Folder setup: about 5 minutes Your Claude becomes a second brain: it keeps every key fact between sessions, loads your main files by itself and drives a real browser Full guide in the article below
0:43

It is becoming f*cking dangerous: when Anthropic shipped CLAUDE.md, they didn't even realize they were opening a Pandora's box 1. Make an empty folder on your computer, call it SECOND BRAIN 2. Open Claude Code inside it 3. Add subfolders: MEMORY/, notes/, people/, projects/ 4. Drop a CLAUDE.md in the root with one rule: save every key fact to MEMORY, one topic per file 5. Add @-links in CLAUDE.md so key files load into context every session 6. Run claude mcp add to connect Playwright MCP, now Claude controls a real browser 7. Build a skill in .claude/skills/ so one command runs the entire routine Folder setup: about 5 minutes Your Claude becomes a second brain: it keeps every key fact between sessions, loads your main files by itself and drives a real browser Full guide in the article below

plusxbt

69,512 Aufrufe • vor 19 Tagen

Claude + n8n just automated an entire YouTube channel in 1 evening. No editor. No script writer. No camera. Here’s the exact setup: → Claude installed on desktop, connected to n8n via MCP → Project instructions define the workflow logic → 1 prompt triggers the entire pipeline: research, script, structure, output The workflow builds itself inside n8n. 1 link. Channel opens. Content is already queued. Most people are still writing scripts manually in 2025. A few set this up once and let Claude run the operation. Comment GUIDE and I’ll send over the full build.
0:29

Claude + n8n just automated an entire YouTube channel in 1 evening. No editor. No script writer. No camera. Here’s the exact setup: → Claude installed on desktop, connected to n8n via MCP → Project instructions define the workflow logic → 1 prompt triggers the entire pipeline: research, script, structure, output The workflow builds itself inside n8n. 1 link. Channel opens. Content is already queued. Most people are still writing scripts manually in 2025. A few set this up once and let Claude run the operation. Comment GUIDE and I’ll send over the full build.

RGK

12,181 Aufrufe • vor 5 Monaten