openclaw-workspace

Summary

Daniel Ball's OpenClaw workspace for configuring, customizing, and managing AI assistant behavior and related projects. This workspace organizes core files for assistant identity, memory, tools, and project context to streamline assistant workflows and ensure continuity across sessions.

Included Assets

• AGENTS.md: Workspace onboarding, daily workflow instructions, and session guidance.
• SOUL.md: Defines the assistant's core principles, personality, and boundaries.
• MEMORY.md: Long-term memory file for curated facts, personal context, and project history.
• TOOLS.md: Local environment notes, credentials, tool settings, and deployment specifics.
• codegrind/ and convertfree/: Project directories with Node.js dependencies (including Playwright for browser automation and fsevents for file watching on macOS).
  • Each includes relevant package.json and README.md files for dependencies.

How to Use

1. Starting a Session:

   • Read SOUL.md to understand the assistant's identity and behavioral guidelines.
   • Review AGENTS.md for the standard session workflow.
   • Check MEMORY.md (main session only) or the latest memory/YYYY-MM-DD.md files for recent continuity/context.

2. Project Context:

   • Each project (like codegrind and convertfree) manages its package dependencies (e.g., Playwright).
   • Use project-level package.json files for dependency management and configuration.

3. Updating Context:

   • Document new facts, context, or decisions in the corresponding memory/YYYY-MM-DD.md files.
   • Curate essential long-term knowledge into MEMORY.md (main session only).

4. Environment Notes:

   • Add local credentials, environment-specific configs, and operational notes to TOOLS.md.

Notes

• Privacy & Security: MEMORY.md contains sensitive, high-context information; load only in direct human sessions, not shared contexts.
• Session Continuity: The assistant wakes up stateless; rely on memory files for persistence.
• Dependencies: Node modules (Playwright, fsevents) are project-specific and managed in their respective directories.
• Edit With Care: Any changes to assistant-defining files (SOUL.md, AGENTS.md) should be communicated to the workspace owner.

This workspace enables robust, opinionated assistant configuration while maintaining clear boundaries and continuity for trusted, high-context automation and interaction.