Memuat
Memuat
Want to go deeper?
Join one of our courses or ask us directly on WhatsApp.
Picked from the software, topic, and level of “Claude from Zero to Expert Class #23: Filling Project Knowledge with Files”.
Other ways we can help with Claude.
Learn with a mentor
Scheduled AI & Machine Learning courses with live guidance and a certificate.

Midjourney Course: Create Stunning AI Images from Text
★ 4.9

DALL-E Course: Creating Professional AI Images from Text
★ 4.9

Stable Diffusion Course: AI Art from Beginner to Professional
★ 4.9
Have it built for you
No time to learn Claude? Our team can do the project for you.

AI Image Creation with Stable Diffusion — Unlimited Custom Visual Production
★ 4.9

AI Image & Video Creation with Leonardo AI — All-in-One Visuals for Business
★ 4.9

AI Image Creation with Midjourney — Cinematic AI Art for Business
★ 4.9
Get notified about new Claude classes
At most one email a week. Unfollow anytime with one click.
The full narration of this video. The current sentence is highlighted while the video plays; click any sentence to jump there.
Hi, let's continue the Claude Projects session. The instructions are strong; now we fill in the second part of a Project: knowledge, in the form of files. In this episode we choose suitable files, tidy them up, upload them to the Project, ask questions based on their content, and maintain them so they don't go stale.
First question: which files deserve a place in a Project? The most useful are the price list and catalog, with products, sizes, prices, and shipping rules. Second, the FAQ: the collection of questions customers ask often, along with the official answers. Third, SOPs, or standard operating procedures, such as the steps for handling complaints, returns, or large orders. Fourth, examples of your best writing. Replies or captions customers have clearly loved are the easiest style examples for Claude to imitate. Fifth, a brand style guide: words you always use, such as a warm greeting for customers, and words you avoid. On the other hand, there are four kinds of files you shouldn't upload. First, customers' personal data, such as full names, addresses, and phone numbers. A Project is for knowledge, not a customer database. Second, passwords, bank account numbers, or confidential financial data. The safety rules from the very first episode still apply here. Third, outdated files. If an old price list stays in the Project, Claude may use the wrong prices. Fourth, blurry or cropped photos of documents. Claude can read images, but clear text is always more accurate. The rule is simple: if you wouldn't pin a document on the office notice board, don't upload it to a Project. Keep sensitive documents in places designed for them.
Tidy files make answers far more accurate. Compare the file names: final document, bracket three, explains nothing, while menu and prices November makes the content and date clear right away. In terms of content, the messy file mixes prices, personal notes, and recipes. The tidy file holds just one topic. The layout differs too. Long paragraphs without headings are hard to search, while headings, bullets, and tables help Claude find the right section. Finally, the form. A tilted screenshot can be misread. Save it as text, such as PDF, Word, or a spreadsheet. What if your notes are still messy? Ask Claude to tidy them first, in a regular chat. Laras pastes the customer questions Dimas collected over a month and asks for an FAQ format. Claude groups the questions by topic, puts them in bold, and keeps the answers short. Laras checks the content, saves it as an FAQ file, and it's ready to upload to the Project. This saves time and produces a tidier file than retyping it yourself. What matters is that the official answers are still decided by the business owner. Let's sum it up as four habits. First, one topic per file. Keep the menu, FAQ, and SOPs separate; don't merge them into one giant document. Second, file names include the content and the date, so you know right away which version is newest. Third, use headings and bullet points. Clear sections are easier to find, both for Claude and for you. Fourth, check before uploading. A person still has to review Claude's cleanup, because this file becomes the source of truth for every chat.
Now let's fill the Project. Notice the instructions have one new sentence: answer from the knowledge files, and if it's not there, write needs admin check. Laras clicks Add and uploads the first file, the November menu and prices, with four products, shipping, and opening hours. Then the second file, the FAQ she just tidied up, covering ordering, delivery, and payment. The third file is the complaint SOP, the official steps for handling customer complaints. With this file, Claude knows that replacement decisions are up to Laras. The fourth file holds eight of the best replies. Besides uploading files, some versions of Claude also let you paste text directly as knowledge. Look at the capacity bar above the file list. It shows how much knowledge space is used. File size and type limits can change, so check the official Claude documentation for the latest numbers. The order is always the same. First, gather the documents you refer to most often while you work. Second, tidy them: one topic per file, with a clear name. Third, upload them with the Add button in the Project. Fourth, test with questions whose answers you know are in the files. That tells us whether Claude is really using them.
Time to test. Dimas pastes a complaint about a cold brew that's no longer cold, and asks Claude to name the source file. Claude writes a reply that follows the SOP: apologize, ask for a photo and the time received, then pass it to Laras. Below it says: source, complaint SOP, steps one and two. Dimas can check it himself if he's unsure. The second test deliberately asks about something that isn't in the files: is there pandan-flavored coffee? Claude doesn't invent a menu item. It writes needs admin check and adds a note that pandan flavor isn't in the menu file. This is exactly the behavior we want. These two tests prove two things: Claude uses the right file, and Claude dares to say it doesn't know. If either one fails, check your instructions and file contents again. These three phrases are powerful when asking questions in a Project. First, name the source file. That way every answer can be double-checked. Second, answer only from the knowledge files. This phrase stops Claude from filling gaps with guesses. Third, if it's not there, say so. It's better for Claude to honestly not know than to make up a price or a rule. If you always use these three phrases, just move them into the Project instructions so they apply automatically in every chat.
A new month arrives, and Sunset Coffee has a year-end promo. Notice that Laras has also moved those three powerful phrases into the instructions: answer only from the files and name the source. Laras deletes the old November menu file, then clicks Add and uploads the December menu. If the old file stayed, Claude could get confused about which price is right. After that she opens a new chat and asks about the year-end promo, to make sure Claude uses the new file. In the new chat, Dimas asks whether there's a year-end promo and asks for the source file. Claude answers based on the December menu and names that file as the source. That means the new file has been read, and the old one no longer gets in the way. The change took five minutes. So you don't forget, set up a simple schedule. Whenever prices or rules change, replace the file and delete the old version. Once a month, review all the files in the Project and remove the ones no longer in use. After every change, retest with two or three questions, just like we did earlier. And keep the original copy of every file on your computer or drive. A Project is a workspace, not your only storage.
We've chosen suitable files, tidied them up, uploaded them to the Project, asked questions that name their source, and maintained the files so they don't go stale. In the next episode we practice in full: combining instructions, files, and testing into a Sunset Coffee customer service Project that Dimas can use every day. See you there!
Try these on your own after watching to lock in what you learned.
Type a question or keyword; we find the part of this episode that explains it and jump the video there.
Notes are saved with the current video time and are only visible to you.
Stuck on a step? Ask here; the instructor and other learners can answer.
No questions yet.

Cerdas Inovasi Digital Team
Software developers, BIM & 3D engineers, and AI practitioners
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.
See our clients →