A Beginner’s Guide to Claude: Five Prompts You Can Use Right Away

Key takeaway: If you are new to Claude, first describe one task to solve now and the answer format you want instead of memorizing elaborate commands. Questions showing what the answer is for are also easier to revise and review. The examples below are practice prompts for adaptation, not reports of actual execution results.

1. Begin Your First Conversation with One Small Task

Claude is a conversational AI provided by Anthropic. On the web, you can access it at claude.ai. The official getting-started guide recommends beginning with a simple question and refining it through follow-ups. Check access and account conditions in the official getting-started documentation.

For your first exercise, choose something whose correctness you can judge, such as “Briefly organize the sentences I wrote.” Starting with unfamiliar historical facts or recent news makes it difficult to distinguish an attractive answer from a correct one. First learn the relationship between questions and answers through a task with short source text and a clear purpose.

2. State Purpose, Material, and Format

It helps to organize your question around “what to communicate to whom,” “which material to use,” and “how many lines or what format to receive.” For example, “Separate decisions from unresolved items in the notes below so a colleague who missed the meeting can read them” makes review criteria easier than “Summarize this.”

목적: 회의 내용을 동료에게 공유하려고 합니다.
자료: 아래에 붙이는 회의 메모만 사용하세요.
형식: 결정 사항 / 담당자 / 미정 사항으로 정리하세요.
규칙: 메모에 없는 담당자나 날짜는 '미정'으로 표시하세요.
메모: [개인정보를 지운 메모를 붙여 넣기]

This example asks AI not to fill missing owners or schedules with guesses. Compare the names and dates in its answer directly with the source. A table matching the original comes before one that merely looks good.

3. Prompts You Can Adapt Immediately

• Email draft: “Write an email announcing a schedule change based on the situation below. The recipient is our business partner's contact. Give the reason in one sentence and the new schedule on a separate line; do not include unconfirmed dates.”
• Learning a technical term: “Explain caching to someone learning it for the first time. Include one everyday analogy and one computer example, and state how the analogy differs from actual operation.”
• Organizing tasks: “Divide the list below into tasks for today and later. Use only the duration estimates I supplied and add one line explaining each priority.”
• Refining sentences: “Keep the facts in the announcement below and reduce only repeated wording. Do not add benefits or promises absent from the original; give three reasons for your changes.”
• Comparing explanations: “Compare whether the two explanations below mean the same thing. Separate matching parts, differing conditions, and matters the source text cannot resolve.”

Fill in the material inside brackets before sending your question. A natural-sounding answer without provided material may be a draft based on assumptions rather than actual content. For sentence exercises, replacing names and customer information with fictional values is sufficient.

4. Revise Answers You Do Not Like

Instead of just “try again,” identify what to change. Specifying both the target and information to preserve—“The second paragraph is too long. Keep the key schedule and shorten it to two sentences”—makes the next answer easier to compare. Clear requests, necessary background, staged work, and follow-up feedback are also basic directions presented in the official prompting guide.

If revision requests accumulate, gather the final conditions once: “Final conditions: polite tone, four sentences, use only October 12 as the date.” This provides criteria for choosing an answer. Replace that date with a genuinely confirmed one.

5. What to Check Before Copying

Check recipients and schedules in emails, omitted conditions in summaries, and terms and exceptions in technical explanations. Compare action-affecting expressions such as “possible,” “always works,” and “free” against source material or official guidance. Asking AI to cite a source and actually opening it are separate actions.

Keep practice records in three columns: question, answer received, and corrected conditions. The aim is to discover recurring conditions in frequent tasks rather than collect long prompts. Adjust your question when material or audience changes, even for the same task format.

6. Choose a First Task Based on Your Situation

For practice, first choose work whose AI answer you can judge. This is a sequence for learning what information questions require, not a demand to delegate only easy tasks. Requests to understand explanations and to create drafts for others require different review items.

Current situation	Information for the first request	What to inspect in the answer
Refining announcement text	Audience, confirmed schedule, facts to preserve	Whether new promises were added
Learning an unfamiliar term	Current knowledge and purpose of understanding	Whether analogy and actual definition are distinguished
Organizing notes	Original text and criteria separating decisions from opinions	Whether a missing owner was guessed
Classifying tasks	Deadlines, durations, and what must finish first	Whether tasks fit the available time
Comparing two explanations	Both original texts and comparison items	Whether seemingly identical wording has different conditions

For example, “make it understandable to a middle school student” alone may lead to broad assumptions about background. Try stating what is already known: “The reader knows how to save files and open folders, but is learning servers and networks for the first time.” This also makes missing explanations easier to judge yourself.

7. Turn Fictional Meeting Notes into a Usable Draft

The following fictional notes were created for this article, not obtained from a meeting or Claude execution. Names and dates are illustrative and must be replaced with confirmed information for actual work.

[가상 원문]
수진: 안내 초안은 10월 8일 오전까지 정리하기로 함.
민호: 배너 이미지 후보 두 개를 이번 주에 보여 주겠다고 함.
공개 날짜는 다음 회의에서 결정.
메일로 알릴지 블로그에 올릴지는 의견만 나왔고 결정하지 않음.
오늘 초안 담당은 수진. 배너 최종 승인자는 정하지 않음.

The source distinguishes a confirmed schedule from an undecided release date. “This week” is not an absolute date and cannot become “by October 9” without confirmation. Keeping relative dates and unresolved opinions separate is central to organizing meeting notes.

아래 회의 메모에서 결정 사항만 정리해 주세요.
1. 확정된 업무는 업무 / 담당자 / 기한으로 표시하세요.
2. 상대 날짜는 원문 그대로 두고 '기준 날짜 필요'를 붙이세요.
3. 공개 날짜·승인자·전달 채널처럼 미정인 것은 별도 목록에 넣으세요.
4. 의견을 결정으로 바꾸지 마세요.
5. 마지막에 추가로 물어볼 질문을 세 개 이내로 작성하세요.
메모: [원문 붙여 넣기]

Author-created organization example	Display according to the source
Guidance draft	Sujin / by the morning of October 8
Present banner candidates	Minho / this week; reference date needed
Release date	To be decided at the next meeting
Banner approver and delivery channel	Undecided

This self-created table illustrates the desired organization. When comparing actual responses, check whether dates and roles match the original rather than counting columns. For next steps, ask “What is the reference date for this week?”, “Who approves the banner?”, and “When will the delivery channel be decided?”

8. Adapt the Five Questions to Your Situation

Add the recipient and requested action to the email prompt. The closing differs depending on whether recipients only need to check the notice or must reply about the new schedule. State the real purpose: “Only announce the changed schedule without requesting a reply,” or “Include a sentence asking them to confirm availability by Friday.”

Separate fixed appointments from free time when organizing tasks. If a meeting runs from 2 to 3 p.m. and only 90 minutes are available today, an answer placing all three tasks of 40, 35, and 30 minutes on today's list violates the time condition. For tasks with unknown durations, request “time undecided” rather than presenting estimates as facts.

아래 할 일에서 오늘 90분 안에 마칠 순서를 제안해 주세요.
고정 일정은 바꾸지 말고, 내가 적은 소요 시간만 사용하세요.
작업을 쪼갠다면 먼저 끝낼 부분과 남는 부분을 구분하세요.
자료가 부족한 일은 '착수 전 질문 필요'에 넣어 주세요.
이 계획은 제안이며 확정 일정과 구별해 표시하세요.
목록: [일 / 마감 / 소요 시간 / 선행 조건]

Specify words to preserve when refining text. Lists are useful for unchangeable product names, menu names, and responsible departments. For comparisons, identifying meaning-changing items such as period, eligibility, and mandatory status clarifies the answer's intended use more than merely finding matching expressions.

9. Specific Follow-Ups When an Answer Goes Off Track

• Content added: “The benefit in the third sentence is absent from the original. Delete that sentence and retain only information confirmed in the source.”
• Decisions and opinions mixed: “Sending the email is an opinion. Move it from confirmed to undecided items and remove the related schedule too.”
• Language too difficult: “For readers hearing ‘server’ and ‘port’ for the first time, add a one-sentence explanation of each. Also state in one line how the analogy differs from reality.”
• Answer too short: “Do not expand the background; add the steps I should follow, required materials, and things to ask about when it fails.”

Instead of changing style, facts, and structure together, correct factual differences from the source first. Adjust length and wording afterward so each revision's effects are easier to compare. Save not only successful wording but also a line about omitted conditions for reuse in your next request.

Frequently Asked Questions and Troubleshooting

Can I ask in Korean? Start by writing your purpose and materials in Korean. Include preferred terminology if you have any. Are longer questions better? It is better to include all necessary task conditions than to expand unnecessary background. What if the first answer is wrong? Identify the incorrect sentence, provide the evidence again, and check the revised answer yourself too.

Official Sources and Date Checked

• Get started with Claude
• My prompt isn’t giving me a helpful answer

Official documentation checked: October 3, 2026. Screens and availability conditions may change afterward.