Brand Configuration¶

Your brand context is the foundation of content quality. This guide covers how to configure and optimize it.

Brand Context Components¶

Voice Profile¶

The voice profile defines how your brand communicates.

Tone¶

Overall emotional quality of communication:

{
  "voice": {
    "tone": "professional yet approachable, technical when needed but never condescending"
  }
}

Examples by industry:

Industry	Tone Example
B2B SaaS	"Professional, helpful, and direct"
Consumer Tech	"Friendly, enthusiastic, and clear"
Finance	"Trustworthy, precise, and accessible"
Healthcare	"Compassionate, authoritative, and reassuring"

Personality Traits¶

Character attributes (choose 3-5):

{
  "voice": {
    "personality": [
      "knowledgeable",
      "helpful",
      "innovative",
      "direct"
    ]
  }
}

Writing Style¶

Specific guidelines for copy:

{
  "voice": {
    "writing_style": "Clear, concise sentences. Active voice preferred. Technical terms okay but always explain acronyms on first use. Address the reader as 'you'. Avoid jargon when simpler words work."
  }
}

Formality¶

Communication register:

Level	Example
`formal`	"We are pleased to announce..."
`business_casual`	"Excited to share that..."
`casual`	"Just shipped something cool..."

Visual Identity¶

Control image and visual generation:

{
  "visual_identity": {
    "primary_color": "#7c3aed",
    "secondary_color": "#f59e0b",
    "accent_colors": ["#10b981"],
    "image_style": "Modern, clean, tech-focused. Geometric shapes. Bold colors.",
    "photo_style": "Authentic workplace settings. Diverse teams. Natural lighting.",
    "illustration_style": "Abstract geometric. Minimal detail. Brand colors only.",
    "avoid_in_images": [
      "Stock photo clichés",
      "Handshakes",
      "Generic office scenes"
    ]
  }
}

Content Guidelines¶

Topics¶

What to cover:

{
  "content_guidelines": {
    "topics": [
      "API design best practices",
      "Developer productivity",
      "Engineering culture",
      "Technical tutorials",
      "Industry trends"
    ],
    "topic_weights": {
      "API design best practices": 0.3,
      "Developer productivity": 0.25,
      "Technical tutorials": 0.25,
      "Industry trends": 0.2
    }
  }
}

Excluded Topics¶

What to never mention:

{
  "content_guidelines": {
    "excluded_topics": [
      "Politics",
      "Religion",
      "Competitor names",
      "Pricing details",
      "Unreleased features",
      "Customer-specific information",
      "Legal matters"
    ]
  }
}

Hashtags¶

Platform-specific hashtag strategy:

{
  "content_guidelines": {
    "hashtag_preferences": {
      "always_use": ["#YourBrand"],
      "platform_specific": {
        "twitter": ["#DevTools", "#API"],
        "linkedin": ["#Engineering", "#TechLeadership"],
        "instagram": ["#coding", "#developer"]
      },
      "never_use": ["#FollowForFollow"],
      "max_per_post": {
        "twitter": 3,
        "linkedin": 5,
        "instagram": 20
      }
    }
  }
}

CTAs¶

Call-to-action style:

{
  "content_guidelines": {
    "cta_style": "soft sell, value-first",
    "preferred_ctas": [
      "Learn more →",
      "See how →",
      "Try it free"
    ],
    "avoid_ctas": [
      "BUY NOW",
      "Limited time offer",
      "Don't miss out"
    ]
  }
}

Examples¶

Examples dramatically improve content quality.

Good Examples¶

{
  "examples": {
    "good_posts": [
      {
        "platform": "twitter",
        "text": "We analyzed 10,000 API designs. The ones developers loved had one thing in common: predictable error messages.\n\nHere's the pattern that works:",
        "why_good": "Data-driven hook, specific insight, promises value"
      },
      {
        "platform": "linkedin",
        "text": "Last month, we shipped a feature that reduced API integration time from 2 weeks to 2 days.\n\nWe didn't add anything new. We removed 6 endpoints.\n\nSometimes the best feature is less complexity.",
        "why_good": "Specific metrics, counterintuitive insight, clear lesson"
      }
    ]
  }
}

Bad Examples¶

{
  "examples": {
    "bad_posts": [
      {
        "platform": "twitter",
        "text": "Check out our amazing new API! It's the best! 🚀🔥💯",
        "why_bad": "Generic, no value, excessive emoji, self-promotional"
      },
      {
        "platform": "linkedin",
        "text": "We're thrilled to announce our revolutionary platform that will change the way you think about APIs forever.",
        "why_bad": "Buzzwords, vague claims, no specific value"
      }
    ]
  }
}

Audience Definition¶

{
  "audience": {
    "primary": {
      "role": "Software Engineers",
      "seniority": "Mid to Senior",
      "company_size": "Startup to Enterprise",
      "interests": ["APIs", "Developer Tools", "Productivity"],
      "pain_points": [
        "Integration complexity",
        "Poor documentation",
        "Breaking changes"
      ]
    },
    "secondary": {
      "role": "Engineering Managers",
      "interests": ["Team productivity", "Technical decisions"]
    }
  }
}

Competitor Context¶

{
  "competitors": [
    {
      "name": "Competitor A",
      "positioning": "We offer better developer experience",
      "differentiators": [
        "Simpler onboarding",
        "Better documentation",
        "More responsive support"
      ],
      "never_mention": true
    }
  ]
}

Iterating on Brand Context¶

Monitor Quality¶

Review generated content regularly:

# Get recent content with confidence scores
curl "https://api.amp.dev/v1/content?sort=-created_at&limit=20" \
  -H "Authorization: Bearer $AMP_API_KEY"

Identify Patterns¶

Look for: - Recurring quality issues - Off-brand language - Missing topics - Overused phrases

Make Targeted Updates¶

curl -X PUT https://api.amp.dev/v1/brand/{id} \
  -H "Authorization: Bearer $AMP_API_KEY" \
  -d '{
    "voice": {
      "writing_style": "Added: Avoid starting sentences with \"Just\""
    }
  }'

Add Examples¶

When you see great content:

curl -X PUT https://api.amp.dev/v1/brand/{id} \
  -H "Authorization: Bearer $AMP_API_KEY" \
  -d '{
    "examples": {
      "good_posts": [
        {
          "platform": "twitter",
          "text": "Actual high-performing post from your account",
          "why_good": "Why it worked"
        }
      ]
    }
  }'

Testing Changes¶

Test brand context changes before applying globally:

Create a test mission with short duration
Enable manual approval
Review generated content
Iterate on brand context
Apply to production missions

Brand Context Templates¶

B2B SaaS¶

{
  "voice": {
    "tone": "professional yet approachable",
    "personality": ["knowledgeable", "helpful", "innovative"],
    "formality": "business_casual"
  },
  "content_guidelines": {
    "cta_style": "soft sell, value-first"
  }
}

Developer Tools¶

{
  "voice": {
    "tone": "technical but accessible",
    "personality": ["expert", "pragmatic", "community-focused"],
    "formality": "casual"
  },
  "content_guidelines": {
    "topics": ["tutorials", "best practices", "community"]
  }
}

Consumer Brand¶

{
  "voice": {
    "tone": "friendly and enthusiastic",
    "personality": ["fun", "relatable", "helpful"],
    "formality": "casual"
  }
}