SYNTER / DEVDOCUMENTATION

Run and adapt

Eight real Synter workflows

Lead with the installed slash command. Add a concise brief after it; use supplemental prompts only when you need extra output constraints.

Quickstart

/synter:quickstart Verify my access, list connected organizations and account IDs, then recommend a read-only first action.

Connect

/synter:connect Show current connection state for [organization]. I need [platform]. After I complete connection, verify the exact account ID; do not change campaigns.

Audience

/synter:audience Draft an audience for [ICP] in [geos], excluding [groups]. Use [approved data]. Return size/match risks and a reviewable activation plan. Do not sync until I approve.

Creative

/synter:creative Draft three [format] concepts for [platform/audience/outcome] using only [proof] and [brand rules]. Return policy risks and test rationale. Do not attach to a live campaign.

Launch

/synter:launch Draft a campaign from this brief: [outcome, platforms, accounts, audience/geos, budget/target, offer/URL, evidence, tracking]. Run preflight and stop for approval before creating or enabling anything.

Optimize

/synter:optimize Analyze [period/accounts] against [CPA/ROAS target]. State minimum-data thresholds and recommend exact moves with before/after budgets. Do not pause or change spend without my explicit approval.

Report

/synter:report Build a [weekly/monthly] report for [accounts]. Reconcile platform claims with analytics, flag tracking gaps, and separate observed data from recommendations. Read-only.

Help

/synter:help I want to [goal]. Recommend the right workflow and list the information and approvals it needs.
Prompts do not grant blanket authorityReplace placeholders, verify organization/account IDs, and keep a clear authority clause. Never include API keys or provider secrets.