Customizing Personas

You can edit persona files directly from the Synthcore dashboard. Changes are pushed to your project's VM immediately and take effect on the next agent cycle.

Editing in the dashboard

1. Navigate to your project's Personas tab.
2. Select a file from the file tree (SOUL.md, AGENTS.md, or COORDINATION.md).
3. Edit the content in the built-in editor.
4. Click Save to push changes to the VM.

The editor supports Markdown syntax highlighting and a side-by-side preview.

Editing SOUL.md

Here's an example SOUL.md for a Next.js SaaS project:

# Project: MyApp

## Description
A B2B SaaS platform for project management built with Next.js 15,
TypeScript, Tailwind CSS, and Supabase.

## Tech Stack
- Framework: Next.js 15 (App Router)
- Language: TypeScript (strict mode)
- Styling: Tailwind CSS 4 + shadcn/ui
- Database: Supabase PostgreSQL
- Auth: Supabase Auth

## Conventions
- Commit messages: conventional commits (feat:, fix:, chore:)
- Branch naming: feature/*, bugfix/*, chore/*
- File naming: kebab-case for files, PascalCase for components

## Current Priorities
1. Complete user onboarding flow
2. Add Stripe billing integration
3. Write integration tests for API routes

Editing AGENTS.md

Control individual agent behavior:

# Alex (Backend)

## Boundaries
- CAN modify: lib/, app/api/, supabase/
- CANNOT modify: app/(marketing)/, components/ui/
- CANNOT delete: migration files

## Schedule
- Active hours: 24/7

# Pixel (Frontend)

## Boundaries
- CAN modify: app/(marketing)/, components/, styles/
- CANNOT modify: lib/, app/api/

Editing COORDINATION.md

Define how agents work together:

# File Ownership
- Alex: lib/, app/api/, database/
- Pixel: components/, app/(marketing)/, styles/
- Echo: tests/, __tests__/
- Scout: docs/, research/

# Escalation Protocol
If an agent encounters a blocking issue:
1. Log the issue with severity "warning"
2. Skip the task and move to the next item
3. Notify the project owner via Telegram

# Merge Rules
- Agents must pull before pushing
- If merge conflicts occur, abandon the commit and log a warning
- Never force push

Version history

Every persona edit creates a version. You can view and restore previous versions from the version dropdown in the Personas tab.

Tips for effective personas

• Be specific — The more detail you provide about conventions and priorities, the better agents perform.
• Update regularly — As your project evolves, update SOUL.md to reflect new priorities.
• Set clear boundaries — Prevent agents from modifying files they shouldn't touch.
• Start with defaults — The default persona files work well for most projects. Customize incrementally.