blog-brand

Generates BRAND.md and VOICE.md editorial context files for blog workflows.

1|Updated Dec 24, 2021
One-click install
npx skills add https://github.com/arthur-fontaine/arthurfontaine.fr --skill blog-brand-arthur-fontaine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blog-brand
Source: https://github.com/arthur-fontaine/arthurfontaine.fr/tree/main/.agents/skills/blog-brand
Command: npx skills add https://github.com/arthur-fontaine/arthurfontaine.fr --skill blog-brand-arthur-fontaine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Blog writing commands often lack consistent brand context, forcing each command to re-derive audience, positioning, and voice from scattered sources. This Skill creates two canonical project-root files, BRAND.md and VOICE.md, that the blog orchestrator auto-loads for write, rewrite, brief, outline, calendar, and strategy workflows. ## Core Features & Use Cases - Interactive brand interview: A 5-step guided process captures audience, positioning, editorial rules, topic boundaries, and voice settings, then writes structured BRAND.md and VOICE.md files. - Persona integration: Pre-fills voice answers from existing blog-persona JSON and mirrors tone dimensions into readable VOICE.md prose. - Show and update commands: Display current brand context or re-run the interview with existing values as defaults. - Use Case: A content lead runs the init command once to define audience, taboo phrases, and competitor differentiators; every subsequent blog write or brief command automatically inherits that editorial context. ## Quick Start Ask the assistant to run the blog brand init command and answer the interview questions to generate BRAND.md and VOICE.md in your project root.

Frequently Asked Questions about blog-brand

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create brand guidelines for a blog with AI?▼

Run the blog brand init command to start a 5-step interactive interview covering audience, positioning, editorial rules, topic scope, and voice. The answers are written to BRAND.md and VOICE.md files at your project root for reuse across blog commands.

What is the difference between BRAND.md and VOICE.md?▼

BRAND.md captures audience, positioning, competitor differentiation, editorial rules, and topic scope. VOICE.md captures how the brand sounds, including pronoun stance, sentence and paragraph ceilings, headline patterns, and tone dimensions mirrored from persona JSON.

Does blog-brand work without a blog-persona file?▼

Yes, the init interview still produces a complete VOICE.md even when no persona JSON exists. If a persona exists, its tone dimensions are used to pre-fill voice answers, and you can create one later for programmatic enforcement.

Which blog commands use the BRAND.md and VOICE.md files?▼

The blog orchestrator auto-loads both files for write, rewrite, brief, outline, calendar, and strategy commands, injecting their contents into downstream agent prompts. If the files are absent, behavior is unchanged and fully backward compatible.

How do I update existing brand context files?▼

Run the blog brand update command, which re-runs the interview with your current values pre-filled as defaults. Accept existing answers or type new ones, and both files are overwritten with an updated date line.