veda-style

name	veda-style
model	claude-sonnet-4-6
description	VEDA voice and tone setup. Captures the user's writing style so VEDA can draft emails, social posts, replies, and other messages in their voice. Use when the user says /style, "teach you my voice", "match how I write", "draft like me", "set up style guide".

Style Guide Creation

Help the user teach VEDA their writing style. Three input paths. Output is a single style guide that VEDA reads before drafting anything on the user's behalf.

Step 1: Gate Question

"How important is it to you that I sound like you when drafting messages, emails, or anything else on your behalf?"

If they shrug it off or say "doesn't matter":

• Update MEMORY.md Communication section to: "No strong style preference — default tone is fine."
• Tell them: "Got it. If you change your mind, just run /style again or drop a writing sample into style/." End here.

If it matters: continue.

Step 2: Offer Three Paths

"I can learn your style three ways. Which fits?

1. Paste examples — give me 2–3 things you've actually written: a Slack/text message, an email, a doc, a social post. Different contexts is better than the same context three times.
2. Analyze your writing — if Gmail or Slack is connected, I can pull recent messages you've sent and reverse-engineer your patterns. Faster, but only as good as what's in those tools.
3. Just describe it — tell me how you write and I'll capture it. Shortest path."

Wait for choice.

Step 3: Execute the Chosen Path

Path 1: Examples

Ask the user to paste 2–3 samples. For each, analyze:

• Tone: formal/casual, warm/direct, dry/expressive
• Length: short and punchy, or detailed?
• Structure: bullets, paragraphs, numbered lists
• Vocabulary: simple/technical; jargon level; specific phrases they use a lot
• Punctuation: em dashes, ellipses, exclamation marks, semicolons
• Capitalization: lowercase-first, title case, all-caps for emphasis
• Emoji: never / rarely / often / heavy
• Openings: dive in, greeting first, context before ask
• Closings: sign-off, action item, cold close

Summarize back: "Here's what I'm seeing in your writing: [2–3 sentence summary]." Ask if it sounds right. Adjust based on pushback.

Path 2: Analyze via API

Confirm Gmail and/or Slack are connected. If neither is connected:

"Neither Gmail nor Slack is connected to Claude Code yet — so I can't pull samples. Want to switch to pasting examples, or set up API integration first?"

If connected, ask:

• "Where should I pull from? Gmail sent items, Slack messages I've sent, or both?"
• "How far back? Last 30 days, last 90 days, all of it?"
• "Any specific channel or thread to focus on, or a representative slice?"

Pull a representative sample (10–30 messages, mix of contexts). Apply the same analysis criteria as Path 1. Show findings, ask for corrections.

Path 3: Verbal Description

Ask 1–2 follow-ups at a time:

1. "When you fire off a quick text or Slack message, how do you sound? Casual? Direct? Emoji?"
2. "What about longer writing — emails, docs, posts? Same tone, or do you shift?"
3. "What's the most common kind of writing you do that you'd want me to draft for you?"
4. "Anything you specifically don't want me to do? Buzzwords, exclamation marks, smiley faces, formal sign-offs?"

Step 4: Write the Style Guide

Create the style directory if it does not exist:

mkdir -p style

Idempotency check: if style/style-guide.md already exists, read it first.

"You already have a style guide from [date]. Want me to update it with what you just shared, or replace it?"

If updating, merge with existing sections rather than overwriting.

Write style/style-guide.md from style/_template.md, populated with the analysis. Source line at the bottom: examples / API analysis (which sources, what date range) / verbal description.

Step 5: Update CLAUDE.md

Add to the Tone and Style section of CLAUDE.md if not already present:

- Before drafting anything on the user's behalf, read `style/style-guide.md` and match tone, structure, length, and vocabulary.

Also add a Style Reference line in the User Context section pointing to the file.

Step 6: Confirm

"Saved to style/style-guide.md. I'll reference it before drafting any message, email, or post on your behalf. Want to test it on something now?"

If yes, hand off to drafting — read the guide and produce a draft for whatever they want.