Claude обучен на структурированных промптах с XML-тегами — это нативная функция модели. По данным официальной документации Anthropic, XML-теги остаются «инструментом с наибольшей значимостью» для сложных задач, поскольку устраняют двусмысленность между тем, где заканчивается контекст и начинается инструкция. При этом в 2026 году для простых вопросов тяжелые ролевые промпты уже не обязательны — современные модели Claude 4.x одинаково хорошо реагируют на простые инструкции, а XML-структура максимально полезна, когда промпт содержит несколько секций или требует консистентного формата вывода.
Ниже — коротко о том, что делает промптинг для Claude особенным, и больше 55 готовых промптов по категориям: документы, кодинг, учеба, бизнес, личная продуктивность и продвинутые техники вроде chain-of-thought.
Claude без VPN
Если нужен доступ к Claude без VPN и оплаты в валюте — проще всего через SpeShu.AI: своя точка доступа, оплата в рублях, без иностранной карты. У SpeShu.AI есть аналоговые модели: SpeShu Claude, SpeShu Gemini, SpeShu ChatGPT. Они не уступают официальным моделям и при этом работают без VPN, оплачиваются картой банков РФ и стоят дешевле.
Что делает промптинг для Claude особенным
Claude буквально выполняет то, что написано в промпте — это одновременно плюс и минус: расплывчатый запрос дает средний результат, а точный работает лучше, чем у конкурентов. Модель устроена так, что скорее скажет «не знаю», чем придумает ответ, — это важно для задач, где важна точность, и промпты вида «если не уверен — скажи явно» здесь реально работают.
Claude Opus 4.6 держит 76% точности извлечения информации даже на контексте в миллион токенов (бенчмарк MRCR v2) — загрузить весь договор, весь код проекта или всю переписку и задавать по ним вопросы вполне реальный сценарий. Модель также не начинает ответы с клише типа «В современном мире…» и не заканчивает штампованными выводами.
А если вы используете Клод с функцией Projects, инструкции из Project Knowledge применяются ко всем чатам в проекте автоматически — один раз описали стиль, роль, и не нужно повторять это в каждом запросе.
55 промптов для Claude по категориям
Для коротких задач достаточно обычного текста, а для сложных многочастных лучше работает XML-структура: роль, контекст, задача, формат, ограничения. Все промпты ниже — на английском языке, поскольку Claude лучше всего работает именно с такой формулировкой.
Работа с текстом и документами
1. Правовой анализ договора
Role: Experienced legal analyst
Task: Analyze the attached contract
Instructions: Find:
1. Obligations I as the client will not be able to fulfill
2. Penalty clauses with specific amounts or percentages
3. Clauses without clear deadlines or specific figures
4. What is missing compared to a standard contract of this type
Format: Table: Section | Risk | Recommended action.
Specifics only — no general conclusions.
2. Редактирование с сохранением авторского стиля
Edit my text: [insert]
Rules:
— preserve my style and tone, do not neutralize it
— remove repetition and filler words
— do not add anything new
— do not change the structure, only the language
Show: original paragraph -> edited version -> what you changed and why.
3. Резюме
Task: Read the document and write a summary for a busy executive
Constraints: — maximum one page
— start with the main conclusion, not the context
— facts with numbers only, no «general remarks»
— end with what requires a decision from the executive
4. Поиск противоречий в тексте
Read the attached document carefully.
Task: find places where:
1. The author contradicts themselves in different parts of the text
2. A claim is not backed by evidence
3. A conclusion does not follow from the data presented
For each — quote both places and explain the contradiction.
If there are no contradictions, say so honestly.
5. Письмо в определенном стиле (в рамках проектов)
I uploaded three samples of my writing to Project Knowledge.
Study: tone, sentence length, typical phrasing, what I deliberately avoid.
Write [type of text] on the topic of [X] in exactly the same manner.
Forbidden words: «unique», «undoubtedly», «it should be noted»,
«in conclusion», «thus».
6. Структурирование хаотичных заменток
Here are my raw notes: [insert]
Organize them:
1. Group by topic (invent a name for each group)
2. Within each group, highlight the main point in one sentence
3. Note what contradicts, what repeats, what is missing
Format: structured text with headings, not just a list.
7. Технический текст в понятный язык
Rewrite the technical text for a non-technical audience.
Audience: [description]. Their level: [basic/intermediate].
Instructions: replace jargon with everyday words, explain each complex concept with one everyday analogy, preserve the accuracy of meaning — do not oversimplify into distortion, if a term cannot be replaced, explain it in parentheses.
8. Полное саммари встречи
Here is the meeting transcript: [insert]
Clearly highlight:
-
Decisions: what was decided, by whom, on which issue
-
Action items: who, what, by which deadline
-
Open questions: what remains unanswered
-
Participants: who spoke, brief position of each
Format: a structured document that can be sent to all participants.
9. Проверка аргументации
Read my argument: [insert]
Evaluate: how well is the thesis proven by the data provided? What counterarguments did I fail to consider? What in my logic works well — not only criticism?
Be honest even if the argument is weak. Suggest how to strengthen the weakest point.
10. Email с конкретной целью
Write a business email. Recipient: [position/role]. Situation: [description]. Goal of the email: [what exactly we want to achieve].
Format: subject line (up to 60 characters), body of maximum 3 paragraphs, a specific next step at the end.
Avoid cliches, self-praise, passive-aggressive phrasing. Tone: direct and respectful.
11. Сравнительный анализ двух текстов
Compare two versions, [text A] and [text B], by criteria: clarity of argumentation, persuasiveness for [audience], accuracy and factual correctness, readability and structure.
Do not pick a winner — show where each is stronger. Say what you would take from each for an ideal version.
12. Создание ТЗ
Draft a project brief. Project: [description]. Contractor: [type of specialist]. Deadlines: [if known].
Sections: goal, what’s included, what’s not included, requirements for the result, acceptance criteria, deadlines, delivery format.
Кодинг и Claude Code
13. Написание кода с объяснением
Write [type of function/module]. You are a senior [language] developer focused on clean code. Task: [description]. Constraints: [what cannot be used, if any].
Instructions: first write working code, for every non-obvious choice explain why, add error handling, typing and docstrings, suggest a test for 3 key cases.
14. Код-ревью
You are a senior developer focused on [security / performance / readability]. Review this code: [insert].
Find security issues, performance bottlenecks, violations of accepted conventions ([specify standard]), and places where the logic is unclear without a comment.
For each issue: what exactly is wrong, why, and the corrected version. Do not touch what already works correctly.
15. Рефакторинг кода
Refactor this code without changing its external behavior: [insert code].
Goals: readability, reducing duplication, splitting into smaller functions, better naming.
Show: before, after, and a list of changes with a brief explanation of each.
16. Отладка ошибки
This code throws an error: [insert code]. Error: [insert error message]. Expected behavior: [what should happen].
Do not give the answer right away. First, ask a clarifying question if you need more context. Then explain the cause of the error, show the fix, and explain why it works.
17. Написание тестов
Write tests for this code: [insert]. You are a QA engineer experienced in TDD.
Cover: happy path (normal operation), edge cases (boundary values), error cases (invalid input, exceptions). Framework: [pytest/jest/other]. Each test with a comment on what exactly it checks.
18. Объяснение чужого кода
Explain this code to me as if I’m seeing it for the first time: [insert].
Tell me: what the code does overall in one sentence, what each key block does in order, what patterns or libraries are used, and whether there’s anything unusual or potentially problematic. If something is unclear, say exactly what.
19. Оптимизация SQL-запроса
Optimize this SQL query: [insert]. Database: [PostgreSQL/MySQL/other]. Table sizes: [approximately]. Current execution time: [if known].
Explain what exactly is slow, what you changed and why, and which indexes to add if needed.
20. Архитектурный ревью
Conduct an architecture review of the proposed solution. You are a systems architect with 10+ years of experience. Context: [description of the system/requirements]. Proposed architecture: [description].
Assess: scalability at 10x load, single points of failure, security, operational complexity. What’s good, what’s problematic, how to fix it.
21. Документация для API
Write documentation for this API endpoint: [insert code].
Include: description (what it does, why), request parameters (name, type, required?, description), example request in curl, possible responses with codes, and usage notes.
Format: Markdown, ready to paste into a README.
22. Код-ревью с метриками
Before answering, rate the code on 5 criteria from 1 to 10 and explain each score.
Conduct a code review: [insert]. Rate on a scale of 1-10: readability, logic correctness, error handling, testability, performance.
After the ratings, give concrete recommendations only for aspects scoring below 7.
Учеба и саморазвитие
23. Объяснение сложной концепции
Explain [concept/topic]. My level: [absolute beginner / familiar with basics / technical background in another field]. Why I need this: [application].
Start with one everyday analogy, explain the principle in your own words, show one concrete example of application, and end with three questions that will check whether I understood. If you’re not sure about something, say so explicitly.
24. Сократовский диалог
I’m studying [topic]. I want to go deeper through dialogue.
Rules: don’t explain right away, ask questions that make me think, one question at a time, point out flaws in my thinking but don’t correct immediately — let me get there myself, and if I’m stuck give a hint, not the answer.
Start by asking me one question on [X] to begin with.
25. Создание учебного плана
Create a personal learning plan. Skill/topic: [X]. Current level: [none/basic/intermediate]. Goal: [what I should be able to do at the end]. Time: [deadline] at [X hours per day].
Break it down by week: what to study, a practical assignment to reinforce it, how to check that it’s been mastered. Separately: resources — books, courses, practice.
26. Генерация тестов с объяснениями
Based on this material: [insert or attach], create 20 questions — 7 on factual knowledge, 8 on understanding concepts, 5 on applying them in a new situation.
For each: question, 4 answer options, correct answer, and why it’s correct in 2-3 sentences.
27. Разбор моих ошибок
Here is the task: [problem statement]. Here is my solution: [insert].
Don’t say right away whether it’s correct. First ask «how did you get this result?» After my explanation, point out exactly where the logic broke down. Give a hint, not the answer.
28. Глубокое погружение в тему
Before answering, build a mental map of the topic’s key concepts and their connections.
Explain [topic] to me fully, from basic principles to nuances: the essence in three sentences, key concepts with an explanation of each, how they connect to each other, common misconceptions, and what I need to know to go further.
29. Подготовка к собеседованию
Position: [role/level]. Company/industry: [context].
Ask me 10 questions typical for such an interview. After each of my answers, tell me what’s good, what’s missing or imprecise, and how to answer more strongly. Start with the first question and wait for my answer.
30. Флэш-карточки из материала
Read the attached material and create 25 flashcards. Question should be specific, not vague; answer no more than 1-2 sentences.
Cover facts, concepts, cause-and-effect links, and application. Format: question, then answer, separated clearly for each card.
31. Анализ пробелов в знаниях
I believe I understand [topic]. Here’s what I know: [state my understanding].
Find gaps and misconceptions: what is correct and complete, what is correct but incomplete, what is incorrect or distorted, and what is critically important and completely missing. Rank the gaps by what to fix first.
32. Помощь с эссе
Help write a strong essay. Topic: [X]. Type: [argumentative / analytical / descriptive]. Length: [words/pages]. Audience: [who’s reading].
Evaluate my thesis: [insert] — how debatable and provable is it? Suggest an argument structure, name three counterarguments that need to be addressed, and say what types of evidence are needed. Don’t write it for me — help me think.
Бизнес и профессиональная жизнь
33. Стратегический анализ ситуации
Before answering, examine the situation from three perspectives — short-term, long-term, and alternative.
Situation: [description of the business problem or decision]. Analyze honestly: what is the real problem, not the symptom? What options exist, at least three? What am I most likely overlooking? What question should I ask myself before acting?
34. Написание вакансии
We need a specialist: [role]. Responsibilities: [list]. Team and product: [context].
Write a job posting that attracts strong candidates instead of scaring them off. Avoid: «dynamic company» and similar cliches, a list of 20+ requirements, «communication skills» without explaining why, passive voice and vague phrasing.
35. Подготовка к переговорам
Prepare me for a negotiation. Situation: [description]. Our goal: [what we want]. Their likely position: [assumption]. Our constraints: [what’s off the table].
Give me three scenarios — best, realistic, difficult — top 5 objections with responses, red lines we absolutely cannot agree to, and the first sentence to open the conversation.
36. Анализ конкурентов
My niche: [description]. My competitors: [list with a brief description of each].
Analyze what is each one’s real difference, not their marketing positioning; each one’s weak points and where this is visible from; and what position none of them occupy. Specifics only.
37. Коммерческое предложение
Write a one-page business proposal. You are a B2B copywriter experienced in [industry]. Product/service: [description]. Client: [who, what they know, what pain point]. Our unique selling point: [why us].
Structure: problem, solution, evidence, terms, call to action. Tone: specific, no self-praise.
38. Обратная связь сотруднику
I need to give developmental feedback to [an employee/colleague] about [specific situation].
Help me formulate: a specific observation without judgment, its impact on the team or result, what I’d like to see instead, and a question that opens up dialogue. Tone: honest, but not accusatory.
39. Скрипт для сложного разговора
Help me prepare for a difficult conversation. With whom: [conversation partner]. Topic: [essence]. My concerns: [what I’m afraid of]. My goal: [what I want in the end].
Write how to open the conversation verbatim, how to respond to likely pushback, what to say if the conversation stalls, and how to close it constructively regardless of the outcome.
40. Анализ данных из файла
Attached table: [description of the data].
Find three most significant patterns with specific numbers, anomalies or outliers and what they might mean, and what these numbers predict for the next period. If there isn’t enough data for a conclusion, say so explicitly and specify what’s needed.
41. Стратегия контента
Develop a one-month content strategy. Platform: [YouTube/other]. Niche: [topic]. Audience: [who, what they want, what annoys them]. Goal: [sales/awareness/expertise].
Give me 3-4 content pillars with an explanation of why each, 20 specific topics with format, and how to address the objection «why should I follow this.»
42. Описание продукта
Product: [description of features]. Buyer: [who, what pain point].
Write a product listing description: a headline that’s a benefit, not a feature, up to 10 words; three bullet points with specific advantages; a call to action. Forbidden: «unique», «best», «innovative», «premium quality».
43. Разбор провала проекта
Before answering, examine three levels of causes — operational, process, and systemic.
Project [X] did not achieve its goal. Here’s what happened: [description]. Conduct a post-mortem: immediate causes, systemic causes, what was done right honestly, and three specific changes that will prevent a repeat. Don’t look for someone to blame.
44. Резюме
Write resume sections. You are a career consultant experienced in [industry]. Position I’m applying for: [X]. My experience: [list of achievements with numbers].
Give me a LinkedIn headline up to 120 characters focused on value not job title, an About section of 150 words, and current position as 3 bullet points with results, not duties.
45. Письмо с просьбой
I need to ask [what] from [whom]. Context: [situation, why it matters].
Help me write a letter that doesn’t sound demanding, makes it easy to say yes, and explains the value for the recipient, not just for me. Show one version and explain the choice of tone.
Личная жизнь и продуктивность
46. Принятие сложного решения
Before answering, draft a list of 5 questions that will help think more clearly.
I need to decide: [description of the dilemma]. Don’t give me advice — help me think: formulate the real question, what information am I missing, what would a smart person I trust ask, and what am I most likely rationalizing rather than analyzing.
47. Разбор конфликта
Situation: [describe the conflict without embellishment].
Help me formulate my position without blame — «I feel» instead of «you always» — find what I’m probably doing differently honestly, and write a message that opens dialogue rather than shutting it down.
48. Планирование недели
My goals for this week: [list]. Fixed calendar events: [list with times]. Free time: [how many hours a day]. Energy level: [right now and generally].
Build a day-by-day plan, prioritize what to do first and why, and leave a 20% buffer for the unexpected.
49. Помощь с выгоранием
I’m working on [project/goal] and feeling burned out. Here’s what’s happening: [describe].
Be a mentor with empathy and a practical approach: tell me objectively what’s actually going well, one reframe that changes the perspective, and one next small step. Don’t give motivational speeches.
50. Финансовое планирование
My income: [X per month]. Fixed expenses: [list with amounts]. Goal: [save X / build an emergency fund / pay off debt].
Analyze how much realistically is left for the goal each month, where I’m probably overspending, whether the goal is realistic, and what should change first.
Продвинутые техники Claude — шаблоны
Это не готовые сценарии, а шаблоны структуры, которые адаптируются под любую задачу.
51. Универсальный шаблон для сложных задач
Who Claude is in this conversation: [role]. What’s needed to complete the task: [context]. Specific action: [one verb]. Numbered steps or requirements: [instructions]. Exactly how to format the result: [format]. What’s forbidden: [constraints].
52. Шаблон с рассуждением перед ответом
Before answering: [instruction on what to think through — e.g., consider three perspectives, list your assumptions, check the logic]. Then: [main task].
53. Шаблон для продолжения работы
We’re working on [project/task]. Previously agreed: [key decisions from prior sessions]. Now I need: [specific next step]. Don’t repeat what’s already decided — continue from where we left off.
54. Шаблон «честный анализ»
I need an honest analysis of [X], including uncomfortable conclusions. Separate what’s confirmed by data, what’s likely, and what’s disputed. If you don’t know something, say so explicitly. Don’t smooth over contradictions — I prefer the precision of an unpleasant truth.
55. Шаблон для Projects
Paste into Project Instructions on claude.ai: you are my working assistant for [topic/project]. Always answer specifically without introductory phrases, ask one clarifying question if something is unclear, use [markdown / bullet points / plain text] as the default format, and don’t use [list of forbidden words/phrases]. Project context: [description]. Key agreements: [what’s already decided].
Советы по промптингу именно для Claude
Если промпт длиннее трех предложений, стоит использовать XML-структуру: Claude обучен на структурированных промптах и выдает заметно более организованный результат. На одну задачу лучше ставить один глагол действия — «напиши», «проанализируй», «отредактируй», «сгенерируй» по отдельности, поскольку при нескольких задачах без XML-структуры модель может выбрать одну из них или усреднить результат.
Хорошо работают и ограничения: «не используй слово X», «ответ не длиннее Y слов», «только факты, без оценок» — Claude выполняет это точно, так что не стоит бояться быть конкретным в запретах. Добавление тега <thinking> с инструкцией, что обдумать перед ответом, заметно повышает точность на сложных задачах. И всегда полезно ставить контекст перед задачей — сначала кто-что-зачем, потом что делать: Claude строит фреймворк понимания из контекста, прежде чем приступить к самой задаче.
Частые вопросы
Почему промпты для Claude пишут с XML-тегами? Модель изначально обучена на структурированных промптах с такими тегами, что устраняет двусмысленность между контекстом и инструкцией и дает более организованный результат на сложных задачах.
Нужны ли XML-теги для простых вопросов? Нет, для простых задач современные модели Claude 4.x одинаково хорошо реагируют на обычные явные инструкции без структуры.
Что такое тег <thinking> в промпте? Это способ заставить Claude явно обдумать задачу перед тем, как дать финальный ответ, что заметно повышает точность на сложных рассуждениях.
Можно ли получить доступ к Claude без VPN из России? Да, через SpeShu.AI — с оплатой в рублях и без иностранной карты.
Заключение
Промпты для Claude работают иначе, чем для большинства других нейросетей, — модель точно следует структуре и явным ограничениям, поэтому вложенные усилия в формулировку окупаются заметно лучше. Все шаблоны из этой подборки можно сразу адаптировать под свою задачу, просто заменив текст в квадратных скобках.
Промокод HABRSPESHUAI дает дополнительный бонус читателям блога. Введите промокод при пополнении баланса и получите +15% на счет агрегатора.
ссылка на оригинал статьи https://habr.com/ru/articles/1067330/