Claude Styles are moving to Skills: how to migrate.
By Bernard Huang · Updated
Anthropic is retiring the per-chat Styles picker in Claude. Here is where your old writing presets and custom voices belong now.
On this page
Why the old picker was split into Preferences and Skills.
People used the old Styles dropdown for two very different jobs: permanent habits like “never use filler intros” and task-specific templates like “write in our weekly release-note format.” Splitting the two means you no longer have to toggle a preset on and off between threads:
| What you kept in the old preset | Where to migrate it now | Why it works better |
|---|---|---|
| Everyday tone, brevity, directness, and pushback | Settings → Profile / General → Personal Preferences | Applies automatically in every chat without picking from a dropdown. |
| Repeatable document formats, rubrics, or brand voice rules | Claude Skills (SKILL.md) | Loads only when the task calls for that specific format, keeping ordinary chats clean. |
| Client-specific or codebase-specific instructions | Claude Project Instructions | Scoped to one workspace and shared with project files. |
| Terminal CLI communication style | Claude Code ~/.claude/output-styles/ | Keeps coding instructions intact via keep-coding-instructions: true. |
Step 1: Move always-on tone rules to Personal Preferences.
If you used the old Concise or Formal style just to stop Claude from over-explaining, paste those rules once into Settings → Profile → Personal Preferences:
For 15 role-specific blocks, see Claude Personal Preferences: 15 examples.
Step 2: Turn task-specific writing voices into a Skill.
If your old Style described a specific deliverable—like an executive memo, customer support reply, or technical RFC—turn it into a Skill so Claude doesn’t format your Python debugging answers like a boardroom memo.
Include three short parts in your Skill:
- When to trigger: One sentence naming the exact tasks where Claude should use the Skill.
- Structure and rules: Heading order, paragraph length, and banned phrases.
- One short example: A 3–5 sentence sample showing the target style.
Step 3: Use /output-style in Claude Code.
While web Claude Styles are moving to Personal Preferences and Skills, Claude Code in the terminal keeps its own /output-style command backed by Markdown files in ~/.claude/output-styles/. Always include keep-coding-instructions: true in the YAML frontmatter (see the Claude Code personality guide).
Questions people ask.
Why did Anthropic retire the old Styles menu in Claude?
Claude Styles are being retired and replaced by Personal Preferences (for account-wide tone defaults) and Skills (for repeatable task workflows and writing formats), so users do not have to toggle a preset on and off between conversations.
How do I replace the old Concise preset in Claude?
Open Settings, then General, and add a two-line rule in Personal Preferences: 'Lead with the direct answer in the first sentence. Keep routine replies under 150 words in plain prose without filler intros or closing offers.'
Should I put my writing voice in a Claude Skill or Personal Preferences?
If you want Claude to talk to you that way in every conversation, put it in Personal Preferences. If it is a writing format for specific documents—like newsletters, memos, or support emails—put it in a Skill or a dedicated Project.
Are output styles in Claude Code also changing?
No. While web Claude Styles are being migrated to Skills and Personal Preferences, Claude Code in the terminal continues to support ~/.claude/output-styles/*.md selected with the /output-style command.
What changed.
- First published covering how to move rules from the retiring Styles menu into Personal Preferences, Skills, and Projects.