OpenClaw Workspace Structure and Self-Improvement Approach from Longtime User

Core Workspace Structure

The user's main workspace is located at C:\Users\sandm\clawd with this simplified structure:

clawd/
├─ AGENTS.md
├─ SOUL.md
├─ USER.md
├─ MEMORY.md
├─ HEARTBEAT.md
├─ TOOLS.md
├─ SECURITY.md
├─ memory/
├─ skills/
├─ tools/
├─ projects/
├─ docs/
├─ logs/
├─ drafts/
├─ reports/
├─ research/
├─ secrets/
└─ agents/

Critical Markdown Files

These markdown files serve distinct, non-overlapping purposes:

• SOUL.md - voice, posture, and behavioral style
• AGENTS.md - startup behavior, memory rules, and operational conventions
• USER.md - the human user's goals, preferences, and context
• MEMORY.md - lightweight index instead of giant memory dump
• HEARTBEAT.md - recurring checks and proactive behavior
• TOOLS.md - local tool references, integrations, and real-world usage notes
• SECURITY.md - hard rules and outbound caution

Key Implementation Lessons

Self-Improvement Approach

The most significant insight was that OpenClaw becomes dramatically more effective when the agent is allowed to improve its own environment through:

• Updating its own internal documentation
• Editing its own operating files
• Refining prompt and config structure over time
• Building custom tools for itself
• Writing scripts that make future work easier
• Documenting lessons so mistakes don't repeat

This transforms the workspace from static prompt scaffolding into a living operating system the agent helps maintain.

Memory Management

Instead of one giant memory file, the user implemented:

• MEMORY.md as an index
• memory/people/ for person-specific context
• memory/projects/ for project-specific context
• memory/decisions/ for important decisions
• Daily logs as raw journals

The system loads only the index initially and drills down when needed.

Skills Development

Valuable skills are tied to real recurring work like research, documentation, calendar, email, Notion, project workflows, memory access, and development support. The test for whether a skill should exist: "Would I notice if this skill disappeared tomorrow?" If no, it shouldn't be a skill yet.