언제 쓸까: Before you've ever used the writer commands — profile must exist first.
흐름
-
Create the profile
/writer:profile-create — URL to scan: https://mysite.com/blog. I'll answer the questionnaire.✓ 복사됨
→ Structured voice profile with specific traits (not generic 'professional + approachable')
-
Calibrate from samples
Here are three posts I wrote. Refine the profile.✓ 복사됨
→ Concrete adjustments tied to your samples
-
View
/writer:profile-view✓ 복사됨
→ Saved profile you can edit later
결과: A reusable voice profile every subsequent piece draws from.
함정
- Profile is too generic because you skipped the questionnaire — Don't shortcut — vague profiles produce generic output
언제 쓸까: Fresh topic, want a finished post with SEO and quality checks.
사전 조건
- Brand voice profile created — /writer:profile-create as above
흐름
-
/writer:discuss the topic
/writer:discuss — the unspoken risks of serverless. 1200 words, for engineering VPs.✓ 복사됨
→ Claude gathers requirements, not a draft yet
-
/writer:plan and /writer:execute
/writer:plan, then /writer:execute.✓ 복사됨
→ Structured outline → full draft in your voice
-
/writer:verify and /writer:ship
/writer:verify — SEO + humanizer pass. Then /writer:ship to content/blog/.✓ 복사됨
→ Quality report, issues fixed, file saved with metadata
결과: A ready-to-publish post including SEO metadata.
언제 쓸까: You shipped a post and want a LinkedIn version that doesn't read like AI.
흐름
-
Feed the source
/writer:discuss — LinkedIn version of <blog URL>. 5-7 posts.✓ 복사됨
→ Sequencing + hook strategy, not raw fragmenting
-
Execute and verify
/writer:execute then /writer:verify.✓ 복사됨
→ Thread that stays in voice through the humanizer pass
결과: A LinkedIn thread you'd actually post.