Teamday

Docs · guides

Setting Up Your Company Folders

Step-by-step recipes for organizing folders, agents, and scheduled work — an SEO folder, a development folder, a content hub, and a multi-agent team.

This page used to describe "Space" setup. Spaces no longer exist; the same recipes now use ordinary folders and organization-wide agents. The page address is unchanged so older links keep working.

Setting Up Your Company Folders

This guide gives step-by-step recipes for common setups. For the concepts behind them, see Folders and Files.

Every recipe follows the same pattern:

  1. Create a folder for the work.
  2. Create or install an agent. Agents belong to your organization and carry their own skills and MCP connections wherever they work.
  3. Store any credentials as organization secrets.
  4. Put reference material in the folder.
  5. Start a chat or mission with that folder as its working directory.

SEO Folder

An SEO analyst working from /marketing/seo with Ahrefs, Google Analytics, and Search Console access.

1. Create the folder

teamday files mkdir /marketing/seo

2. Create the SEO agent

teamday agents create \
  --name="Sarah" \
  --role="SEO Analyst" \
  --system-prompt="You are Sarah, an SEO specialist. Analyze search performance, find keyword opportunities, and provide actionable recommendations. Always cite data sources and use tables for comparisons." \
  --default-cwd=/marketing/seo

--default-cwd is the folder new chats with Sarah start in unless you pick another one.

3. Connect MCP servers to the agent

MCP connections belong to the agent, not to a folder:

teamday mcp setup ahrefs --token=<ahrefs-token> --agent=<sarah-id>
teamday mcp setup google-analytics --from=service-account.json --agent=<sarah-id>

4. Store credentials

teamday secrets put AHREFS_API_KEY "$AHREFS_API_KEY"
teamday secrets put GA_PROPERTY_ID "12345678"

5. Add context

Write a CLAUDE.md into the folder so every run starts with the same context:

teamday files write /marketing/seo/CLAUDE.md --from=seo-context.md

# SEO

Primary domain: example.com
Focus keywords: [your target keywords]
Competitors: competitor1.com, competitor2.com

## Reporting Schedule
- Weekly: keyword ranking changes, traffic trends
- Monthly: full SEO audit, competitor analysis

## Tools Available
- Ahrefs: backlinks, keywords, domain rating
- Google Analytics: traffic, user behavior
- Google Search Console: impressions, clicks, CTR

6. Start work

teamday chats new --agent-id=<sarah-id> --cwd=/marketing/seo

Development Folder

A code reviewer working on a connected repository.

1. Connect the repository

teamday repositories add --remote=https://github.com/your-org/your-repo.git
teamday repositories list

See Git Integration for where connected repositories appear in your file tree.

2. Create a code review agent

teamday agents create \
  --name="Code Reviewer" \
  --role="Senior Software Engineer" \
  --system-prompt="You are a senior engineer. Review code for quality, security, and maintainability. Check for OWASP top 10 vulnerabilities. Provide specific fixes with code examples."

3. Attach skills

teamday agents add-skill <reviewer-id> research-assistant code-reviewer

4. Store credentials

teamday secrets put GITHUB_TOKEN "$GITHUB_TOKEN"
teamday secrets put DATABASE_URL "$DATABASE_URL"

5. Add context

A CLAUDE.md at the repository root:

# Backend API

Tech stack: Node.js, Express, PostgreSQL, Prisma ORM
Deployment: Docker on AWS ECS
CI: GitHub Actions

## Coding Standards
- TypeScript strict mode
- Tests required for all new endpoints
- Use Prisma for all database operations
- Follow REST conventions (proper status codes, resource naming)

## Important Paths
- src/routes/ — API routes
- src/models/ — Prisma schema and models
- src/middleware/ — Auth, validation, error handling
- tests/ — Jest test files

6. Start work

Start the chat with the repository folder as its working directory:

teamday chats new --agent-id=<reviewer-id> --cwd=/engineering/your-repo

Content Hub

A content writer producing blog posts and images under /marketing/content.

1. Create the folders

teamday files mkdir /marketing/content
teamday files mkdir /marketing/content/images

2. Create the writer

teamday agents create \
  --name="Alex" \
  --role="Content Writer" \
  --system-prompt="You are Alex, a content writer for B2B SaaS. Write in a conversational but professional tone. Use short paragraphs, clear headers, and data-backed claims. Always generate a cover image for blog posts." \
  --default-cwd=/marketing/content

3. Add context

# Content

Brand voice: Professional but friendly. We explain complex topics simply.
Audience: Marketing managers and business owners.

## Content Types
- Blog posts (1500-2500 words)
- Case studies
- Product updates

## SEO Rules
- Primary keyword in title and first paragraph
- Meta description under 160 characters
- At least 3 internal links per post

## Image Generation
- Use landscape_16_9 for blog covers
- Style: clean, modern, abstract
- Save to images/

The MediaGeneration platform tool is available automatically. Generated images are saved relative to the working directory, so images/cover.png lands in /marketing/content/images/.

Multi-Agent Team

Several specialists working in one folder and handing work to each other.

1. Create the folder

teamday files mkdir /marketing
teamday files mkdir /marketing/reports
teamday files mkdir /marketing/content
teamday files mkdir /marketing/data

2. Create the specialists

# SEO Specialist
teamday agents create \
  --name="Sarah" \
  --role="SEO Analyst" \
  --system-prompt="You are Sarah, an SEO specialist. When asked about SEO, analyze data from Ahrefs. For non-SEO questions, suggest handing off to the appropriate team member."

# Content Writer
teamday agents create \
  --name="Alex" \
  --role="Content Writer" \
  --system-prompt="You are Alex, a content writer. Write blog posts and marketing copy. For SEO analysis, suggest handing off to Sarah."

# Data Analyst
teamday agents create \
  --name="Max" \
  --role="Data Analyst" \
  --system-prompt="You are Max, a data analyst. Query data, generate insights, and build reports. For content creation, suggest handing off to Alex."

All three are organization agents. Nothing needs to be added to the folder for them to work there; you choose the folder when you start a chat or mission.

3. Add handoff instructions

A CLAUDE.md in /marketing:

# Marketing Team

## Team Members
- Sarah: SEO analysis, keyword research, competitor analysis
- Alex: Blog posts, marketing copy, social media content
- Max: Data analysis, reporting, Google Analytics

## Handoff Protocol
When a request is outside your expertise:
1. Use the UICommand tool to call listAgents
2. Find the right specialist
3. Use switchAgent to hand off the conversation
4. Briefly explain to the user why you're handing off

## Shared Folders
- reports/ — Generated reports
- content/ — Blog posts and articles
- data/ — Analysis outputs

4. Schedule recurring work in the folder

teamday missions create \
  --title="Weekly marketing report" \
  --agent-id=<max-id> \
  --cwd=/marketing/reports \
  --schedule-cron="0 9 * * MON" \
  --schedule-timezone="Europe/Bratislava"

Automation with the CLI

Script a folder setup for repeatable environments:

#!/bin/bash
# setup-folder.sh

FOLDER="$1"
AGENT_ID="$2"

teamday files mkdir "$FOLDER"
teamday files mkdir "$FOLDER/reports"
teamday files write "$FOLDER/CLAUDE.md" --from=context.md

# Credentials are organization secrets, shared by every agent
teamday secrets put OPENAI_API_KEY "$OPENAI_API_KEY"
teamday secrets put GITHUB_TOKEN "$GITHUB_TOKEN"

# Start the first chat in the folder
teamday chats new --agent-id="$AGENT_ID" --cwd="$FOLDER"

echo "Folder $FOLDER ready"

chmod +x setup-folder.sh
./setup-folder.sh /projects/launch agent-abc123

Next Steps