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

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.

Fine-Tuning Qwen 3:0.6B for Question Categorization – Baseline vs Finetuned Results
Fine-tuning a tiny 0.6B parameter LLM (Qwen 3:0.6B) with ~850 household questions using Unsloth. Baseline prompting scored 10% accuracy; finetuned results likely exceed 80-90%.

Fix for Running OpenClaw on Android via proot Ubuntu: Hijack networkInterfaces() to Resolve uv_interface_addresses Error 13
A developer shares a fix for running OpenClaw 2026.3.13 on Android 16 via Termux and proot Ubuntu 25.10, where the app crashes with 'uv_interface_addresses returned Unknown system error 13'. The solution is a JavaScript hijack script that overrides os.networkInterfaces().

5 Coherence Checks Before Any OpenClaw Profile Goes Live
Stop chasing perfect spoofing. Internal signal coherence matters more. TLS, locale, WebGL, canvas, and behavior checks from r/openclaw.