Improve Claude’s Writing with the Claude Style Patch

What Claude Style Patch Does

Claude Style Patch is a drop-in set of writing instructions for CLAUDE.md. It is designed to reduce dense, compressed prose and several recurring stylistic habits found in recent Claude generations. The patch applies not only to chat replies, but also to generated documents, deliverables, prompts, and code comments.

The project was refined through repeated use with Claude Code and Claude.ai across multiple generations of Opus and Fable. Rather than asking Claude to write more clearly in general terms, it gives concrete rules that identify an unwanted habit and specify how to repair it.

Key Features

• Drop-in configuration: Append one file to a global or project-level CLAUDE.md.
• Concrete writing rules: Each rule names a habit, illustrates it, and provides a rewrite strategy.
• Broad coverage: The instructions apply to ordinary conversation, documents, deliverables, agent prompts, and code comments.
• Flexible deployment: Use it in Claude Code, Claude Projects, or another system prompt.
• Public-domain license: The patch uses CC0, so you may copy, modify, fork, or extract parts without attribution.

Writing Habits It Targets

The patch focuses on several tendencies in Claude’s default prose:

• Announcing a point before actually making it.
• Using a colon so that the first half of a sentence labels the second half.
• Opening paragraphs with verbless fragments.
• Stacking compressed phrases until sentences become difficult to read.

These patterns can become more pronounced as a conversation grows longer or more abstract. The patch attempts to preserve direct, readable prose under those conditions.

Install the Patch Globally

For Claude Code, append the remote STYLE.md file to your global configuration:

curl -sL https://raw.githubusercontent.com/andrewroxby/claude-style-patch/main/STYLE.md >> ~/.claude/CLAUDE.md

The >> operator appends the downloaded instructions rather than replacing the existing file. Run the command only when you intend to add the patch, because repeating it will append another copy.

Once installed globally, the style instructions become part of your Claude Code configuration across projects that use the global CLAUDE.md.

Install It for One Project

If you want to test the patch or apply it only to a specific repository, append it to the project’s own CLAUDE.md:

cd path/to/your/project
curl -sL https://raw.githubusercontent.com/andrewroxby/claude-style-patch/main/STYLE.md >> CLAUDE.md

Project-level installation is useful when a repository needs a particular prose style but you do not want to change Claude’s behavior in every Claude Code session.

Use It Outside Claude Code

The patch is plain instruction text, so it does not depend on a special plugin or runtime. To use it with a Claude Project, copy the contents of STYLE.md into the project’s custom instructions. You can also paste it into a system prompt in another environment.

1. Open the repository’s STYLE.md file.
2. Copy the complete contents.
3. Open the custom-instructions or system-prompt editor for your environment.
4. Paste the instructions and save the configuration.

The source file is available from the Claude Style Patch repository.

Basic Usage

After installation, use Claude normally. You do not need to invoke a command or mention the patch in every request. Ask for the output you need, and the instructions will guide how Claude presents it.

Example: Generate a Document

Write a technical overview of this service for new engineers. Explain its architecture, request flow, dependencies, and operational risks.

The patch is intended to make the resulting document easier to read by discouraging prefatory announcements, fragment-based paragraph openings, and overly compressed sentence structures.

Example: Request Code Comments

Review this module and add comments where they clarify non-obvious behavior. Keep the comments concise and useful to future maintainers.

Because the style specification also covers code comments, its rules can influence explanatory prose written inside source files.

Example: Create a Prompt for Another Agent

Hew closely to the response style instructions. Write a detailed implementation prompt for another agent that will add authentication to this application.

This explicit reminder is especially useful before Claude produces long prompts or substantial new prose.

Advanced Tips

Reinforce the Rules Before Dense Tasks

Compliance is good but not perfect, and it can degrade during long conversations. The patch’s opening paragraph asks Claude to re-check the rules when material becomes dense, but this does not eliminate every lapse.

Before a complex writing task, add the following reminder:

Hew closely to the response style instructions.

The project author reports that this wording works particularly well before generating long prose or prompts for other agents.

Choose Global or Project Scope Deliberately

Use the global configuration when you consistently prefer the patch’s style across Claude Code. Use a project-level CLAUDE.md when the rules should apply only to one codebase or when you want to evaluate the results before adopting them more broadly.

Account for the Context Cost

The style file is roughly 1,600 words. Those instructions occupy part of the available context, so consider that cost when working within constrained environments. The project author reports that the improvement has been worth the additional context in both Claude Code and Claude.ai sessions.

Expect Model Differences

The README reports that Fable appears to follow the specification more consistently than Opus, particularly in longer threads. Treat the patch as guidance rather than a guarantee, and reinforce it when a conversation becomes lengthy or abstract.

Customize the Patch

Because the project is released under CC0, you may copy it, fork it, remove rules, or reuse selected sections. This makes it possible to keep only the guidance that matches your preferred writing style and context budget.

Conclusion

Claude Style Patch offers a simple way to change Claude’s prose through explicit, repair-oriented instructions. Append it to a global or project-level CLAUDE.md, or paste it into custom instructions or a system prompt. For long and demanding writing tasks, reinforce the configuration by asking Claude to hew closely to the response style instructions.