---
type: WebPage
title: The new rules of context engineering for Claude 5 genera
description: ""
resource: https://claude.com/blog/the-new-rules-of-context-engineering-for-claude-5-generation-models
tags: []
timestamp: 2026-07-26T01:36:37.318811Z
---

* Meet Claude

  Products

  + [Claude](/product/overview)
  + [Claude Code](/product/claude-code)
  + [Claude Cowork](/product/cowork)
  + [@Claude](/product/tag)

  Features

  + [Claude for Chrome](/claude-for-chrome)
  + [Claude for Microsoft 365](/claude-for-microsoft-365)
  + [Skills](/skills)

  Claude apps built for

  + [Design](/product/design)
  + [Science](/product/claude-science)
  + [Security](/product/claude-security)

  Models

  + [Mythos](https://www.anthropic.com/claude/mythos)
  + [Fable](https://www.anthropic.com/claude/fable)
  + [Opus](https://www.anthropic.com/claude/opus)
  + [Sonnet](https://www.anthropic.com/claude/sonnet)
  + [Haiku](https://www.anthropic.com/claude/haiku)
* Platform

  Build on Claude

  + [Overview](/platform/api)
  + [Pricing](http://claude.com/pricing#api)
  + [Developer docs](https://platform.claude.com/docs)
  + [Console login](https://platform.claude.com/)

  Works with Claude

  + [Ecosystem](/ecosystem)
  + [Marketplace](/platform/marketplace)
  + [Connectors](/connectors)
  + [Plugins](/plugins)
* Solutions

  Use cases

  + [AI agents](/solutions/agents)
  + [Coding](/solutions/coding)

  Company size

  + [Enterprise](/solutions/enterprise)
  + [Startups](/programs/startups)

  Departments

  + [Cybersecurity](/solutions/cybersecurity)
  + [Legal](/solutions/legal)

  Industries

  + [Customer support](/solutions/customer-support)
  + [Financial services](/solutions/financial-services)
  + [Government](/solutions/government)
  + [Healthcare](/solutions/healthcare)
  + [Higher education](/solutions/education)
  + [K-12 teachers](/solutions/teachers)
  + [Life sciences](/solutions/life-sciences)
  + [Nonprofits](/solutions/nonprofits)
* Pricing

  + [Overview](/pricing)
  + [API](/pricing#api)
* Resources

  Insights

  + [Blog](/blog)
  + [Customer stories](/customers)
  + [Anthropic news](https://www.anthropic.com/news)

  Learn

  + [Anthropic Academy](https://www.anthropic.com/learn)
  + [Courses](/resources/courses)
  + [Tutorials](/resources/tutorials)
  + [Use cases](/resources/use-cases)

  Connect

  + [Events](https://www.anthropic.com/events)
  + [Community](/community)
* [Login](https://claude.ai/login)

* Contact sales

  [Contact sales](/contact-sales)Contact sales
* Try Claude

  [Try Claude](https://claude.ai/)Try Claude
* Contact sales

  [Contact sales](/contact-sales)Contact sales
* Try Claude

  [Try Claude](https://claude.ai/)Try Claude

* Contact sales

  [Contact sales](/contact-sales)Contact sales
* Try Claude

  [Try Claude](https://claude.ai/)Try Claude
* Contact sales

  [Contact sales](/contact-sales)Contact sales
* Try Claude

  [Try Claude](https://claude.ai/)Try Claude

* Meet Claude

  Products

  + [Claude](/product/overview)
  + [Claude Code](/product/claude-code)
  + [Claude Cowork](/product/cowork)
  + [@Claude](/product/tag)

  Features

  + [Claude for Chrome](/claude-for-chrome)
  + [Claude for Microsoft 365](/claude-for-microsoft-365)
  + [Skills](/skills)

  Claude apps built for

  + [Design](/product/design)
  + [Science](/product/claude-science)
  + [Security](/product/claude-security)

  Models

  + [Mythos](https://www.anthropic.com/claude/mythos)
  + [Fable](https://www.anthropic.com/claude/fable)
  + [Opus](https://www.anthropic.com/claude/opus)
  + [Sonnet](https://www.anthropic.com/claude/sonnet)
  + [Haiku](https://www.anthropic.com/claude/haiku)
* Platform

  Build on Claude

  + [Overview](/platform/api)
  + [Pricing](http://claude.com/pricing#api)
  + [Developer docs](https://platform.claude.com/docs)
  + [Console login](https://platform.claude.com/)

  Works with Claude

  + [Ecosystem](/ecosystem)
  + [Marketplace](/platform/marketplace)
  + [Connectors](/connectors)
  + [Plugins](/plugins)
* Solutions

  Use cases

  + [AI agents](/solutions/agents)
  + [Coding](/solutions/coding)

  Company size

  + [Enterprise](/solutions/enterprise)
  + [Startups](/programs/startups)

  Departments

  + [Cybersecurity](/solutions/cybersecurity)
  + [Legal](/solutions/legal)

  Industries

  + [Customer support](/solutions/customer-support)
  + [Financial services](/solutions/financial-services)
  + [Government](/solutions/government)
  + [Healthcare](/solutions/healthcare)
  + [Higher education](/solutions/education)
  + [K-12 teachers](/solutions/teachers)
  + [Life sciences](/solutions/life-sciences)
  + [Nonprofits](/solutions/nonprofits)
* Pricing

  + [Overview](/pricing)
  + [API](/pricing#api)
* Resources

  Insights

  + [Blog](/blog)
  + [Customer stories](/customers)
  + [Anthropic news](https://www.anthropic.com/news)

  Learn

  + [Anthropic Academy](https://www.anthropic.com/learn)
  + [Courses](/resources/courses)
  + [Tutorials](/resources/tutorials)
  + [Use cases](/resources/use-cases)

  Connect

  + [Events](https://www.anthropic.com/events)
  + [Community](/community)
* [Login](https://claude.ai/login)

* Contact sales

  [Contact sales](/contact-sales)Contact sales
* Try Claude

  [Try Claude](https://claude.ai/)Try Claude
* Contact sales

  [Contact sales](/contact-sales)Contact sales
* Try Claude

  [Try Claude](https://claude.ai/)Try Claude

1. Blog

   [Blog](/blog)

   /
2. The new rules of context engineering for Claude 5 generation models

Explore here

* Ask questions about this page
* Copy as markdown

![](https://cdn.prod.website-files.com/68a44d4040f98a4adf2207b6/6903d222061abf091318fb82_423062049d4676b41d52b16068cbb5e21603190e-1000x1000.svg)

# The new rules of context engineering for Claude 5 generation models

We removed over 80% of Claude Code's system prompt for more advanced models. How to apply the lessons we learned to your own context engineering in Claude Code and with your own agents.

* Category

  [Claude Code](https://claude.com/blog/category/claude-code)

  [Agents](https://claude.com/blog/category/agents)
* Product

  Claude Code

  Claude Enterprise

  Claude Platform
* Date

  July 24, 2026
* Reading time

  5

  min
* Share

  Copy link

  https://claude.com/blog/the-new-rules-of-context-engineering-for-claude-5-generation-models

I’ve written previously about how to best [prompt the newest generation of Claude 5 models](https://claude.com/blog/a-field-guide-to-claude-fable-finding-your-unknowns) and work with them iteratively to discover what you want to build.

But when you send a message to Claude, the prompt is only a small part of the context it gets. Much of your context is assembled from your system prompt, Skills, CLAUDE.md files, memory, and other sources. We call this [context engineering](https://www.anthropic.com/engineering/effective-context-engineering-for-ai-agents), and it makes a big impact on the results you generate when using Claude Code or in building your own agents.

Unlike a prompt, context is used generally across many requests, so it cannot be as specific.  How do you build these general prompts and guidance for Claude, especially when you don’t know what a user’s prompt might be?

This can be surprisingly difficult as Claude’s own capabilities evolve. Most recently, we noticed a large jump in the way we prompt the newest generation of Claude models. We removed over 80% of Claude Code’s system prompt for models like Claude Opus 5 and Claude Fable 5 with no measurable loss on our coding evaluations.

Here’s what we’ve learned about prompting this new class of models, and how you can utilize it to update your context engineering. We’ve put these best practices in `claude doctor;` use the command /doctor in Claude Code to rightsize your skills, and CLAUDE.md files.

## Unhobbling Claude

Overall, we found that we were overconstraining Claude Code, both through our system prompt and in our CLAUDE.md files and skills.

For example, when we read transcripts of our own internal usage of Claude Code, we see several conflicting messages in a single request like “leave documentation as appropriate,” or “DO NOT add comments” as our system prompt, skills, and user requests clash with each other.

![](https://cdn.prod.website-files.com/68a44d4040f98a4adf2207b6/6a63620bedb2b7813b1071e2_afa90c36.png)

Generally, Claude can interpret the user’s intent to get to the right answer, but Claude must think more carefully about these overlapping and conflicting messages before deciding what to do.

And while these constraints were once needed to avoid worst case scenarios, we have since found we can delete many of them and let the model use surrounding context and judgement instead.

Additionally, Claude Code now has many more tools. Claude used to rely on CLAUDE.md as a source of memory, information, and guidance. Now we have memory, artifacts, and skills, which Claude can use to create new ways of loading and sharing context across sessions.

No items found.

PrevPrev

0/5

NextNext

Get Claude Code

* [Desktop](/download)
* [VS Code](https://marketplace.visualstudio.com/items?itemName=anthropic.claude-code)
* [JetBrains](https://plugins.jetbrains.com/plugin/27310-claude-code-beta-)
* [On the web](https://claude.ai/code)
* [Slack](https://slack.com/oauth/v2/authorize?client_id=1601185624273.8899143856786&scope=app_mentions:read,assistant:write,channels:history,channels:read,chat:write,files:read,files:write,groups:history,groups:read,im:history,im:read,im:write,mpim:history,reactions:write,users:read,users:read.email,commands,search:read.public&user_scope=bookmarks:read,channels:history,channels:read,chat:write,emoji:read,files:read,groups:history,groups:read,groups:write,im:history,im:read,im:write,links:read,mpim:history,mpim:read,mpim:write,mpim:write.topic,pins:read,reactions:read,reactions:write,remote_files:read,team:read,users:read,users:read.email,search:read.public,search:read.private,search:read.im,search:read.mpim,search:read.files,search:read.users,canvases:read,canvases:write)

curl -fsSL https://claude.ai/install.sh | bash

Copy command to clipboard

irm https://claude.ai/install.ps1 | iex

Copy command to clipboard

Or read the [documentation](https://code.claude.com/docs/en/overview)

Try Claude Code

[Try Claude Code](https://claude.ai/code)Try Claude Code

Developer docs

[Developer docs](https://code.claude.com/docs/en/overview)Developer docs

eBook

##

![](https://cdn.prod.website-files.com/6889473510b50328dbb70ae6/6889473610b50328dbb70b58_placeholder.svg)

![](https://cdn.prod.website-files.com/6889473510b50328dbb70ae6/6889473610b50328dbb70b58_placeholder.svg)![](https://cdn.prod.website-files.com/6889473510b50328dbb70ae6/6889473610b50328dbb70b58_placeholder.svg)

## Then and now

There were a number of previous context engineering best practices that had become myths. Including:.

![](https://cdn.prod.website-files.com/68a44d4040f98a4adf2207b6/6a63620bedb2b7813b107213_3979f6a1.png)

### Then: Give Claude rules

### Now: Let Claude use judgement

When we first rolled out Claude Code, we needed to be sure that Claude avoided worst case scenarios, such as deleting files. This meant we would give particularly strong guidance that might not always be true, For example, in the system prompt we used to say:

*In code: default to writing no comments. Never write multi-paragraph docstrings or multi-line comment blocks — one short line max. Don't create planning, decision, or analysis documents unless the user asks for them — work from conversation context, not intermediate files.*

But for a certain subset of prompts, this guidance would be wrong. In the case of documentation, the user may have their own preferences, or specific parts of very complex code might need multi-line comment blocks.

Still, without these guardrails for older models, the comments Claude wrote would be incorrect in many cases and we had to accept this tradeoff. But newer models have better judgement and can handle these decisions well without explicit rules.

In the new system prompt we say: *Write code that reads like the surrounding code: match its comment density, naming, and idiom.*

### Then: Give Claude examples

### Now: Design interfaces

The number one rule for tool usage was to give Claude examples on how to use them. With our newest models, we’ve found that giving examples actually constrains them to a certain exploration space.

![](https://cdn.prod.website-files.com/68a44d4040f98a4adf2207b6/6a63620bedb2b7813b107216_c4fdec0d.png)

Instead of using examples, think more about the design of your tools, scripts and files- what parameters does Claude have and how can they be more expressive?

For example, in the Todo tool example, just listing status as an enumeration between pending, in\_progress, and completed, hints to Claude about how to use it. The instruction on keeping one item in\_progress helps define our requested behavior.

### Then: Put it all upfront

### Now: Use progressive disclosure

Because Claude Code was focused on coding, our system prompt included detailed information on how to do code review and verification. These were not always needed, but when they were, it was crucial information.

Since then, Claude Code has gotten very competent at using progressive disclosure- loading the right context at the right times. For example, we moved verification and code review into their own skills that Claude Code could selectively call.

But progressive disclosure is not just for skills, we also use it for tools. Some of our tools are ‘deferred loading,’ which means the agent must search for their full definitions using ToolSearch before using them. This allows us to have more tools (such as our Task tools) that don’t take up context until they’re needed.

The same can be applied to your own CLAUDE.md and Skill.md files. A common myth is that you want to make these a central repository for every known practice that you *might* run into, because Claude would not find it otherwise. Instead, [consider having a tree of files that can be loaded at the right time](https://claude.com/blog/a-harness-for-every-task-dynamic-workflows-in-claude-code).

### Then: Repeat yourself

### Now: Simple tool descriptions

Earlier Claude models could sometimes need repeated instructions or be more likely to listen to instructions at the end of their context window than at the start. This meant our system prompt would sometimes have references to tools in the main system prompt as well as instructions in the tool description.

We found we could delete these repeat examples and put instructions on how to use tools in the tool descriptions rather than the system prompt.

### Then: Memory in CLAUDE.md files

### Now: Auto-memory

We used to encourage users to save things to Claude’s memory, by using the # hotkey to write to their [CLAUDE.md](http://claude.md) automatically. Instead, Claude now automatically saves memories that are relevant to the work and to you.

### Then: Simple specs

### Now: Rich references

In plan mode, Claude Code has heavily relied on markdown files with plans. Storing these files as plans helped Claude refer to them when needed. Another similar best practice was to store specs in the codebase for Claude to refer to while working across longer projects.

But we’ve found that Claude can handle increasingly more complicated references. Instead of simple markdown files, Claude can reference HTML artifacts created by our new artifacts feature.

You may also give Claude references in the form of code. A spec may also be a detailed test suite, or a function in a different codebase that Claude might port.

Rubrics are another form of references. Rubrics allow Claude to try and verify your taste in a particular field (e.g. what does a good API design look like) by using [dynamic workflows](https://claude.com/blog/a-harness-for-every-task-dynamic-workflows-in-claude-code) and spinning up verifier agents with those rubrics.

## Applying this to your context

Pulling this all together, what does this look like when you assemble your context?

![](https://cdn.prod.website-files.com/68a44d4040f98a4adf2207b6/6a63620bedb2b7813b10721a_836a850d.png)

### System Prompt

A system prompt is heavily tied to the product context. It tells Claude what product it’s operating in and what it’s doing. For Claude Code, you will likely never modify this, but if you are building your own agent harness, this is where you should spend a lot of time.

### CLAUDE.md

Keep your CLAUDE.md lightweight and briefly describe what your repo is for, but spend most of the tokens on gotchas inside of the codebase. For example, you may organize your code to keep types in one monolithic file and nowhere else. Avoid stating ‘the obvious’ things Claude should know by looking at your file system or your repo.

Use progressive disclosure heavily, for example if you have several unique instructions on how to verify your work, create a verification skill and reference it from your CLAUDE.md.

### Skills

Think of skills as lightweight guides to let Claude find information when needed. Avoid making them overconstrained, except in highly important areas.

For long skills, try and use progressive disclosure as much as possible- divide it into many files and split them out.

It’s best when skills encode particular opinions, knowledge, or best practices that are particular to you, your team, or product.

### References

You can @ mention files to include them as references. References allow Claude to refer to in-depth information about the current plan.

This might be in specs files, mockups, or even entire codebases. Generally you should prefer files that are in code as it provides clear, high-fidelity instructions to Claude in a language it knows very well. For example, a HTML mockup of a design will generally produce better results than a description of the design or a screenshot.

## Try simplifying

Across your system prompt, skills, and CLAUDE.md files, you may need to simplify just like we did. We rolled out a new command called `claude doctor,` which will help you do this automatically as well. For more details on prompting more advanced models specifically, check out our [Fable field guide](https://claude.com/blog/a-field-guide-to-claude-fable-finding-your-unknowns).

*This article was written by Thariq Shihipar, member of technical staff, Anthropic.*

FAQ

No items found.

## Related posts

Explore more product news and best practices for teams building with Claude.

![](https://cdn.prod.website-files.com/68a44d4040f98a4adf2207b6/6903d225e31f7aa22c1f28cb_46e4aa7ea208ed440d5bd9e9e3a0ee66bc336ff1-1000x1000.svg)

Jul 24, 2026

### Claude models explained: choosing the best model for your use case

Enterprise AI

Claude models explained: choosing the best model for your use caseClaude models explained: choosing the best model for your use case

[Claude models explained: choosing the best model for your use case](/blog/claude-models-explained-choosing-the-best-model-for-your-use-case)Claude models explained: choosing the best model for your use case

![](https://cdn.prod.website-files.com/68a44d4040f98a4adf2207b6/6903d224d39f9b8e905d1823_b68cbb43d7c8f56f0b14cc867e8d4d74445f78b0-1000x1000.svg)

Jul 22, 2026

### Building verification loops in Claude Code with skills

Claude Code

Building verification loops in Claude Code with skillsBuilding verification loops in Claude Code with skills

[Building verification loops in Claude Code with skills](/blog/building-verification-loops-in-claude-code-with-skills)Building verification loops in Claude Code with skills

![](https://cdn.prod.website-files.com/68a44d4040f98a4adf2207b6/6903d22824d4124c2e33ba8e_b1ce510c468b2920d4f8f61c17a50906801f939a-1000x1000.svg)

Jul 21, 2026

### How Anthropic secures its AI-native software development lifecycle

Claude Code

How Anthropic secures its AI-native software development lifecycleHow Anthropic secures its AI-native software development lifecycle

[How Anthropic secures its AI-native software development lifecycle](/blog/how-anthropic-secures-its-ai-native-software-development-lifecycle)How Anthropic secures its AI-native software development lifecycle

![](https://cdn.prod.website-files.com/68a44d4040f98a4adf2207b6/6903d2260bfc90348429f9c3_cd9cf56a7f049285b7c1c8786c0a600cf3d7f317-1000x1000.svg)

Jul 16, 2026

### How Anthropic runs large-scale code migrations with Claude Code

Claude Code

How Anthropic runs large-scale code migrations with Claude CodeHow Anthropic runs large-scale code migrations with Claude Code

[How Anthropic runs large-scale code migrations with Claude Code](/blog/ai-code-migration)How Anthropic runs large-scale code migrations with Claude Code

## Transform how your organization operates with Claude

See pricing

[See pricing](https://claude.com/pricing#api)See pricing

Contact sales

[Contact sales](https://claude.com/contact-sales)Contact sales

Get the developer newsletter

Product updates, how-tos, community spotlights, and more. Delivered monthly to your inbox.

SubscribeSubscribe

Please provide your email address if you'd like to receive our monthly developer newsletter. You can unsubscribe at any time.

Thank you! You’re subscribed.

Sorry, there was a problem with your submission, please try again later.

[Homepage](https://claude.com)Homepage

NextNext

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Write

Button TextButton Text

Learn

Button TextButton Text

Code

Button TextButton Text

Write

* Help me develop a unique voice for an audience

  Hi Claude! Could you help me develop a unique voice for an audience? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

  Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help!
* Improve my writing style

  Hi Claude! Could you improve my writing style? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

  Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help!
* Brainstorm creative ideas

  Hi Claude! Could you brainstorm creative ideas? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

  Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help!

Learn

* Explain a complex topic simply

  Hi Claude! Could you explain a complex topic simply? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

  Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help!
* Help me make sense of these ideas

  Hi Claude! Could you help me make sense of these ideas? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

  Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help!
* Prepare for an exam or interview

  Hi Claude! Could you prepare for an exam or interview? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

  Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help!

Code

* Explain a programming concept

  Hi Claude! Could you explain a programming concept? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

  Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help!
* Look over my code and give me tips

  Hi Claude! Could you look over my code and give me tips? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

  Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help!
* Vibe code with me

  Hi Claude! Could you vibe code with me? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

  Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help!

More

* Write case studies

  This is another test
* Write grant proposals

  Hi Claude! Could you write grant proposals? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to — like Google Drive, web search, etc. — if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

  Please execute the task as soon as you can - an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help!
* Write video scripts

  this is a test

[Anthropic](https://www.anthropic.com/)Anthropic

© [year] Anthropic PBC

Products

* Claude

  [Claude](/product/overview)Claude
* Claude Code

  [Claude Code](/product/claude-code)Claude Code
* Claude Code for Enterprise

  [Claude Code for Enterprise](/product/claude-code/enterprise)Claude Code for Enterprise
* Claude Cowork

  [Claude Cowork](/product/cowork)Claude Cowork
* @Claude

  [@Claude](/product/tag)@Claude
* Claude Design

  [Claude Design](/product/design)Claude Design
* Claude Science

  [Claude Science](/product/claude-science)Claude Science
* Claude Security

  [Claude Security](/product/claude-security)Claude Security
* Download app

  [Download app](/download)Download app
* Pricing

  [Pricing](/pricing)Pricing
* Log in

  [Log in](https://claude.ai/login)Log in

Features

* Claude for Chrome

  [Claude for Chrome](/claude-for-chrome)Claude for Chrome
* Claude for Microsoft 365

  [Claude for Microsoft 365](/claude-for-microsoft-365)Claude for Microsoft 365
* Skills

  [Skills](/skills)Skills

Models

* Mythos

  [Mythos](https://www.anthropic.com/claude/mythos)Mythos
* Fable

  [Fable](https://www.anthropic.com/claude/fable)Fable
* Opus

  [Opus](https://www.anthropic.com/claude/opus)Opus
* Sonnet

  [Sonnet](https://www.anthropic.com/claude/sonnet)Sonnet
* Haiku

  [Haiku](https://www.anthropic.com/claude/haiku)Haiku

Solutions

* AI agents

  [AI agents](/solutions/agents)AI agents
* Code modernization

  [Code modernization](/solutions/code-modernization)Code modernization
* Coding

  [Coding](/solutions/coding)Coding
* Customer support

  [Customer support](/solutions/customer-support)Customer support
* Cybersecurity

  [Cybersecurity](/solutions/cybersecurity)Cybersecurity
* Enterprise

  [Enterprise](/solutions/enterprise)Enterprise
* Financial services

  [Financial services](/solutions/financial-services)Financial services
* Government

  [Government](/solutions/government)Government
* Healthcare

  [Healthcare](/solutions/healthcare)Healthcare
* Higher education

  [Higher education](/solutions/education)Higher education
* K-12 teachers

  [K-12 teachers](/solutions/teachers)K-12 teachers
* Legal

  [Legal](/solutions/legal)Legal
* Life sciences

  [Life sciences](/solutions/life-sciences)Life sciences
* Nonprofits

  [Nonprofits](/solutions/nonprofits)Nonprofits
* Small business

  [Small business](/solutions/small-business)Small business

Claude Platform

* Overview

  [Overview](/platform/api)Overview
* Developer docs

  [Developer docs](https://platform.claude.com/docs)Developer docs
* Pricing

  [Pricing](https://claude.com/pricing#api)Pricing
* Ecosystem

  [Ecosystem](/ecosystem)Ecosystem
* Marketplace

  [Marketplace](/platform/marketplace)Marketplace
* Claude on AWS

  [Claude on AWS](/partners/claude-on-aws)Claude on AWS
* Google Cloud

  [Google Cloud](/partners/google-cloud)Google Cloud
* Microsoft Foundry

  [Microsoft Foundry](/partners/microsoft-foundry)Microsoft Foundry
* Regional compliance

  [Regional compliance](/regional-compliance)Regional compliance
* Console login

  [Console login](https://platform.claude.com/)Console login

Resources

* Blog

  [Blog](/blog)Blog
* Claude partner network

  [Claude partner network](/partners)Claude partner network
* Community

  [Community](/community)Community
* Connectors

  [Connectors](/connectors)Connectors
* Courses

  [Courses](https://www.anthropic.com/learn)Courses
* Customer stories

  [Customer stories](/customers)Customer stories
* Engineering at Anthropic

  [Engineering at Anthropic](https://www.anthropic.com/engineering)Engineering at Anthropic
* Events

  [Events](https://www.anthropic.com/events)Events
* Plugins

  [Plugins](/plugins)Plugins
* Powered by Claude

  [Powered by Claude](/partners/powered-by-claude)Powered by Claude
* Service partners

  [Service partners](/partners/services)Service partners
* Tutorials

  [Tutorials](/resources/tutorials)Tutorials
* Use cases

  [Use cases](/resources/use-cases)Use cases

Company

* Anthropic

  [Anthropic](https://www.anthropic.com/)Anthropic
* Careers

  [Careers](https://www.anthropic.com/careers)Careers
* Policy

  [Policy](https://www.anthropic.com/policy)Policy
* Economic Futures

  [Economic Futures](https://www.anthropic.com/economic-futures)Economic Futures
* Research

  [Research](https://www.anthropic.com/research)Research
* News

  [News](https://www.anthropic.com/news)News
* Policy on the AI Exponential

  [Policy on the AI Exponential](https://www.anthropic.com/policy-on-the-ai-exponential)Policy on the AI Exponential
* Responsible Scaling Policy

  [Responsible Scaling Policy](https://www.anthropic.com/news/announcing-our-updated-responsible-scaling-policy)Responsible Scaling Policy
* Security and compliance

  [Security and compliance](https://trust.anthropic.com/)Security and compliance
* Transparency

  [Transparency](https://anthropic.com/transparency)Transparency

Programs

* Startups

  [Startups](https://claude.com/programs/startups)Startups
* Research Labs

  [Research Labs](https://claude.com/programs/claude-team-plan-for-research-labs)Research Labs

Help and security

* Availability

  [Availability](https://www.anthropic.com/supported-countries)Availability
* Status

  [Status](https://status.anthropic.com/)Status
* Support center

  [Support center](https://support.claude.com/en/)Support center

Terms and policies

* Privacy choices

  ### Cookie settings

  We use cookies to deliver and improve our services, analyze site usage, and if you agree, to customize or personalize your experience and market our services to you. You can read our Cookie Policy [here](https://www.anthropic.com/legal/cookies).

  Customize cookie settings

  Reject all cookies

  Accept all cookies

  ###### Necessary

  Enables security and basic functionality.

  Required

  [x]

  ###### Analytics

  Enables tracking of site performance.

  Off

  [ ]

  ###### Marketing

  Enables ads personalization and tracking.

  Off

  [ ]

  Save preferences
* Privacy policy

  [Privacy policy](https://www.anthropic.com/legal/privacy)Privacy policy
* Responsible disclosure policy

  [Responsible disclosure policy](https://www.anthropic.com/responsible-disclosure-policy)Responsible disclosure policy
* Terms of service: Commercial

  [Terms of service: Commercial](https://www.anthropic.com/legal/commercial-terms)Terms of service: Commercial
* Terms of service: Consumer

  [Terms of service: Consumer](https://www.anthropic.com/legal/consumer-terms)Terms of service: Consumer
* Terms of Service: US K-12

  [Terms of Service: US K-12](https://anthropic.com/legal/k12-terms)Terms of Service: US K-12
* Data Processing Agreement: US K-12

  [Data Processing Agreement: US K-12](https://anthropic.com/legal/k12-dpa)Data Processing Agreement: US K-12
* Usage policy

  [Usage policy](https://www.anthropic.com/legal/aup)Usage policy

[x.com](https://x.com/claudeai)x.com

[LinkedIn](https://www.linkedin.com/showcase/claude/)LinkedIn

[YouTube](https://www.youtube.com/%40anthropic-ai)YouTube

[Instagram](https://www.instagram.com/claudeai)Instagram

English (US)

[English (US)](/blog/the-new-rules-of-context-engineering-for-claude-5-generation-models)

[日本語 (Japan)](/ja)

[Deutsch (Germany)](/de)

[Français (France)](/fr)

[한국어 (South Korea)](/ko)

[Italian (Italy)](/it)

Claude Code

Claude Enterprise

Claude Platform

Agents

Coding