Projects in AI: upload context once, not every time

I'm about to set up an AI project for [area: e.g. a regular
client who does [industry], I write [type of output] for them,
we've worked together for [how long], volume [how many
pieces/tasks a month]].

Typical tasks I'll handle in this project:
- [task 1]
- [task 2]
- [task 3]

Give me a list of materials that belong in the project, so the
model never has to guess. For each item, note:
1. What it is (a specific document type, not a broad category)
2. Exactly what the model will use it for given my tasks
3. How important it is: REQUIRED / USEFUL / LATER
4. Whether it risks containing sensitive data, and what I
   should strip out

At the end, add 5 questions you can't answer from my
description, without which the project will be incomplete.

I'm attaching a document I want to upload to an AI project as
a permanent reference. It's a [document type] and I'll mainly
need [what for: structure, phrasing, numbers without names,
a process].

Make an anonymized version:
- replace people's names with their role in square brackets
  ([sales director], [client contact])
- replace company names with [client], [vendor A], [vendor B]
- remove phone numbers, addresses, emails, national ID
  numbers, contract numbers, and bank details
- keep amounts only where they're needed for the meaning
- keep the structure, phrasing, and terminology unchanged

At the end, attach a list of everything you replaced. Don't
infer anything.

I'm attaching [4] pieces I wrote that I consider a sample of
my style. They're [type: newsletters, proposals, meeting
notes].

Pull a style sheet out of them that I'll upload to the project
as a permanent reference. Structure:

1. VOICE: form of address, first person singular or plural,
   degree of formality
2. SENTENCES: average length, whether I use long compound
   sentences or short, clipped ones
3. STRUCTURE: how I open, how I close, headings, bullets,
   paragraphs
4. VOCABULARY: words and phrases that recur (list specifics)
5. WHAT NEVER SHOWS UP IN MY WRITING: clichés, superlatives,
   phrasing I clearly avoid
6. THREE SENTENCES that are typical of my style — quote them
   verbatim

Work only from the attached texts, don't generalize from how
such texts are usually written. Where the sample is too small,
say so instead of making a claim.

I'm attaching materials from client [name] — [website, brand
manual, old copy, meeting notes].

Build a terminology glossary from them for the project. A
table with columns: CORRECT | WRONG | WHY.

Include:
- product and service names in their exact form, including
  capitalization
- terms of art the client uses differently from the industry
  at large
- abbreviations and their spelled-out form on first use
- how the client addresses its audience (how it does and
  doesn't refer to them)

Work exclusively from the attached materials. Where you're not
sure whether something is intentional or a coincidence, put it
in a separate TO VERIFY section instead of the glossary.

I'm writing instructions for an AI project. Context:

- Who I am: [role, field]
- What I handle in the project: [task types]
- What's uploaded in the project: [list of materials]
- Who receives the output: [client, boss, the public, myself]
- What's bothered me about answers so far: [specifically —
  too long, too generic, makes up numbers, adds unnecessary
  offers]

Write me project instructions in six parts: who I am and what
we're doing here / the model's role / sources of truth and
what to do when the answer isn't in the materials / default
output format / explicit prohibitions / when to ask instead
of guessing.

Requirements: 300 words maximum, rules as short imperatives,
no phrases like “be helpful.” Every rule has to be one where
I can tell whether it was broken.

SOURCES OF TRUTH

Take facts about the client, product, prices, deadlines, and
processes exclusively from the materials uploaded in this
project.

When the answer isn't in the materials:
- don't estimate or fill in from general knowledge
- write on its own line: MISSING MATERIAL: [exactly what I
  need to know]
- finish the rest of the answer normally

When the materials contradict each other (say, two versions
of the price list), flag the contradiction and ask which one
applies. Don't pick for me.

For every claim that comes from the materials, cite the
filename in parentheses.

Before I give you a first task, I want to check what you
actually know from the materials. Answer only from the
uploaded files, don't guess anything.

1. Who's the client and what do they do — 3 sentences.
2. Who's the target audience and how do the materials say we
   address them.
3. List 5 words or phrases I must never use in copy for this
   client, and what to use instead.
4. What does the structure of [output type] look like per the
   template.
5. What's the current price for [service], and which file did
   you get it from.
6. What's missing from the materials for you to be confident
   writing [output type]?

Cite the filename you're drawing on for every answer.

You're my examiner for [subject name]. Work exclusively from
the materials uploaded in this project — the syllabus, course
materials, and my notes.

Quiz me on [topic] like this:
1. Ask me one question and wait for my answer. Don't ask
   about several things at once.
2. Then tell me what was right, what was missing, and what
   was wrong — with a reference to the specific passage in
   the materials.
3. Choose the next question based on my answer: if I did well,
   go deeper; if I did poorly, go back to basics.
4. Never give me the full answer up front. If I don't know,
   give a hint, not the solution.

After ten questions, write a summary: what I know, what's
weak, and what I should study first.

Let's run maintenance on this project. Go through every
uploaded document and every instruction, and return an audit:

1. OUTDATED — materials with a date, version, or figure older
   than [date]; note what's time-sensitive in each.
2. CONTRADICTIONS — places where two materials disagree with
   each other. Cite both versions and the files.
3. DUPLICATES — files that cover the same ground.
4. UNUSED — materials that don't relate to my typical tasks
   ([list the tasks]).
5. GAPS — information you'd need for my typical tasks that
   isn't in the project.
6. INSTRUCTIONS — rules that reference a file that no longer
   exists, or that contradict each other.

For each point, propose a specific action: delete / replace /
add / keep.

This conversation is ending. Go through the whole thing and
pull out what should stick around permanently — so I don't
have to explain it again next time.

Split the output into four parts:

1. FOR PROJECT INSTRUCTIONS — rules, preferences, and
   prohibitions I stated during this conversation that also
   apply to future tasks. Phrase them as short imperatives.
2. FOR MATERIALS — facts, numbers, definitions, and lists I
   gave you that will be useful repeatedly. Organize them into
   a document I can save and upload right away.
3. FOR SAVED PROMPTS — requests that worked well in this
   conversation and that I'll repeat.
4. NONE OF THIS — things that only applied today and have no
   reason to survive. Just list them briefly so I can see what
   you dropped.

Distinguish between what I said (that's binding) and what you
proposed and I never confirmed (mark that UNCONFIRMED).