Set up a Claude Project so you stop re-explaining context every chat

PROJECT KNOWLEDGE DOCUMENT — Q3 Product Launch — Northwind App

Paste this as a text file into this Project's knowledge, then paste the CUSTOM INSTRUCTIONS section below into the Project's custom instructions field. Everything here should be true for every future chat in this Project, not just the current one.

WHAT THIS PROJECT IS
Coordinating copy, positioning and internal FAQs for the Northwind app launch on October 14. Done means every asset is consistent with the same three positioning pillars.

AUDIENCE AND STAKEHOLDERS
Marketing team drafting external copy, and support leads writing internal FAQs for the same launch.

STANDING FACTS
Treat the following as ground truth for every chat in this Project. If a request in a chat conflicts with one of these, flag the conflict instead of silently picking a side.
- Launch date is October 14, not negotiable.
- Product is called "Northwind," never "Northwind App" in customer-facing copy.
- Pricing is not final and must never be stated as a number in any draft.

TERMINOLOGY
"NW" always means Northwind internally, never spelled out in Slack drafts. Customers are called "members," never "users."

---
CUSTOM INSTRUCTIONS (paste into the Project settings field)

When responding inside this Project:
- Assume the project knowledge above is already true; do not ask me to re-explain it.
- Default output register: Plain, confident, no exclamation points, short paragraphs over bullet walls
- Never invent a fact about this project that is not in the knowledge document or in the current chat — say what is missing instead of guessing.
- If a new fact emerges in a chat that should apply to every future chat, say so explicitly at the end of your reply so I know to add it to the knowledge document, rather than quietly assuming I will remember.