Content is user-generated and unverified.

🧠 Claude Advanced Techniques - Universal Best Practices

Core Problem-Solving Workflow

Essential sequence for any complex task:

  1. Present the problem with clear context and constraints
  2. Ask Claude to generate a comprehensive plan
  3. Request 3 best approach options and iteratively edit the plan
  4. Layer in extended thinking (see section below)

🔄 Extended Thinking - Critical Performance Booster

Key insight: Extended thinking works best when Claude already has context - it's not just about thinking, it's about contextual thinking.

When to Use Extended Thinking:

  • Complex analysis tasks (business strategy, research, policy analysis)
  • Creative projects (writing, design, content strategy)
  • Problem-solving scenarios (troubleshooting, optimization, planning)
  • Decision-making processes (vendor selection, strategic planning)
  • Learning and education (curriculum design, training materials)
  • After Claude has ingested relevant documents/context
  • When you need deeper analysis beyond surface-level responses

Why It Works:

  • Internal benchmarks show dramatic improvement: context → think → execute = significantly better results
  • Claude performs better reasoning when it can build on existing understanding
  • Not just "think harder" - it's "think with full context"
  • Applies across domains: coding, writing, analysis, strategy, research

Optimal Task Execution Workflow

Proven sequence for any complex deliverable:

For Development:

  1. Read files first - understand codebase architecture
  2. Think and brainstorm - use extended thinking
  3. Then build solution - results are measurably better

For Analysis/Research:

  1. Ingest source materials - documents, data, requirements
  2. Think and synthesize - use extended thinking for deeper insights
  3. Then produce analysis - recommendations, reports, findings

For Creative Work:

  1. Understand context - brand guidelines, audience, objectives
  2. Think and ideate - use extended thinking for creative exploration
  3. Then create content - copy, designs, strategies

For Strategic Planning:

  1. Gather inputs - market data, constraints, stakeholder needs
  2. Think and model - use extended thinking for scenario planning
  3. Then develop strategy - roadmaps, recommendations, action plans

This sequence consistently outperforms direct task requests across all domains in internal evaluations

Claude Memory System (.md files)

Project-Level Memory:

  • CLAUDE.MD - Primary team memory file
    • Location: Root of your project/repository
    • Contents: Frequently used templates and frameworks, brand guidelines and style preferences, standard operating procedures, key stakeholder information, major project decisions and rationale
    • Check into version control - share with entire team
    • Auto-read: Claude automatically reads this when working in the project

Personal Memory:

  • claude.local.md - Individual preferences
    • Location: Root of your project/repository (alongside CLAUDE.MD)
    • Contents: Personal shortcuts and workflow preferences, individual writing style notes, personal project context
    • Never check into version control - add to .gitignore
    • Auto-read: Claude reads this for your personal context

Global Memory:

  • claude.global.md - Cross-project instructions
    • Location: Your home directory (~/claude.global.md)
    • Contents: Company-wide standards and preferences, universal templates, cross-project shared instructions
    • Scope: Applies to all Claude instances across all projects
    • Auto-read: Claude reads this regardless of which project you're working on

Nested Directory Memory:

  • claude.md files in any subdirectory
    • Location: Any nested folder within your project structure
    • Contents: Directory-specific context, module-specific instructions, team-specific guidelines
    • Auto-discovery: Claude automatically finds and reads these from any directory level
    • Use cases: Different teams, project phases, or specialized workflows

How to Create and Save Claude Memory Files

Step-by-Step Setup:

1. For Global Memory (claude.global.md):

  • Where: Your user home folder
  • Windows: C:\Users\[YourUsername]\claude.global.md
  • Mac: /Users/[YourUsername]/claude.global.md
  • How to create:
    • Open any text editor (Notepad, VS Code, TextEdit)
    • Create new file, save as claude.global.md
    • Put in your home folder (not Desktop, not Downloads)

2. For Project Memory (CLAUDE.MD):

  • Where: Root folder of your project/work directory
  • Example locations:
    • C:\Users\[YourUsername]\Documents\MyProject\CLAUDE.MD
    • C:\Users\[YourUsername]\Desktop\WorkProject\CLAUDE.MD
    • Inside your VS Code workspace folder
  • How to create:
    • Navigate to your project folder
    • Create new file named CLAUDE.MD (all caps)
    • Save directly in that project folder

3. For Personal Memory (claude.local.md):

  • Where: Same folder as your CLAUDE.MD
  • How to create: Same as above, but name it claude.local.md
  • Important: Add to .gitignore if using version control

Creating the Files:

  1. Open any text editor (Notepad, VS Code, Sublime, etc.)
  2. Create new file
  3. Save with exact filename (case-sensitive):
    • claude.global.md
    • CLAUDE.MD
    • claude.local.md
  4. Save in correct location (see above)
  5. Add content using markdown format

File Structure Example:

C:\Users\YourName\
├── claude.global.md                 # Global instructions
└── Documents\
    └── MyProject\
        ├── CLAUDE.MD                # Main project memory (shared)
        ├── claude.local.md          # Personal memory (not shared)
        ├── frontend\
        │   └── claude.md            # Frontend-specific instructions
        └── backend\
            └── claude.md            # Backend-specific instructions

Memory Mode (# Command)

  • Use # to enter memory mode
  • Command: "Hey Claude, memorize this [information]"
  • Claude automatically incorporates into appropriate memory file
  • Build persistent knowledge base for:
    • Projects: requirements, decisions, stakeholder feedback
    • Processes: workflows, templates, best practices
    • Preferences: style guides, communication preferences
    • Context: organizational knowledge, domain expertise

Universal Applications

These techniques work across all domains:

  • Software Development - architecture, coding, debugging
  • Content Creation - writing, marketing, documentation
  • Business Analysis - strategy, operations, market research
  • Design & UX - user research, prototyping, design systems
  • Project Management - planning, risk assessment, stakeholder communication
  • Research & Education - curriculum design, knowledge synthesis, training materials

Roadmap Preview

Next version improvements:

  • Native tool integration across all work environments
  • Enhanced handling of routine tasks without manual setup
  • Streamlined workflows for common business and creative patterns
  • Cross-domain memory sharing and context preservation

These techniques show measurable performance improvements in internal benchmarks across context understanding, reasoning quality, and task execution - regardless of domain or use case

Content is user-generated and unverified.
    Claude Advanced Techniques - Universal Best Practices | Claude