HeyRon@partner $ ~load-module workspace

04 Workspace_

Your workspace is where your agent learns how you think. Structure it intentionally, and the agent can move with precision and care.

Slow Down First

Before organizing anything, ask your agent: What am I building here? What will I be doing most often? What does the agent need to find quickly?

Different projects need different shapes:

The structure you choose should reflect what you're trying to accomplish.

Machine-Readable vs. Human-Readable

Your agent needs to find things fast. You need to understand what's there when you look. These don't always align.

Example: Instead of nesting a project three levels deep (projects/active/legal/case-brief-2026.md), flatten it to the root with a prefix: p-legal-case-brief-2026.md. The agent can find it instantly. You still know what it is.

Simple Structure

Once you know what you're building, keep it simple:

workspace/
  p-project-name/
    drafts/
    final/
    archive/
  README.md (describes what's in this project)

Naming Conventions

What the Agent Can Access

Everything in the workspace folder. But be intentional—don't clutter it with files the agent doesn't need to know about.

Keep a README.md in each project with a description of what lives there. It's how the agent learns your thinking.

See How Others Organize

Want to see how other den members are organizing their workspaces? Check the tips page or go to the discord server for real-world examples and FAQ.