Claude / Claude Projects & Instructions
Claude: separate general preferences from project rules
List preferences that apply everywhere and rules that belong to one assignment. Identify any conflicts before saving either set.
Environment and inputs: Claude user guide · Feature and source access depend on the active account, app and organization settings. Optional file or app steps have a text-excerpt fallback. No fixed model version, price or usage quota is assumed.
What you will make
A practical Claude guide to separate general preferences from project rules. Use the sample input and prompt, then check the result. Use a fictional support-document review as the practice setting. Keep passages and your interpretation in separate output fields.
Prepare the source and scope
List preferences that apply everywhere and rules that belong to one assignment. Identify any conflicts before saving either set. Open Claude and start a focused conversation, or use the appropriate existing project for recurring work.
Try this prompt
In Claude, provide the prepared input, then send the following request. For real work, replace fictional details with approved facts.
Sort these instructions into general communication preferences, project-specific constraints and one-time task details. Explain uncertain classifications.Review the result
Start a simple unrelated task and check that customer-specific rules do not appear there. Record each correction and its supporting source.
If the answer is wrong or incomplete
An account-wide instruction can influence unrelated work. Keep project terminology and confidential background scoped to the project. Put the source excerpt and the request in separate labeled blocks. For longer reviews, retain paragraph labels so corrections remain traceable.
Practice and completion check
Repeat with one incomplete input. Check the answer against the review criteria, remove unsupported claims and save the prompt with its source version. This workflow has not been verified in a customer deployment.