AI Workspace
Where company context, working materials, instructions, and local configuration belong in an ACT Playbook AI workspace.
An ACT Playbook AI workspace keeps the files your team and its AI agent need in one private repository. Use the folders below consistently so people and agents can find the right context and working materials.
wording-guidelines.md
CLAUDE.md or AGENTS.md
MEMORY.md
.env.local
| Area | What belongs here |
|---|---|
context | Company knowledge that should guide work across the repository, such as voices, writing rules, and competitive material. |
context/voices | Voice files for the company and individual team members. |
context/competition | Competitive research and comparison material. |
workspace | Work created for customers, prospects, campaigns, social content, websites, research, whitepapers, sequences, and sales materials. |
workspace/company-research | Research about companies that informs customer and prospect work. |
workspace/customers | Customer-specific working material. |
workspace/prospects | Prospect-specific research and material. |
workspace/sales-campaigns | Sales-campaign plans, sequences, and supporting assets. |
workspace/social-content | LinkedIn posts, ads, blog posts, and other thought-leadership material. |
workspace/website | Website plans, copy, audits, and generated website material. |
.agents/skills | Workflows created specifically for this repository. |
CLAUDE.md or AGENTS.md | Standing instructions for the AI agent. |
MEMORY.md | Corrections, decisions, and working preferences that should remain available in future conversations. |
.env.local | Local-only credentials for selected workflows, such as API keys. Git ignores this file, so its contents remain on your computer and outside commits. |
Keep shared work in the repository so the team can review it. Keep secrets in .env.local or the provider's credential store. ACT Playbook MCP OAuth credentials belong in the agent's credential store, not in repository files.