Claude Styles (2026): Presets, Skills and Custom Writing

As of September 17, 2026, Anthropic's help center directs Claude styles customization to Skills and account-wide Instructions for Claude. Its personalization guide does not document a Styles selector or current preset list. Use these documented controls to create reusable writing guidance. Claude personalization.

Historical Styles interface; Anthropic introduced the feature on November 26, 2024.

What happened to Claude Styles?

Anthropic introduced Styles on November 26, 2024, for customizing tone and response structure through presets or writing samples. Anthropic's launch announcement.

The current personalization guide lists Instructions for Claude, Project instructions, and Skills. It does not establish whether every app has removed the Styles selector or automatically migrated saved styles.

Which Claude Styles presets were documented?

Anthropic's November 26, 2024 announcement named three presets: Concise, Formal, and Explanatory. These are historical presets, not a verified current menu. The current personalization guide provides no equivalent Styles preset list.

The 2024 announcement also described custom styles created from uploaded samples and instructions. For the currently documented workflow, use the Skills procedure below. Historical Styles announcement.

Where are the writing controls now?

For general communication preferences, open your account menu, select Settings, and find Instructions for Claude. These instructions apply across conversations. Reserve this space for preferences you want broadly applied. Account instructions.

For reusable task-specific writing guidance, use Customize → Skills. Anthropic documents toggles for enabling individual skills and a + → Create skill → Upload a skill route for ZIP packages containing a skill folder. Using Skills.

Are custom writing instructions available on the free plan?

Skills are available on Free, Pro, Max, Team, and Enterprise, according to the current Skills overview. They require code execution to be enabled. Skills availability.

For individual plans, check Settings → Capabilities → Code execution and file creation. Team and Enterprise organizations also have organization-level controls; an owner can restrict user-created skills. Skills prerequisites.

Create a custom writing style from samples

Build a writing skill around a format you regularly use. Anthropic's Skills tutorial recommends naming the format, describing the tone, and providing an example that meets your standards. Skills tutorial.

1. Choose a sample you would be happy to publish again.
2. Identify what to preserve: sentence length, level of detail, headings, or vocabulary.
3. Paste the sample into a conversation and ask Claude to create a skill for that writing task.
4. Review the proposed instructions before packaging them.
5. Upload the skill through Customize → Skills and enable it.
6. Try a new assignment and compare the response with your sample.

Here is an original starter prompt:

Create a reusable writing skill from the sample below. Describe its tone, paragraph structure, vocabulary, and level of technical explanation. Preserve those patterns without copying the sample's facts or distinctive sentences. Apply the skill when I ask for practitioner tutorials. Ask me to resolve any unclear preference before finalizing the instructions. Sample: [paste your writing].

Create a style from a description

You can describe the writing behavior directly when you do not have a suitable sample. Give the skill one repeatable task and a clear trigger. Anthropic recommends focused skills with explicit instructions and examples where useful. Custom skill guidance.

1. Name the audience and document type.
2. Specify tone, structure, and detail level.
3. Explain when the guidance should apply.
4. Ask Claude to turn that description into a skill.
5. Inspect the generated package, upload it, and test it.

Five custom style descriptions to paste

These original descriptions can form the writing instructions for a skill. Add your own examples and specify the task that should trigger each one. Browse AI prompts for additional tasks to use when testing.

1. Practitioner tutorial

Write for an AI practitioner who understands the goal but has not used this tool. Start with the outcome and prerequisites. Explain each action before introducing the next dependency. Use numbered steps for procedures and short paragraphs for reasoning. Preserve exact names from supplied documentation. Label assumptions and leave unverifiable commands out. End with a practical way to check whether the task succeeded.

2. Decision memo

Write for a team lead deciding what to do next. Open with the recommendation and the condition that would change it. Compare options using the same criteria. Separate evidence from judgment. Include costs or limits only when the supplied sources establish them. Keep the tone direct and measured. Close with the decision needed, who owns it if specified, and the next reversible action.

3. Patient technical explainer

Explain one concept at a time to a curious beginner. Define unfamiliar terms when they first appear. Use a small example, then explain where the example stops being accurate. Keep necessary technical detail and remove decorative jargon. When I ask a narrow question, answer it before expanding. Use an analogy only if you also connect it back to the actual mechanism.

4. Research digest

Write a concise digest for readers evaluating AI research. Begin with the research question. Separate the authors' claims, the evidence they provide, and your interpretation. Retain qualifications and relevant experimental conditions. Cite the supplied primary sources beside the claims they support. Do not manufacture missing results or turn a limited experiment into a general ranking. Finish with questions the evidence leaves open.

5. Editorial cleanup

Edit for clarity while preserving my meaning and degree of certainty. Prefer concrete verbs and familiar words. Remove repeated conclusions, empty praise, and introductions that delay the point. Keep technical names unchanged. Explain substantial meaning changes separately so I can review them. Do not add facts, examples, quotations, or promises unless I supply them. Match the original audience and maintain a consistent voice.

Styles vs project instructions vs profile preferences vs system prompts

Sources: personalization scope, Skills behavior, API system parameter.

For project-specific writing, open the project, choose Set project instructions, and save your guidance. Put reusable source material in project knowledge. Anthropic notes that context is not shared between project chats unless added there. Project setup.

For an API application, supply the writing rules through the documented system parameter. Treat that as application configuration; do not assume a saved chat preference is your API's configuration. See our LLM API pricing guide when planning that separate integration.

Limits and troubleshooting

Skill not used: check that it is enabled, make its description identify the task, and request it by name. Upload unavailable: check code execution and organization permissions. Skills troubleshooting.

Writing still feels wrong: compare one response with your reference sample. Identify one concrete problem, such as excessive background or unsuitable headings, and revise that instruction before testing again.

Missing Styles menu: use the documented Skills or account-instructions controls.

FAQ

Where do I find Claude Styles now?

Current help directs reusable tone and format customization to Customize → Skills. For account-wide communication guidance, use Settings → Instructions for Claude.

Can I make Claude write like me?

You can supply your writing as an example and ask for reusable guidance. Evaluate the resulting instructions and test them on a different assignment; a sample is not proof of exact voice matching.

Are Claude writing skills free?

The current Skills overview includes the Free plan. Code execution must be enabled, and organization controls apply where relevant. Availability.

Should I use a skill or project instructions?

Use a skill for a repeatable writing method across tasks. Use project instructions when the guidance belongs to one project's audience, context, or requirements.

Sources

• Current Claude personalization guide
• Anthropic's Styles launch announcement, November 26, 2024 (indexed historical text; live page returns 404)
• What are Skills?
• Use Skills in Claude
• How to create custom Skills
• Teach Claude your way of working using Skills
• Create and manage projects
• Messages API reference: system instructions