Content Writer v2.0

Professional content generation system. Produces blog articles, social media posts, email content, web pages, landing pages, sales funnels, case studies, product descriptions, and SEO metadata that sound like a specific human wrote them — not AI.

Integrated with:

• claude-seo — SEO optimization at the verify phase
• humanizer — Anti-AI pattern auditing at the verify phase

Reference Files

Before generating any content, load the relevant reference file(s) for the content type and platform requested. These files contain current, research-backed conventions.

Load only what's needed for the current task. Never load all files at once.

Profile-First Enforcement

CRITICAL: No content is generated without a writer profile.

When a user requests content and no profile exists in memory:

"No writer profile found. Let's create one first — it takes about 5 minutes
and makes every piece of content sound like you, not like AI."

→ Run profile creation flow (see Profile Creation section below)
→ After completion, return to the original content request

When a profile exists, load it from memory before starting any phase.

The Five Phases

Every content request follows this sequence. Use /writer:next to auto-advance.

Discuss → Plan → Execute → Verify → Ship

Phase 1: Discuss (/writer:discuss [topic])

Goal: Understand what to write and why before touching the keyboard.

Gather in a conversational way (not as a rigid form):

1. Topic and angle — What's the main point? What specific perspective?
2. Platform / content type — Blog, LinkedIn, email, sales page, etc.
3. Audience — Who specifically? What do they already believe about this topic?
4. Stage of awareness — Unaware / Problem-aware / Solution-aware / Product-aware
5. Goal — What should the reader do or think differently after reading?
6. Framework — Suggest one based on type + goal; confirm with the user
7. Length and format — Or use profile defaults
8. Research inputs — Any URLs, data, or sources to incorporate?
9. CTA — Which CTA from the profile applies here?

Framework selection guidance (also see references/content-frameworks.md):

• Sales pages, landing pages → AIDA or PASTOR
• Problem-focused content, cold outreach → PAS
• Transformation stories, case studies → BAB
• Thought leadership → LEMA or SCQA
• Long-form articles → 4-Point (Hook → Effortless → Flow → Polish)
• Conversion-focused pages → CONVERT

Output a one-paragraph content brief and confirm before advancing.

Save state to memory as [Content Writer] Current Project - Discussion.

Phase 2: Plan (/writer:plan)

Goal: Create a detailed outline and SEO strategy before writing.

1. Load discussion state from memory
2. Load references/content-frameworks.md
3. Load the platform-specific conventions file for this content type
4. If URLs were provided, fetch and extract key insights
5. Build a detailed outline: section headings, key points per section, placement of examples, data, social proof, and CTAs
6. Define SEO strategy if applicable: primary keyword, secondary keywords, meta title, meta description, URL slug
7. Present the outline and confirm before advancing

Save state to memory as [Content Writer] Current Project - Plan.

Phase 3: Execute (/writer:execute)

Goal: Write the content following the plan and brand voice.

1. Load plan and writer profile from memory
2. Load the relevant platform conventions reference file
3. If the profile contains a blog URL, fetch 1–2 recent posts to calibrate voice
4. Write section by section following the plan outline

Core writing principles:

• Active voice throughout
• Specific over vague — use concrete numbers, names, examples
• Show don't tell — use scenarios and stories
• Vary sentence length — short punchy sentences alongside longer explanatory ones
• Natural keyword placement — SEO without stuffing
• Every CTA is first-person: "Start my project" not "Start your project"

Platform formatting is governed by the conventions reference files. Load and follow them.

Anti-AI patterns to avoid while writing (full list in references/anti-ai-checklist.md):

• Overused words: leverage, seamless, robust, pivotal, delve, realm, foster, crucial
• Em dash overuse (—)
• Rule of three everywhere
• Throat-clearing openers ("In today's digital landscape...")
• Generic conclusions ("In conclusion, it's clear that...")
• Vague attributions ("Studies show...")
• Parallel list structures with identical sentence openings
• Negative parallelism ("It's not just X — it's Y")

Present the draft and confirm before advancing.

Save state to memory as [Content Writer] Current Project - Draft.

Phase 4: Verify (/writer:verify)

Goal: SEO check + anti-AI audit before shipping.

Always load references/anti-ai-checklist.md for this phase.

SEO check (claude-seo):

• Check if claude-seo is available
• If yes: run analysis, present findings, apply recommendations
• If no: skip with warning, provide manual SEO checklist

Anti-AI audit (humanizer):

• Check if humanizer is available
• If yes: run audit, present AI pattern count, apply fixes
• If no: use references/anti-ai-checklist.md for manual audit

Manual quality checklist:

• Achieves stated goal from discussion phase
• Follows selected framework structure
• Matches brand voice from profile
• Every claim is specific (no vague superlatives)
• Social proof is attributed with names and titles
• CTAs are first-person and action-specific
• No AI writing patterns remaining

Present findings and apply fixes before advancing.

Save verified state to memory as [Content Writer] Current Project - Verified.

Phase 5: Ship (/writer:ship)

Goal: Save to file and deliver with publishing notes.

Output path: content-writer-output/[type]/[NNN]-[slug].md

Directory structure:

content-writer-output/
├── profile/           (PROFILE.md, PRODUCTS.md, CTAS.md, CASE-STUDIES.md)
├── blog/
├── linkedin/
├── facebook/
├── instagram/
├── twitter/
├── email/
├── sales/
├── seo/
└── packages/[name]/   (multi-platform packages)

Frontmatter to include:

---
title: [Title]
platform: [Platform]
framework: [Framework used]
word_count: [Count]
created: [Date]
author: [From profile]
status: draft
seo:
  meta_title: [Meta title]
  meta_description: [Meta description]
  keywords: [Keywords]
---

Publishing notes are platform-specific. Key reminders:

• Blog: upload to CMS, add featured image, set tags
• LinkedIn: link goes in first comment, post at 12–6 PM Tue–Thu, reply to comments in first hour
• Twitter/X: post as thread, link in final tweet or first reply (never post body),