cf-style-guide

Brand Style Guide Importer

Import brand voice profiles from existing style guide documents, URLs, or manual input. Extracts tone, formality, personality traits, writing style, approved/banned terminology, and compliance guardrails into a structured brand profile JSON that the ContentForge pipeline uses for every piece of content it produces.

When to Use

Use /contentforge:cf-style-guide when:

• You're onboarding a new brand and have an existing style guide document (.docx, .pdf) or URL
• You need to update an existing brand profile with revised guidelines
• You want to extract terminology and guardrails from compliance documents
• You're setting up ContentForge for a regulated industry (Pharma, BFSI, Healthcare, Legal) where guardrails are critical
• You want to validate that an existing brand profile matches current guidelines
• A client provided a style guide URL (Notion page, Google Doc, website page) and you need to import it

For creating a brand profile from scratch (no existing style guide), use /contentforge:brand-setup with interactive mode. For using an existing brand profile, just reference it by name in /contentforge:create-content --brand=BrandName.

What This Command Does

1. Load Style Guide — Fetch style guide from URL (via WebFetch), parse .docx/.pdf document, or accept manual input
2. Extract Voice Characteristics — Identify tone (authoritative, conversational, technical, witty), formality level (1-5), personality traits, and writing style patterns
3. Identify Terminology — Parse approved terms, banned/prohibited terms, industry-specific jargon, preferred spellings, and acronym definitions
4. Parse Compliance Requirements — Extract guardrails, required disclaimers, prohibited claims, regulatory requirements, and sensitivity guidelines
5. Capture Author Profiles (E-E-A-T) — If the style guide names authors/spokespeople (About/Team sections, byline conventions), extract name, title, credentials, bio, and profile URLs into author_profiles; otherwise prompt for at least one default author (or an explicit "authorless" choice, recorded with its SEO/AEO trade-off). Only user-confirmed facts — never invent credentials
6. Configure the AI-Assistance Disclosure — Write the ai_disclosure block: {"mode": "claude-surfaces", "text": null, "author": null} by default. Explain the three modes plainly: claude-surfaces (default — the disclosure attaches when the pipeline runs on a Claude surface, or when the surface is uncertain; it is skipped only when a non-Claude harness is affirmatively detected), always (attach on every surface — the safest posture for brands with their own AI-transparency obligations), off (never attach; the brand owns that choice and its compliance implications). The author field is OPTIONAL and may stay null — the default wording ("reviewed by our editorial team") needs no name; when the brand does name someone, that name also feeds the E-E-A-T byline. Custom text replaces the default verbatim — note that the default is deliberately vendor-neutral and claims only the review the pipeline performs; a brand adding stronger claims owns them
7. Generate Brand Profile JSON — Create or update a structured JSON profile following the brand-registry-template.json schema
8. Save and Validate — Save profile to Google Drive (via MCP) or local cache using the brand-cache-manager pattern, and validate the profile works with the ContentForge pipeline
9. Configure Tracking Backend — Choose where ContentForge tracks quality scores and delivers output files: Google Sheets + Drive, Airtable, or local filesystem