Platform Showcase

Multi-Platform Content Showcase

Process

1. Ingest source content -- receive the primary content piece (video, article, image, thread)
2. Identify target platforms -- determine which of the 8 platforms to adapt for
3. Load platform configs -- pull algorithm weights, content specs, and winning formulas from platform_master_config.json
4. Adapt per platform -- transform content to match each platform's format, tone, and algorithm priorities
5. Apply winning formula -- structure each adaptation using the platform's highest-performing template
6. Schedule via waterfall -- stagger publishing per the cross-posting cascade order and timing
7. Generate platform metadata -- hashtags, captions, descriptions, tags, thumbnails per platform (grounded pipeline — see Visual generation below)

Supported Platforms

Waterfall Cross-Posting Strategy

Cascade Order

YouTube (primary) --> LinkedIn --> Instagram --> Facebook --> X (Twitter) --> TikTok --> Pinterest --> Reddit

Timing Rules

• Delay between platforms: 30 minutes
• Cascade delay from primary: 2 hours
• Each platform publishes at its own optimal time window
• Adaptation level: high (full rewrite per platform, not copy-paste)

Adaptation Levels

• High: Full content rewrite matching platform voice, format, and algorithm priorities
• Medium: Structural changes with shared core message
• Low: Minor formatting adjustments (reserved for same-category platforms)

Content Adaptation Rules

YouTube (Source/Primary)

• Long-form: Hook (0-15s) > Problem (15-60s) > Solution (60-80%) > CTA (final 20s)
• Shorts: Extract most compelling 15-60s segment from long-form
• Thumbnail: custom, high contrast, readable text
• Description: timestamps, keywords, links
• Tags: 10-15 relevant keywords

Instagram

• Reels: Re-edit video to 15-30s, vertical 9:16, trending audio
• Carousel: Extract key points into 5-10 swipeable slides
• Caption: storytelling hook, 5-10 hashtags (trending + niche mix)
• Visual hooks: movement or surprise in first 3 seconds

TikTok

• Re-cut to 15-60s, fast pacing with scene changes every 2-3s
• Text overlay for silent viewing
• Trending sound integration within 24-48 hours
• Hashtags: #fyp #foryou + 3-5 niche tags
• Duet/stitch hooks for engagement

X (Twitter)

• Distill core message to 71-100 characters for single tweet
• Thread version: 5-15 tweets with hook > narrative > conclusion
• Media every 2-3 tweets in threads
• 1-2 hashtags maximum
• Controversial or bold take angle for engagement

Facebook

• Video: re-edit to 1-3 min, square or 4:5 aspect ratio, captions required
• Post: personal story angle with community question
• Images: minimal text overlay (<20% of image area)
• Group cross-posting with value-first approach

LinkedIn

• Long-form post: 1300+ characters, professional tone, line breaks every 1-2 sentences
• Data-driven or insight angle from source content
• 3-5 hashtags at end
• Industry insight or professional story template
• Content pillars: 40% expertise, 25% personal, 20% company, 15% engagement

Pinterest

• Create 2:3 vertical pin (1000x1500) with clear title and step visual
• Keyword-rich title (100 chars) and description (500 chars)
• Board placement with searchable names
• Alt text for accessibility
• Schedule 15-25 pins daily cadence

Reddit

• Value-sharing format: helpful resource > context > community benefit
• Authentic voice, no self-promotion feel (90% value, 10% promotion)
• Subreddit-specific adaptation (respect community rules)
• Markdown formatting for readability
• Flair usage per subreddit requirements

Content Pillars Distribution

Output

Per Platform Adaptation

• Adapted content text/script matching platform format
• Platform-specific metadata (hashtags, tags, description)
• Recommended winning formula template applied
• Optimal posting time from platform schedule
• Required media assets list (dimensions, format)

Campaign Package

• Full set of adaptations across selected platforms
• Waterfall publishing schedule with timestamps
• Cross-platform content calendar
• Performance tracking KPIs per platform

References

• All platform specs, algorithm weights, and winning formulas sourced from Synthex/platform_master_config.json
• Posting schedules and optimization checklists per platform in config
• Analytics KPIs defined in analytics_config.kpis section of config
• See grounded-visuals skill for visual asset generation (per-platform specs still apply — dimensions, format)
• See video-engine skill for video format adaptation

Visual generation (binding): every thumbnail, pin, and per-platform image asset in step 7 is produced ONLY via generateImage()/generateBatch() (lib/services/ai/image-generation.ts) or the generate_image MCP tool — grounded-by-default on the owned reference library (public/reference-library/manifest.json + the private bucket, ingest via POST /api/admin/private-refs). No owned references for the subject ⇒ BLOCKED — never substitute stock or a direct provider call. Video re-cuts of owned footage route through the Railway media worker / media_* MCP tools; generated video uses lib/services/ai/video/generation-service.ts with the same grounded default. See .claude/rules/real-images-only.md + grounded-visuals. Direct provider calls fail CI.

Capability Uplift — Override Defaults

NEVER describe Synthex features with generic SaaS language: "powerful AI", "seamless integration", "robust platform", "world-class automation". Never produce a bullet list of features without an outcome attached to each one.

INSTEAD every feature showcase leads with the client outcome:

• ✗ "AI-powered content generation"
• ✓ "Produces 18 platform-ready posts from a single brief in under 4 minutes"

Use specific numbers wherever possible. Write in Australian English. Every platform is showcased from the client's perspective: what problem does it solve, how long does it take, what does the client NOT have to do anymore.

REFERENCE .claude/skills/synthex-standards/references/content-standards.md

Foundation & Gate Wiring (SYN-1050)

Adopted from the senior-skill standard so every artefact this skill produces is checked against the locked foundation before it lands.

Reads at every invocation (never cached — re-read each run):

• .claude/memory/ceo-foundation.md — voice tag (Q2.5.5), client-outcome framing, universal taboos.
• .claude/memory/verification-gates.md — gate state for any claim referenced.

Output gate: every client-facing artefact this skill produces routes through brand-voice-enforce before the CEO batched-review queue. A REJECT blocks the artefact until the quoted offending string is fixed.

Evidence standard: every quantitative or factual claim carries exactly one tag — [VERIFIED] / [INFERENCE] / [UNCONFIRMED]. Untagged = defect (.claude/rules/fabel-evidence-standard.md). Never state a projected result as fact.

Spec: see spec.md in this skill directory.