Free to read · no account needed

16 min · claude

Claude Projects: knowledge and instructions that stay

Goal: Put standing instructions and reference files in a Project so each new chat inherits your rules—without re-pasting your life story.

Best for: Ongoing client work, courses, long writing, team playbooks.

Same idea as ChatGPT Projects: one workstream, redacted files, explicit Unknown rules. Claude often shines on long docs—still verify facts and export finals to your system of record. Projects reduce retyping; they do not grant truth.

Projects work when knowledge is curated and instructions are short. Dumping every PDF teaches noise; a one-page instruction + three source docs beats a junk drawer.

Why beginners skip this

Skipping the hard part of “Claude Projects: knowledge and instructions that stay” feels fine until a live thread pays the bill. Hold: Standing instructions and files live in the Project—not in every paste—check it once this week, or it stays a bookmark Mid-week cost shows up as rework, not as a missing bookmark.

Step 1 — Create with a sharp name

Name for the workstream (Client-River-Q4, Course-HCI-notes), not Stuff or your own name.

Step 2 — Instructions that bind

Do this step with a real artifact open—not from memory.

Project instructions:
- Audience: [ ]
- Tone: [ ]
- Prefer files I uploaded over general guesses
- If missing: Unknown — do not invent
- Never ask for secrets/raw PII
Custom style lines: [we say / we never say]
Example

Filled prompt

Create a Project instruction (≤12 lines) for customer-FAQ answers. Knowledge: 3 official FAQ PDFs only. Rules: quote doc titles, never invent policy, draft only.

What good output looks like

  • Pulls from Project/file named in the ask for “Claude Projects: knowledge and”
  • Standing instructions respected; no silent scope creep
  • Decisions quoted or labeled Unclear — never “sounds good”
  • One-minute check: does output match claude-projects-knowledge-and-instructions Done?
  • Pass/fail dated (Asia/Shanghai) sits next to the artifact

Step 3 — Hygiene monthly

Remove stale PDFs. Bump voice guide versions. Start fresh chats inside the Project when a thread goes sideways. If two clients share vibes but not facts, use two Projects.

Audit my Project file list (names only): [list].
Which look stale for Q4 work? Suggest keeps vs archive. Do not invent file contents.
Example

Filled prompt

Live task this week (not a toy): apply this guide's Goal — Put standing instructions and reference files in a Project so each new chat inherits your rules—with
Fill with your real artifact names/files. Constraints: no invented facts; label Unknowns; stop before send/delete/pay.
Return the working prompt + one pass/fail check I can mark in a minute.

What good output looks like

  • Standing instructions respected; no silent scope creep
  • Decisions quoted or labeled Unclear — never “sounds good”
  • One-minute check: does output match claude-projects-knowledge-and-instructions Done?
  • Pulls from Project/file named in the ask for “Claude Projects: knowledge and”

Save this card

Card: Standing instructions and files live in the Project—not in every paste—check it once this week, or it stays a bookmark. Keep this beside the tool; read before you start.

1. What I shipped: ___ 2. What I refused: ___ 3. What I will never-do again: ___ (date: Asia/Shanghai)

  • [ ] Tools/writes paused
  • [ ] Refuse-line dated
  • [ ] Artifact path saved
  • [ ] Next link chosen (or stop)

Before you start

Open the Claude Project you will keep. Confirm standing instructions + the knowledge file for “Put standing instructions and reference” are current. Guide: claude-projects-knowledge-and-instructions. If you only have a blank practice box, stop and fetch the real job first.

Default posture: draft-only until a human confirms sends/writes. Date your first refuse-line (Asia/Shanghai) before granting new tools.

  • Goal in one line: ___
  • Allowed tools: ___
  • Forbidden: ___
  • Human approve needed for: ___

How to use this week

This week in Claude: put standing instructions + one scrubbed file into a Project; open a fresh chat and confirm it loads without re-paste. Date the setup on a live artifact—not a blank demo. Write one refuse-line and date the note (Asia/Shanghai). If you only skimmed claude-projects-knowledge-and-instructions, put 25 minutes on the calendar and redo once.

Keep it real

Run this guide’s Practice now on work you will actually ship this week—not a fictional scenario. Dated notes beat perfect theory.

Do not bookmark-only

Finish Practice now, then tick this guide on your path. Titles unread are not skills.

Close the loop

After Practice now, write one line: what you will refuse next time. That line is the habit.

Example

Filled prompt

Project has 6 files; chats ignore the style guide.
Rewrite standing instructions: "always open style.md first; never invent SLA."
Test with refund-window ask.

What good output looks like

  • Pulls from Project/file named in the ask for “Claude Projects: knowledge and”
  • One-minute check: does output match claude-projects-knowledge-and-instructions Done?
  • Standing instructions respected; no silent scope creep
  • Decisions quoted or labeled Unclear — never “sounds good” [claude-projects-knowledge-and-instructions#3]
Example

Filled prompt

Chats ignore style.md.
Instructions: always open style.md first; never invent SLA. Test refund ask.
Context: real workstream this week (Asia/Shanghai). Name actual files/people.
Constraints: no invented metrics/owners/prices; label Unknowns; stop before send/delete/pay.
Done check: I can mark pass/fail in one minute on the output.

What good output looks like

  • Decisions quoted or labeled Unclear — never “sounds good”
  • Pulls from Project/file named in the ask for “Claude Projects: knowledge and”
  • One-minute check: does output match claude-projects-knowledge-and-instructions Done?
  • Standing instructions respected; no silent scope creep

Red flag

Expired policy still in knowledge; instructions fighting knowledge; answers citing dead files—clean before the next thread.

Pitfalls

PitfallFix
Instructions that contradict each otherOne voice; freeze facts outside
Dumping every file into Project knowledgeCurate; label must-use vs optional
Uploading whole DriveCurate
Instructions without UnknownAdd honesty line
Mixing clientsSeparate Projects
Never exporting finalsWiki/git is source of truth

Practice now

Live card: one Claude artifact/diff/email pass for “Claude Projects: knowledge and instructions that stay” with Blind before share (Asia/Shanghai).

Move one live job into a Project today. Write ≤15 lines of standing instructions. Attach one file. Run one task in a new Project chat. Note what you no longer retype.

Today card (copy) — claude-projects-knowledge-and-instructions: 1. Artifact I will produce: ___ 2. Pass/fail check: ___ 3. Refuse-line if tempted to skip verify/send: ___ (date: Asia/Shanghai) 4. One never-do from this guide: ___

  • [ ] Artifact path written
  • [ ] Refuse example would say "yes"
  • [ ] Dated Asia/Shanghai

One sentence takeaway

Standing instructions and files live in the Project—not in every paste—check it once this week, or it stays a bookmark

  • You can point to a dated refuse-line
  • You have one artifact path from tonight
  • You can teach the red flag in one sentence

Next

Style guides that stick · ChatGPT Projects · Artifacts · Standing vs user

Pair with today: open the first Next link (claude-style-guides-that-stick) only after you dated a refuse-line for this guide (Asia/Shanghai).

← Back to home · Learn · Tools · Compare · Start