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

OpenClaw 101: The Ultimate Setup Guide for New Users

Building a Full BI System with Claude Code and Metabase for Under $50/month
A Reddit user built a complete BI system using Claude Code, BigQuery, and self-hosted Metabase — replacing $15k expert quotes with 3 days of work and $30/month in cloud costs.
Upgrading an NVMe Raspberry Pi 5 to OpenClaw 9.3 Using a Staged Clone
A developer upgraded a production NVMe Raspberry Pi 5 from OpenClaw 2026v7.1-2 to 9.3 by cloning to a spare Pi, wiping the original, and restoring — with the agent SSHing in to do the work.

How to avoid unexpected OpenRouter costs in OpenClaw automation
A developer team accidentally spent $750 in 3 days on OpenRouter by defaulting to Claude Sonnet 4.6 ($3/M tokens) across all automation tasks. They reduced costs by 97% by changing default models, locking cron jobs and subagents to cheaper options, and reserving expensive models only for sensitive work.