Claude Styles Migrating to Skills: Preserve Your Preferences

Claude styles are migrating to skills, which means the saved writing preferences you configured in Claude.ai need to be moved into the new Skills format to continue working. The migration is straightforward: copy your style instructions into a skill, verify the output matches what you expected, and save the result somewhere it will still be available if you switch AI apps. fenbs keeps the original preferences in Skills and prompts, where any connected assistant can read and apply them regardless of which app you are using.

A style in Claude was a saved preference for how Claude writes: concise or detailed, formal or conversational, with bullet points or prose. Skills serve the same purpose but give you more control over the instruction text. The practical effect for most users is a short copy-and-translate step, not a significant change to how they work with Claude.

What the migration actually means

When Anthropic migrates styles to skills, any existing style you saved is either automatically converted or becomes unavailable, depending on the migration path in the version of Claude.ai you are using. Check the Claude.ai interface for the current status: look in your Project settings or account preferences for a notification about the migration.

If your style was converted automatically, open the converted skill and read the instruction text. Automatic conversions capture the broad setting but may miss nuances you added. Review it against how you want Claude to write and adjust the text before you rely on it for important work.

If your style was not converted, you will need to recreate it as a skill. Retrieve your original style text from your account settings or from any notes you kept, and follow the steps below. See claude skills files for how skill files work, and claude skills marketplace for pre-built alternatives if you need a starting point.

How to translate a style into a skill

A style instruction and a skill instruction are both text. The difference is that a skill is named, stored in a project and activated intentionally, while a style was a persistent setting that applied automatically. When translating, the content stays the same but you choose when the skill is active rather than having it apply everywhere.

1. Find your original style text. Check Claude.ai account settings, your account preferences, or any notes where you saved it. If you cannot find it, write a brief description of how you wanted Claude to write: tone, length, structure, any specific rules.
2. Create a new Claude.ai Project or open the one where you do this type of work. Go to Project settings and add a new skill.
3. Paste your style text as the skill content. Add a one-line description at the top: "Writing style: concise, direct, active voice. No bullet points unless the content is a list." This helps you find the right skill quickly.
4. Test the skill with a sample task you know well. Compare the output to what you expected from the old style setting. Adjust the instruction text until the output matches.
5. Save the final skill text somewhere outside Claude.ai, such as fenbs Skills and prompts, so you have it if you set up a new project, move to a different AI app, or need to give the same instructions to a colleague.

If you had more than one style, create one skill per style and name each one after the context where you use it: "client emails," "internal reports," "social copy." That way you activate the right style for each piece of work rather than switching a global setting.

Testing the translated skill

Test the skill against two or three real examples before you rely on it. The test should include edge cases: a piece where the old style felt exactly right, and one where you had to ask Claude to adjust. If the new skill produces a different result than expected, the instruction text is probably missing a specific rule. Add it explicitly rather than hoping Claude infers it.

Common things to check: sentence length, use of bullet points versus prose, whether Claude uses the first person, formality level, and whether it follows specific rules you care about such as Oxford commas, active voice or avoiding certain phrases. For each one, add a short line to the skill text if it is not already there.

How to do this with fenbs

Pair your translated skills with a project record so the style instructions stay linked to the work they apply to.

1. Create a free account and add a project for the work where you use Claude most.
2. Add the translated skill text to fenbs Skills and prompts with a clear name and a note on when to use it.
3. Connect Claude.ai to fenbs over MCP from /integrations. At the start of each session, your connected assistant can read the current skill text from fenbs.
4. If you refine the skill after testing, update the fenbs entry and record the change in Decisions and rules so you know what you changed and why.
5. If a colleague needs the same style instructions, share the fenbs project and give them the right role. They do not need to set up the skill independently in their own Claude account.

When skills do not work like styles

The main difference between a style and a skill is that a skill is activated intentionally rather than applied automatically to every response. If you want the style to apply to every conversation in a project, add the instruction text to the project's system instructions or baseline context rather than a separate skill. That replicates the behavior of the old persistent style setting. Skills are better for style preferences you want to apply selectively. See claude projects vs skills vs artifacts for help choosing the right storage location.