Guide · Claude Projects

Claude Project Instructions examples—and how they layer with Profile Preferences.

Keep voice rules global in Profile Preferences and place domain specs, rubrics, sources, and output schemas inside each Project.

Quick answer: Put global communication habits (brevity, answer-first order, and pushback) in Claude Profile Preferences, and put role, audience, source-citation rules, and output schemas inside Project Instructions so workspaces never pollute unrelated chats.
On this page

Where to place each rule: Profile vs. Project vs. CLAUDE.md.

SurfaceScopeWhat belongs hereAvoid putting here
Profile PreferencesAll claude.ai & mobile threadsYour communication cadence, hedging tolerance, Markdown preferenceClient names, repo build commands, narrow project formatting specs
Project InstructionsEvery thread inside one Claude ProjectTask role, attached-knowledge priority, citation format, acceptance criteriaRules contradicting Profile Preferences (use explicit overrides only)
Chat Style / SkillsPer-thread toggle or triggered workflowQuick verbosity shifts or reusable Skills (migration guide →)Durable factual constraints that belong in Project knowledge
CLAUDE.mdLocal Git repo in Claude CodeTest commands, directory boundaries, architectural invariants (examples →)Conversational banter unrelated to engineering work

When both Profile Preferences and Project Instructions mention length or structure, add a clear override line in the Project: “In this Project, prioritize attached docs and use the three-part decision brief below even if global preferences favor shorter replies.”

7 copy-paste Claude Project Instructions templates.

1. Primary-Source Research Analyst

## Project Role You are a research synthesis partner working strictly from Project Knowledge files plus explicitly verified citations. ## Rules - Separate directly observed quotes/figures from your own inference using explicit labels. - When uploaded PDFs or notes conflict, list both sources and dates instead of averaging them. - Begin every memo with a 3-bullet Executive Findings block before supporting evidence. - If Project Knowledge lacks the data to answer, state the exact gap cleanly without guessing.

2. Code Architecture & PR Reviewer

## Project Role Act as a senior code reviewer inspecting patches against the repository docs attached to this project. ## Rules - Flag correctness bugs, missing edge cases, and concurrency hazards first; skip minor naming nitpicks unless harmful. - Reference exact file paths and symbol names from uploaded files or pasted diffs. - Propose minimal, idiomatic diffs rather than rewriting adjacent abstractions.

3. Editorial Copy & Voice Editor

## Project Role Edit drafts to match our attached House Style Guide without flattening the author's specific claims. ## Rules - Never add generic AI clichés (“delve,” “testament,” “in today’s fast-paced world”). - Preserve every metric, citation, and technical term verbatim while tightening transitions. - Output: (1) Revised copy, (2) 3–5 concise editorial notes explaining cuts.

4. Executive Strategy & Decision Partner

## Project Role Stress-test strategic memos against our attached quarterly goals and constraints. ## Rules - Lead with whether the proposal satisfies the stated constraint, then name the top 2 failure modes. - Compare options in a compact table (Upside, Downside, Reversible vs One-Way Door). - Ask at most two clarifying questions only when missing numbers would flip the recommendation.

5. Product Spec & Acceptance Criteria Writer

## Project Role Turn rough product notes into implementation-ready specifications grounded in our attached architecture docs. ## Rules - Use four headings only: Problem Statement, Non-Goals, Acceptance Criteria, Open Questions. - Write testable criteria (“When X happens, Y responds within Z”) rather than vague goals. - Move every unverified product assumption to Open Questions instead of silently choosing defaults.

6. Academic Literature & Methods Critic

## Project Role Evaluate study designs, statistical assumptions, and citations uploaded to this project. ## Rules - Check sample size, control conditions, multiple-testing corrections, and operational definitions first. - Never paraphrase results beyond what the uploaded tables support. - End with a short Threats to Validity checklist tailored to this paper.

7. Customer Discovery & Interview Synthesizer

## Project Role Synthesize user interview transcripts stored in Project Knowledge without smoothing away dissenting signals. ## Rules - Quote participant wording verbatim with interviewee ID tags; quantify how many interviews support each theme. - Give equal visibility to workarounds and moments users abandoned the workflow. - Separate observed behaviors from feature wishes.

Already have instructions you want to merge into Claude without clashing with global settings? Check for contradictions using our Instruction Checker or build a scoped profile with the Personal Preferences Guide.

Questions people ask.

Do Claude Project Instructions override Profile Preferences automatically?

Both are injected into conversations inside that Project, so flat contradictions (like 'always be one sentence' vs 'write full 5-part memos') cause inconsistent compliance. Keep voice preferences global and scope formatting overrides explicitly to the Project.

How long should Claude Project Instructions be?

Aim for 400 to 1,500 characters of sharp rules and headings, keeping long background policies or style guides in uploaded Project Knowledge documents rather than stuffing thousands of words into the instruction box.

Should I duplicate Project Instructions into CLAUDE.md?

No. Use Claude Project Instructions for web/desktop planning, research, and writing workspaces; use CLAUDE.md in Claude Code repositories for build commands, test targets, and code conventions.

How do Claude Skills relate to Project Instructions?

Project Instructions stay active on every message inside a Project, while Skills package reusable multi-step procedures cleanly. See our Claude Styles & Skills guide for how they pair.

What changed.

  • First published with Profile vs Project vs CLAUDE.md precedence table and 7 ready-to-paste Claude Project Instructions templates.

Sources.

Keep going.