Claude Context Mastery

Smart Development Workflow Guide for Multi-Project Developers

Leverage Claude's Built-in Features for Maximum Productivity

What Makes Claude Different

Claude Projects

Persistent Context: Create dedicated workspaces for each application

  • Add files, schemas, and documentation
  • Custom instructions per project
  • All chats inherit project knowledge
Recommended
Memory System

Automatic Context: Claude remembers across conversations

  • No manual copy-paste needed
  • Tell Claude what to remember
  • Persistent across all chats
Always Active
Chat Search

Instant Recall: Find past conversations instantly

  • Ask Claude to search past chats
  • Retrieve specific discussions
  • No scrolling required
Built-in Tool

Three Methods to Manage Context

Choose the approach that fits your workflow. Method 1 (Projects) is recommended for your multi-app development.

Method 1: Claude Projects RECOMMENDED

Create a dedicated project for each major application. Best for long-term, complex development.

How to Set Up
  1. Create a New Project: Click "Projects" in the sidebar → "New Project"
  2. Name It Clearly: E.g., "Aimoruk Pharmacy System", "drsergio.tl Medical Portal"
  3. Add Project Knowledge:
    • Upload your database schema files (.sql)
    • Add core PHP files (config.php, functions.php)
    • Include API documentation
  4. Set Custom Instructions: Define your coding standards, preferences, and project-specific rules
Example Custom Instructions for "Aimoruk" Project:
Project: Aimoruk Pharmacy Delivery Platform Tech Stack: PHP, MySQL, Bootstrap 5, JavaScript Database: aimoruk_db Key Roles: - Patients (order medications) - Pharmacies (fulfill orders) - Riders (deliver orders) - Admins (manage system) Coding Standards: - Use prepared statements for all SQL queries - Mobile-first responsive design - Multilingual support (Portuguese, Tetum, English) - Follow PHP PSR-12 coding standards Current Focus: Real-time rider tracking and order status updates
When to Use Projects
  • Multiple related apps (Aimoruk, drsergio.tl, AIFAESA tools)
  • Long-term development spanning weeks or months
  • Complex database schemas that need to be referenced frequently
  • Team collaboration (share project with colleagues)
Pro Tip: Every conversation in a project automatically has access to all project files and instructions. No need to repeat yourself!

Method 2: Claude Memory System

Let Claude remember key information across all conversations. Best for general preferences and frequently used facts.

How to Use Memory

Simply tell Claude what to remember:

Example Commands:
  • "Please remember that I work for AIFAESA in Timor-Leste"
  • "Remember that the Aimoruk database uses the following schema: [paste schema]"
  • "Remember that I prefer PHP over Python for web development"
  • "Remember that all my projects need multilingual support (Portuguese, Tetum, English)"
Managing Your Memory
  • Update: "Update your memory: I now work on the ID Registration system"
  • Remove: "Please forget about the lawyer website project"
  • Check: "What do you remember about my projects?"
What to Store in Memory
Good for Memory:
  • Your role and organization
  • Preferred tech stack
  • Coding standards
  • Language preferences
  • Active projects list
Not Good for Memory:
  • Full source code
  • Detailed database schemas
  • API keys or passwords
  • Frequently changing info
  • Project-specific details
Note: Memory works across ALL chats, not just within projects. Use it for personal preferences, not project-specific code.

Method 3: Smart Context Injection (For Quick Tasks)

When you need to start fresh but want specific past context. Best for debugging or revisiting old features.

The Claude Way

Instead of manually copying context, let Claude do the work:

Smart Search Prompts:
  1. "Search our past chats about the Aimoruk database schema"
  2. "Find the conversation where we discussed the rider tracking feature"
  3. "What did we decide about user authentication in drsergio.tl?"
  4. "Show me the last time we worked on the AIFAESA inspection form"

Claude will automatically search past conversations and bring relevant context into the current chat.

When You Need a Clean Handover

If you want to create a formal technical document:

Handover Document Prompt:
"Please create a Technical Handover Document for the [Project Name] and save it as a markdown file. Include: 1. Project Overview (purpose, tech stack, current status) 2. Database Schema (tables, relationships, key indexes) 3. Core Files (list with brief descriptions) 4. Completed Features (what's 100% done) 5. Current Task (what we're working on now) 6. Known Issues (bugs or technical debt) 7. Next Steps (immediate priorities) Format this as a downloadable .md file I can add to the project documentation."

Claude will create an actual file you can download and save to your project folder.

When to Use This Method: One-off debugging sessions, contractor handovers, or when you need formal documentation. For ongoing work, use Projects instead.

Recommended Workflow for Your Projects

Here's how to organize your specific development work:

Project Recommended Method What to Include Why This Approach
Aimoruk (Pharmacy) Project Database schema, role definitions, API endpoints, rider tracking logic Complex multi-role system with ongoing development
drsergio.tl (Medical) Project Patient data structure, vital signs schema, HIPAA compliance notes, prescription format Medical apps require high precision and regulatory compliance
AIFAESA Tools Project Inspection forms, document management, government standards, multilingual templates Multiple related tools under one government system
ID Registration Memory + Search Card template format, batch processing logic Smaller scope, may not need full project
Lawyer Website Memory + Search Document vault structure, client portal requirements Simpler structure, less frequent updates

Quick Setup Guide: Your First Project

Let's set up your Aimoruk project as an example:

1 Create the Project
  • Click "Projects" in Claude sidebar
  • Click "Create Project"
  • Name: Aimoruk Pharmacy System
  • Description: "Pharmacy delivery platform connecting patients, pharmacies, and riders in Timor-Leste"
2 Add Knowledge Files

Upload these files to the project:

  • aimoruk_schema.sql - Database structure
  • config.php - Database connection template
  • functions.php - Shared functions
  • README.md - Project overview
3 Set Custom Instructions

Add to "Project Instructions":

  • Tech stack (PHP, MySQL, Bootstrap 5)
  • Coding standards (prepared statements, mobile-first)
  • Language requirements (Portuguese/Tetum/English)
  • Current focus area
4 Start Coding
  • All new chats in this project automatically have context
  • No need to repeat database schema
  • Claude knows your coding standards
  • Focus on the feature, not context setup

Best Practices & Pro Tips

Do This
  • Create one project per major application
  • Keep project files updated
  • Use clear, descriptive project names
  • Add schema files and core configs
  • Update custom instructions as project evolves
Avoid This
  • Don't mix multiple apps in one project
  • Don't store passwords or API keys in project files
  • Don't upload entire codebases (just core files)
  • Don't forget to update docs after major changes
  • Don't use vague project names
Pro Tips
  • Use projects for complex apps, memory for preferences
  • Ask Claude to search past chats when debugging
  • Create handover docs before major refactors
  • Pin active project chats for quick access
  • Archive old chats but keep project files

Old Way vs. Claude Way

The Manual Way (Other AIs)
  1. Chat gets slow and laggy
  2. Manually scroll up to find code
  3. Copy-paste code into text editor
  4. Start new chat
  5. Paste entire context summary
  6. Hope you didn't miss anything
  7. Repeat every few hours

Result: Time-consuming, error-prone, frustrating

The Claude Way
  1. Set up project once with files
  2. Every chat has full context automatically
  3. Ask Claude to search past chats if needed
  4. Tell Claude what to remember
  5. Focus on building, not context management
  6. Download files directly from Claude
  7. Never lose context between sessions

Result: Fast, reliable, productive

Common Scenarios & Solutions

Solution: Create separate projects for each app. Switch projects in the sidebar. Each project maintains its own context, so you never mix up database schemas or feature logic.

Solution: In a new chat, say: "Search our past conversations about [feature name] and help me debug [issue]". Claude will find the relevant past discussion and bring it into context.

Solution: Update the schema file in your project knowledge. Delete the old version, upload the new one. All future chats in that project will use the updated schema automatically.

Solution: Use the handover document prompt (Method 3). Claude creates a comprehensive technical document you can give to the contractor. Include project files, database schema, and current status.

Solution: Use Memory (Method 2) to store your general preferences: "Remember that I always use prepared statements, prefer Bootstrap 5, and need multilingual support". This applies across all projects and chats.

Your Next Steps

Action Plan for This Week:
Day 1-2: Setup Projects
  1. Create project for Aimoruk
  2. Create project for drsergio.tl
  3. Create project for AIFAESA tools
  4. Upload core files to each project
Day 3-4: Configure Memory
  1. Tell Claude about your role at AIFAESA
  2. Store your coding preferences
  3. Add language requirements (PT/Tetum/EN)
  4. Note your active projects
Day 5: Test & Refine
  1. Start a new chat in each project
  2. Verify Claude has the right context
  3. Test chat search for past conversations
  4. Adjust custom instructions as needed
Goal: By the end of the week, you should be able to jump into any project and start coding immediately without repeating context. Your development speed will increase significantly!