# Project Instructions Template

From *Context Matters*, Episode 1: How I set up AI so it doesn't sound like AI.
By Javier Otero, contextur.com

---

## What this is

Project instructions are the second of three layers. They cover one area of your work: a company, a client, a skill you're learning, a recurring kind of task.

They override your Account instructions. That's the point. Your Account says who you are everywhere; a Project says what this one area needs.

Keeping areas separate stops one job's rules from leaking into another. Your cooking notes shouldn't shape a client email.

## Where it goes

- **Claude:** create a Project, then add instructions in the Project's instructions panel.
- **ChatGPT:** create a Project, then add instructions in the Project settings.
- **Other tools:** look for "workspaces," "spaces," "gems," or "projects" with their own instructions.

## How to use this template

Make one copy per area of work. Replace everything in [brackets]. Review it about once a month, or when something important changes.

---

## Template

```
WHAT THIS PROJECT IS FOR
This is my working environment for [the area of work].
[One sentence on what you're trying to achieve here.]

WHAT YOU SHOULD KNOW
- [Key fact about this area. Example: "We're a two-person studio
  that works mostly with nonprofits."]
- [Current state or phase. Example: "We're focused on growing
  recurring clients this year."]
- [Who else is involved, if it matters. Example: "My partner leads
  design; I lead strategy and estimates."]

BOUNDARIES TO HOLD
- [Something AI should never do here. Example: "Never show our
  hourly rates or internal math in client-facing drafts."]
- [Something easy to get wrong. Example: "We don't do paid ads
  work. Don't suggest it."]

HOW I WORK HERE
- [What useful output looks like. Example: "Drafts in our proposal
  structure, ready for me to edit."]
- [Format. Example: "Deliver documents as Markdown."]

WHEN TO ASK ME
- [When AI should check in. Example: "If a decision depends on
  numbers you don't have, ask me for them instead of guessing."]
```

---

## A filled-in example

```
WHAT THIS PROJECT IS FOR
This is my working environment for my bakery's wholesale business.
I want to land three new café accounts this year.

WHAT YOU SHOULD KNOW
- We bake for about 12 cafés across two neighborhoods.
- Capacity is the constraint. We can add 4 accounts, not 10.
- My sister handles delivery and scheduling.

BOUNDARIES TO HOLD
- Never quote prices in drafts. I set them per account.
- We don't do custom cakes for wholesale. Don't suggest it.

HOW I WORK HERE
- Short, friendly outreach emails I can personalize.
- Keep everything in plain language. Owners are busy.

WHEN TO ASK ME
- If a recommendation depends on our capacity, ask before assuming.
```

---

## Three things to check before you save

1. **Does it override, or just repeat?** If a line already lives in your Account instructions, cut it here.
2. **Is there a boundary?** The "never do this" lines are often the most valuable part. Every Project should have at least one.
3. **Is your material in the Project, or just described?** Instructions tell AI how to work. Your actual files, examples, and past work are the third layer, Context. That's where most of the improvement comes from, and it's what Episode 2 covers.

---

Watch the series: [contextur.com/context-matters](https://contextur.com/context-matters?utm_source=template&utm_medium=download&utm_campaign=context-matters&utm_content=ep01-project)
Contextur prepares your files, emails, and notes into context AI can actually use. Local and private. [contextur.com](https://contextur.com/?utm_source=template&utm_medium=download&utm_campaign=context-matters&utm_content=ep01-project-footer)