> ## Documentation Index
> Fetch the complete documentation index at: https://palette.team/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Structure shared AI workspaces in Palette Desktop

> A folder is how you give an agent context. A clear, shallow structure named for the work helps agents and teammates find things fast in every session.

A folder is how you give an agent context, so the way you lay one out matters. A clear structure helps both your team and your agent find things without hunting.

## Start with the files that keep it current

The most valuable part of a workspace is a small set of files that preserve how the work is organized. Add the ones your team will maintain:

* [**CLAUDE.md and AGENTS.md**](/docs/desktop/claude-md-and-agents-md) at the root, so every agent knows who you are and how the workspace is organized.
* **A [README](/docs/desktop/readme-files) where a folder needs explanation**, then link it from your instructions or prompt when an agent should read it.
* [**lessons.md**](/docs/desktop/lessons-md) for durable corrections you want agents to consult.
* [**log.md**](/docs/desktop/log-md) for decisions and changes the team may need to revisit.

These files are not automatically read or updated because of their names. Link the important ones from CLAUDE.md or AGENTS.md, and ask the agent to update them when the work changes.

## Principles

* **Name folders for the work, not the tool.** Prefer `accounts/`, `campaigns/`, `hiring/` over `docs/` or `misc/`.
* **Keep it shallow.** A few clear top-level folders beat deep nesting.
* **One topic per folder.** If a folder holds two unrelated things, split it.
* **Let each folder explain itself.** Add a short [README](/docs/desktop/readme-files).

## A starting structure

Here is a workspace for a GTM team. The folders are named for the work, it stays shallow, and each folder has a README.

```text theme={null}
gtm-workspace/
├── CLAUDE.md              # who you are and how this workspace is organized
├── accounts/              # one folder per customer
├── campaigns/             # work in flight
├── competitors/           # one profile per competitor
├── playbooks/             # how you do the recurring work
└── README.md              # what this workspace is
```

## Starting from Marketplace

You do not have to build this by hand. Marketplace can add a ready-made folder system or workflow, then adapt it to your work. See [Install from Marketplace](/docs/desktop/marketplace) for the steps.

## Related

* [Working with CLAUDE.md and AGENTS.md](/docs/desktop/claude-md-and-agents-md), the file at the root of the workspace
* [Working with README and index files](/docs/desktop/readme-files), folder-level front doors
* [Marketplace](/docs/desktop/marketplace), ready-made folder systems and workflows