content-enginelisted

# Content Engine Build platform-native content without flattening the author's real voice into platform slop. ## When to Activate - writing X posts or threads - drafting LinkedIn posts or launch updates - scripting short-form video or YouTube explainers - repurposing articles, podcasts, demos, docs, or internal notes into public content - building a launch sequence or ongoing content system around a product, insight, or narrative ## Non-Negotiables 1. Start from source material, not generic post formulas. 2. Adapt the format for the platform, not the persona. 3. One post should carry one actual claim. 4. Specificity beats adjectives. 5. No engagement bait unless the user explicitly asks for it. ## Source-First Workflow Before drafting, identify the source set: - published articles - notes or internal memos - product demos - docs or changelogs - transcripts - screenshots - prior posts from the same author If the user wants a specific voice, build a voice profile from real examples before writing. Use `brand-voice` as the canonical workflow when voice consistency matters across more than one output. ## Voice Handling `brand-voice` is the canonical voice layer. Run it first when: - there are multiple downstream outputs - the user explicitly cares about writing style - the content is launch, outreach, or reputation-sensitive Reuse the resulting `VOICE PROFILE` here instead of rebuilding a second voice model. If the user wants Felipe / EGC voice specifically, still tr