setup

/guide:setup — Configure Your Content Pipeline

"Would it save you a lot of time if I just gave up and went mad now?" No. Let's set this up properly instead.

Interactive setup for the Guide content pipeline. Creates your content/config.yaml by asking what you care about, where you get your information, and how you write.

Run this once. After that, /guide:pipeline handles everything.

When This Runs

• First time: User runs /guide:setup directly, or /guide:pipeline detects no config and suggests it
• Reconfiguration: User runs /guide:setup again to add sources, change themes, etc. — existing config is read and updated, not overwritten

Steps

Step 1: Read Existing State

• Check if content/config.yaml already exists
• If yes, read it — this is a reconfiguration, not a fresh setup. Pre-fill answers from existing values.
• Check if defaults/config.yaml exists in the plugin directory for the schema reference

Step 2: Voice Profile

Ask:

"First — how do you write? Do you have an existing writing voice document, or should we figure it out together?"

If they have a voice file: Ask for the path (e.g., thoughts/writing-voice.md). Read it to confirm it looks like a voice profile.

If they don't: Ask a few questions to build one:

• "Describe your writing style in 3 words"
• "What kind of writing makes you cringe?" (these become anti-patterns)
• "Any corporate jargon that should never appear in your content?" (seed the blocklist)
• Write a basic voice profile to thoughts/writing-voice.md and reference it in config

Step 3: Themes

Ask:

"What topics matter to you? Think both personal (what you care about as a human) and professional (what you work on)."

Let them list freely. Organize into themes.personal and themes.professional in the config. Suggest categorization but don't force it.

If they're stuck, offer examples:

• Personal: transformation, fitness, creativity, parenting, travel, vulnerability
• Professional: engineering, AI, leadership, product, design, startups