Using Claude to analyze writing patterns for better custom instructions

A Reddit user shared a method for creating more effective custom instructions for Claude by having the AI analyze actual writing samples rather than relying on subjective descriptions of tone.
The problem with standard custom instructions
The user notes that typical advice for custom instructions involves pasting examples and adding lines about tone, but this only works for a few messages before Claude drifts back to default behavior. The issue is that custom instructions describe voice from memory - you write down what you think you do ("direct," "uses short sentences," "avoids jargon"), which captures only a fraction of what makes your writing distinctive.
The analysis method
The user collected 10 writing samples across different formats and fed them to Claude with a specific request: identify concrete patterns rather than summarizing tone. Patterns that emerged included:
- Which punctuation you avoid entirely
- Where your analogies come from
- Specific word choices (e.g., "I never use the word 'ensure'")
These were patterns the user had been doing for years without consciously noticing them.
Implementation and results
After Claude identified these concrete patterns, the user organized everything into a structured document and used it as a system prompt. The difference was immediate - Claude stopped drifting because the guide was specific enough to anchor it. The user emphasizes that "I never use the word 'ensure'" is a useful instruction, while "I write in a direct tone" is not.
The Reddit post mentions that a training guide has been published for those who want to know how to implement this method themselves.
📖 Read the full source: r/ClaudeAI
👀 See Also

Documentation for Writing MCP Tools in C# .NET Framework for Claude Desktop/Code
Complete documentation and C# coding examples for creating custom MCP tools using .NET Framework 4.8, enabling Claude Desktop/Code to automate interactions with external processes, software, APIs, and IoT devices.

CLAUDE.md Constitution: Building a Personal AI Agent — Part II File Walkthrough
A CEO shares the annotated CLAUDE.md file — 16 sections covering identity, proactive initiative, memory, deadlines, and hard rules — built over 6 weeks for a 50-person company.

Building API endpoints with Claude: Practical prompt engineering lessons from a 70+ endpoint project
A developer built 70+ LinkedIn automation API endpoints with Claude writing 80% of the code, discovering that treating prompts like contracts with explicit constraints works better than natural language instructions for action-taking agents.

CLAUDE.md Files Are Often Organized for Developers, Not AI Models – Here's Why That Matters
CLAUDE.md files commonly place Hard Rules at line 47, after background and tech stack. By the time the model reads constraints, it has already constructed conflicting assumptions. A better structure puts hard rules first.