At most one email a week. Unfollow anytime with one click.
Transcript
The full narration of this video. The current sentence is highlighted while the video plays; click any sentence to jump there.
Show transcript
Introduction
Hi, and welcome back. Laras has just sent a folder of materials for the Sunset Coffee website. Before building anything, we need to know what's inside. In this episode we ask Claude to read and explain the project, find data that must not go live, and then understand what each option in the permission box means.
Step 1: Asking Claude to read the project
Raka copies Laras's materials folder into the project folder. Then Raka asks Claude to explain its contents in simple language, adding an important sentence: don't change anything yet. Claude starts by listing the files. The result: sixteen files in two folders. This only looks at the list; it doesn't open any files yet. Because it's only reading, no permission box appears. Next, Claude reads the about file, which holds a short story of Sunset Coffee written by Laras. Then Claude reads the testimonials file, with what several customers think of the coffee. The summary is clear: story text and testimonials, twelve product photos, and a logo. The most valuable part comes at the end: the full address and the business WhatsApp number are missing. Why does this reading step matter? First, Claude understands the state of the project, so the next instructions hit the mark better. Second, gaps show up early. Raka messages Laras right away to ask for the shop's address and the business WhatsApp number, before the page is built. Third, there's no risk. Reading doesn't change any files. Make it a habit to start every new project this way, including folders built by someone else. Apply this to your business too. Gather your website materials in one folder, then ask Claude to explain what's there and list what's still missing.
Step 2: Asking about the project's contents
Now Raka asks: of the twelve photos, which one fits best at the very top of the page? Claude can look at images. It opens all twelve photos one by one, still without changing anything. The answer comes with a reason: the iced coffee photo has warm light and empty space for a title. Claude also points out that two other photos are a bit blurry. The next question is far more important: is there any customer personal data in this folder? Anyone can see a website, so this question is a must before using any material. Claude uses the Grep tool, a pattern finder that searches many files at once. It looks for phone number and email patterns, and finds one matching file. It turns out the testimonials file contains Rina's and Budi's phone numbers. If that went live on the website, anyone could see them. Claude offers to remove just the numbers.
Step 3: What the permission box means
Before answering Claude's offer, let's understand when the permission box appears. First, reading files, such as Read and Grep, usually isn't asked, because it doesn't change anything. Second, creating or changing files, meaning Write and Edit, is always checked with you first. Third, running computer commands through Bash, such as renaming, moving, or deleting files, is also asked. Fourth, accessing the internet, such as opening a web page, is asked too. These are the default settings; the details can differ and can be adjusted, so check the official documentation for the latest version. The permission box has three options. First, Yes: approve just this once. It's the safest choice for most work. Second, Yes and don't ask again: approve, and don't ask again for similar work during this session. Handy for safe, repeated work, such as editing the same page file many times. Third, No: decline. Claude stops and waits for our directions. Choose No whenever you're in doubt, then explain what you actually want. No option is wrong as long as we read it consciously. What's dangerous is pressing Enter without reading, just to finish faster. Let's see when the No option is used. Raka asks Claude to fix the typos in the Sunset Coffee story file. Claude uses Edit and is about to change one line. Raka reads the change box. The word Bandung really was a typo, and it's been fixed. But wait, the founding year has also changed, from twenty nineteen to twenty twenty. Changing a fact isn't part of fixing typos. Raka chooses No, so the file isn't touched at all. Then Raka gives a more precise direction: the Bandung fix is right, but don't change the year. Without reading the red and green lines, a small mistake like this could go live on the website.
Step 4: Reading the permission box in practice
Raka accepts the earlier offer with a firm direction: remove just the phone numbers, and keep the names and testimonials. Claude uses the Edit tool and says two lines will change. That number makes sense, because there were exactly two customers with numbers listed. Look at the change box. The red lines with phone numbers are removed and replaced by green lines with only the name and testimonial. The praise itself is exactly the same. Raka checks: names kept, content kept, numbers gone. That's what was asked for, so Raka chooses Yes. A small, clear edit like this only needs approval once. The next request is a different kind: renaming the twelve photos to product one through product twelve, so they're tidy to use on the website. This time Claude uses Bash to run a computer command. A command like this touches many files at once, so it waits for permission. Raka reads the permission box: the command renames files, there are twelve of them, and the folder is right. Raka chooses Yes, not don't ask again. For commands that rename, move, or delete, approve them one at a time. Claude is done. The chosen photo is now called product one. Claude even saved the list of old names in a notes file. If Laras later looks for a photo by its old name, Raka can still trace it.
Step 5: Plan mode and safe habits
For big jobs, there's a calmer approach: plan mode. Look at the very bottom line; it says plan mode. In this mode Claude only reads and makes a plan, without changing files. The way to switch modes can change, so check slash help. Raka asks for a plan of the page sections. Claude suggests five: a hero section with the chosen photo, the menu and prices, the Sunset Coffee story, testimonials, and the hours, address, and WhatsApp button. Raka agrees and saves the plan to build later. With plan mode, we can judge the direction of the work before a single file changes. Let's finish with five safe habits. First, read the file name and command in the permission box. Make sure it's the file you actually want to change. Second, look at the red lines. Red lines mean something is being removed. Make sure what disappears is okay to lose. Third, choose No whenever you're in doubt. Declining is safe; Claude will wait for our explanation. Fourth, don't choose don't ask again for commands that delete or move files. Approve them one at a time. Fifth, back up the folder before big changes. The screens in this video are simulations, and the permission options may differ slightly, but these habits always apply.
Done!
We've asked Claude to read and explain the website materials, found and removed customers' phone numbers, understood the three permission options, and tried plan mode. In the next episode we create a CLAUDE.md file, standing notes about Sunset Coffee that Claude reads every time it starts working. See you there!
Practice exercises
Try these on your own after watching to lock in what you learned.
Ask Claude to explain your business materials folder without changing anything
Ask whether there's any personal data in that folder, then clean it up if there is
The next time a permission box appears, read the file name and command before choosing
Ask the class material
Type a question or keyword; we find the part of this episode that explains it and jump the video there.
My notes
Notes are saved with the current video time and are only visible to you.
Questions & answers
Stuck on a step? Ask here; the instructor and other learners can answer.
No questions yet.
Your instructor
Cerdas Inovasi Digital Team
Software developers, BIM & 3D engineers, and AI practitioners
53 video classes1,286 episodes
We build software, BIM models, games and AI automations for clients every day, and turn that hands-on work into step-by-step classes: every step is shown on screen and comes with a PDF guide you can keep.
