# Anthropic releases method to 10× Claude Code / Opus 4.5
Table of Contents
These notes are based on the YouTube video by Greg Isenberg
10 Rules for Prompting Claude
To get the most out of Claude Code and Opus 4.5, it’s essential to understand how to craft effective prompts. The following rules can help you achieve better results:
- Tone of Collaboration: Use a clear, respectful, and directive tone in your prompts to yield better and more direct results.
- Principle of Explicitness: State your request as a clear, action-oriented command with all the necessary details.
- Defining the Boundaries: A well-defined box produces a more creative result than an empty field. Add constraints to your prompts to guide the AI.
- Draft, Plan, Then Act: Use the AI to generate an outline or rough version first, then refine the plan and execute.
- Demand Structured Output: Specify the format of the output you want, such as a markdown table, to get more structured and useful results.
- Explaining the Why: Provide context and explain the reason behind your request to help the AI understand your true intent.
- The Art of Brevity and Verbosity: Explicitly command the AI to be more or less verbose to match your needs.
- Providing a Scaffold: Give the AI a template or example to guide its structure and style.
- Speaking the Language: Use advanced prompting terms to trigger more sophisticated modes of operation.
- Divide and Conquer Strategy: Break down complex tasks into logical subtasks and prompt for each part separately, then prompt for the synthesis.
Detailed Explanations
Tone of Collaboration
Using a clear, respectful, and directive tone in your prompts can significantly impact the quality of the results. Instead of using a vague or overly casual tone, try to craft prompts that are direct and respectful. For example:
Please review the following text for grammatical errors and suggest corrections. My goal is to make it sound more professional and confident.As discussed in Claude Code best practices, this tone is essential for achieving better results.
Principle of Explicitness
To get the most out of Claude, it’s essential to be explicit in your prompts. This means using action verbs, specifying the quantity and target audience, and providing all the necessary details. For example:
Generate 10 blog post titles about the impact of remote work on urban planning. The title should be engaging for an audience of city officials and real estate developers.Building on the concept of Claude Code Agents, let’s explore how explicitness can help you achieve your goals.
Defining the Boundaries
Adding constraints to your prompts can help guide the AI and produce more creative and specific results. This can include constraints on length, style, character, setting, and specific words. For example:
Write a short story, no more than 500 words, in the style of Raymond Chandler. The story must feature a robot detective investigating a data theft on Mars. Do not use the word "cyber".🔗 See Also: 5 Claude Code MCP Servers You Need To Be Using for more information on how to use Claude Code effectively.
Draft, Plan, Then Act
Instead of trying to get a perfect final product in one go, use the AI to generate an outline or rough version first, then refine the plan and execute. This can help you course correct early and produce a higher quality result.
💡 Related: How Claude Code Hooks Save Me HOURS Daily for tips on how to streamline your workflow with Claude Code.
Summary
By following these 10 rules, you can significantly improve the quality of the results you get from Claude Code and Opus 4.5. Remember to use a tone of collaboration, be explicit in your prompts, define the boundaries, draft and plan before acting, demand structured output, explain the why, control the level of verbosity, provide a scaffold, speak the language, and use the divide and conquer strategy. With practice and patience, you can master the art of prompting Claude and achieve amazing results.
Note: The original content has been corrected to reflect that the “10 rules” are the author’s best practices for Claude Code and Opus 4.5, rather than an officially branded Anthropic “10× method”. Additionally, the tone of collaboration has been rephrased to emphasize clarity, respect, and directness, rather than friendliness. The principle of explicitness and defining boundaries have been clarified as widely accepted prompt-engineering heuristics.
