Claude
Claude holds long inputs well and follows written constraints closely, which makes it a good fit for code review, editing and any task where the instruction list is long. It reacts strongly to explicitly marked sections, so wrapping input in tags or clear delimiters improves results more than rewording the instruction. A CLAUDE.md file in a repository is read by Claude Code on every session and is the right place for project rules.
Models
Claude prompts
All 5- Universal
Translate while keeping terminology fixed
Translates text while leaving a named glossary of terms untouched - useful for documentation and interfaces.
- Universal
Explain this code to a new maintainer
Explains what a file does, why it is shaped that way, and where the traps are - aimed at someone about to change it.
- Universal
Technical SEO audit of a single page
Audits one page from its actual HTML, ranks findings by impact, and marks what it cannot verify without a crawler.
- Universal
Summarise a meeting transcript into decisions and actions
Extracts decisions, owners and open questions from a raw transcript, and refuses to invent an owner where the transcript does not name one.
- Universal
Strict code review of a diff
A review prompt that reports only what would break in production, gives the smallest fix for each finding, and is allowed to say the diff is fine.
Configuration files
All 2- Universal
Editor rules for a Django project
A rules file that pins the Django and Python versions, the app layout and the things an assistant should never regenerate.
- Claude
CLAUDE.md for a PHP project
A project file that stops Claude Code rewriting your conventions, reformatting untouched files or inventing a framework you do not use.
Guides
- Universal
Moving your rules into a config file
How to stop repeating the same instructions in every message, and what belongs in a system prompt against what belongs in the task.