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 #35: Setting Response Style and Personal Preferences”.
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, and welcome to the last episode of the Daily Productivity session. So far we've often typed the same requests: keep it short, use plain English, don't be too formal. In this episode we set Claude up just once, through personal preferences and response styles, so it answers the way we like in every conversation.
When do we need to set preferences? The first sign: you repeat the same request every day, such as keep it short, use plain English, and no emoji. The second sign: Claude's answers are often too long or too short, so you have to trim them or ask again. The third sign: the tone doesn't fit. Too stiff for replying to customers, or too casual for a report to your boss. All three problems can be set up just once. Take Laras, for example. Every morning she retypes the same sentence: I own Sunset Coffee, answer in a casual tone. Fifteen seconds isn't long, but done dozens of times a day, it adds up. Before setting anything up, get to know the four layers of settings. The first layer is personal preferences. They apply to every conversation, for example who you are and the language you use. The second layer is the response style. A style controls how Claude writes, for example concise or full of explanation, and you can switch it at any time. The third layer is Project instructions, which we learned in the Projects session. Those rules apply only inside one Project, such as Sunset Coffee's customer reply rules. The fourth layer is a regular prompt in the chat. It applies only to that conversation, for one-off tasks. The rule is simple: what's always true about you goes into preferences, how to write goes into a style, rules for one job go into a Project, and a one-time request just goes in the chat.
Step two is writing personal preferences. Here's Dewi's example, in four parts. First, her role: an operations manager who often writes emails, reports, and meeting minutes. Second, the format: plain English, start with the main point, then details if needed, and use tables for data. Third, the constraints: no emoji in office documents, and if information is missing, Claude must ask first instead of guessing. Fourth, the goal: results she can send right away after reading them through once. A goal like this helps Claude judge how polished the answer needs to be. These preferences go into the settings menu, in the profile section. The screen in this video is a simulation, and menu names may differ slightly because Claude is updated often. First, Dewi fills in what Claude should call her. Then her work: operations manager at an office stationery distributor. In the preferences box, Dewi pastes a summary of those rules. Once saved, these rules carry over into every new conversation without being retyped. One important warning: don't write sensitive data here, such as bank account numbers, your home address, or passwords. Preferences only need to describe how you work. After saving, Dewi opens a new conversation to test it. She writes just one short sentence: write an email to the paper supplier about a late delivery. No extra rules. Claude doesn't start writing right away. Following her preferences, it first asks for the supplier's name, the order number, and the deadline. It also says the email will open with the main request, with no emoji. This is the sign that preferences are working. Dewi didn't type any rules, yet Claude already follows the way she works. Compare that with before, when the same rules had to be typed every morning.
Step three is choosing a response style. Claude usually offers several built-in styles. The normal style suits most work. The list of styles in your app may be slightly different. The concise style suits busy moments when you only need the core answer. The explanatory style suits learning a new topic, like in the previous episode, because Claude includes the reasons and the steps. The formal style suits official letters and reports to your boss. You can pick a style near the chat box and switch it at any time in the middle of your work. So a style doesn't change who you are in Claude's eyes. It only changes how Claude delivers the answer, just as we speak differently to customers, bosses, and friends. Let's see the difference. Dewi uses the concise style and asks why deliveries to the Sinar store were late, with the data included. The answer is just two sentences: three causes and the biggest one. That's enough for Dewi herself while she's in a hurry. Then Dewi needs an explanation for the Sinar store. She switches to the formal style and asks for an explanatory paragraph. The content is the same, but the tone changes completely. There's an apology, a polite explanation, and a fix. One set of data, two styles, for two different readers.
Step four is creating your own style. Nadia, a social media freelancer, wants Claude to write like her. She gives it her three best captions for small business clients. Claude reads all three samples and looks for patterns in her writing. The result is four features: a light question to open, casual language that speaks straight to the reader, just enough emoji, and always a clear call to action at the end. The style is saved as Nadia Casual. Pick samples that truly represent your voice. If the samples are a mixed bag, the resulting style will be a mixed bag too. Now Nadia tests her style on a real task: a cold brew caption for her client, Sunset Coffee. The result feels like Nadia's own writing. It opens with a light question, has one emoji, mentions the price, and ends by inviting people to order via DM. Nadia gives just one correction for this client: replace gonna with going to. A small adjustment like this can be saved into the style, or simply written in a Project instruction just for that client. With her own style, Nadia saves a lot of time. She no longer rewrites Claude's results to make them sound like her.
The last step is testing and maintaining. After changing your preferences or style, test them with three real questions from your daily work. If the results aren't right yet, change one rule at a time. That way, you know which rule made the difference. Update your settings when your role or work changes. Preferences written a year ago may no longer fit. Remember too that a request in the chat can still change the direction of an answer. If your preferences say concise, you can still ask for a long explanation for one question. And once again: don't write sensitive data in your preferences, including in writing samples for a style. Remove customer names and numbers from any samples you use first. Let's sum up the four layers. Preferences hold who you are, your language, and the limits that always apply. A style controls how Claude writes, and you can switch it to suit the reader. A Project holds the rules for one particular job. And a prompt in the chat is for one-time requests. With these four layers set up neatly, Claude becomes an assistant that knows how you like things, and your daily work routine feels much lighter.
We've finished the Daily Productivity session: weekly plans, meeting minutes, brainstorming, learning new topics, and now preferences and response styles that help Claude understand how we like things. In the next episode we move up to the intermediate level in the Intermediate Artifacts session, starting with an interactive sales dashboard built from your own business data. 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 →