Module 13 · Lesson 05

Projects and Persistent Memory for Recurring Workflows

Reading time: 14 minutes Track: Claude Fluency for Teams · Knowledge worker path

The recurring-task opportunity

Most knowledge workers have 5-10 tasks they do every week using Claude: a weekly report, customer communications, meeting prep for recurring stakeholders, research summaries in a specific domain. These tasks have stable context that doesn't change — and yet without Projects, that context gets re-established from scratch every time.

Projects eliminate this waste. Here's how to set them up for maximum effect.

Identifying your Project candidates

Run through your last two weeks of Claude usage. Flag tasks that:

• You do more than once a week
• Have context that doesn't change (your role, the audience, key background)
• Where you've gotten frustrated re-explaining the same background

These are your Project candidates. Most people identify 3-5.

Designing effective Project instructions

Project instructions are a persistent system prompt. They run before every conversation in the Project. The quality of these instructions directly determines how much setup you skip per session.

Structure that works:

## Who I am
I'm a [role] at [company]. [2-3 sentences about your work and context]

## What this Project is for
[1-2 sentences on the specific recurring task]

## Background you always need
- [Stable fact 1]
- [Stable fact 2]
- [Relevant constraints or preferences]

## How I want you to work with me
- [Communication style preferences]
- [Format preferences]
- [What to verify vs. proceed on]

What not to include:

• Information that changes frequently (current status, recent decisions)
• Information specific to one conversation
• Generic instructions that apply to all Claude use (those belong in Memory, not a Project)

Building a Project knowledge base

For Projects where Claude needs reference material:

Add documents to the Project: product specs, style guides, key frameworks, reference data. These are available in all Project conversations without you needing to paste them.

Useful documents to add per Project type:

Memory vs. Project: what goes where

Memory: Personal context that applies across all your Claude use regardless of Project

• Your role and background
• Communication style preferences
• Technical environment
• Standing behavioral preferences ("always suggest testing when I share code")

Project instructions: Context specific to one recurring workstream

• The specific task context
• The specific audience
• Reference information for that domain

Conversation: Context that's specific to one session

• The specific piece of work today
• Current status or recent updates
• The particular document or problem at hand

Getting this hierarchy right means you're only typing new context once. Memory and Projects carry the stable context; each conversation just needs the session-specific details.

Maintaining your Projects

Projects need light maintenance:

• When something fundamental changes (role, team, product direction), update the instructions
• If a Project feels like it's producing worse output than it used to, reread the instructions — they may have become stale
• Every month or two, delete Projects you're no longer using

The overhead is minimal; the time savings compound every week.