Skip to main content
Each example below shows the expert sources to capture, the instruction files to create, and the slash command to run it. Adapt them to your domain.

​
Content Workflow

Learns your writing voice from your past content and drafts new pieces using your frameworks, examples, and tone. Feed it enough of your work and it stops sounding like a language model. Expert sources: 10-20 of your published blog posts, threads, or newsletters. Add 2-3 talks from writers you admire on craft and structure. Instruction file: 
# Voice Rules
- Sentences under 20 words by default. Vary length for rhythm.
- First person. No hedging ("I think," "perhaps," "it seems").
- Use concrete examples over abstractions. Show, then tell.

# Structure
- Open with a tension or a question. Never open with a definition.
- One idea per section. Each section earns the next.
- Close with a reframe, not a summary.

# Constraints
- Never write about [topics to avoid].
- Always reference real examples from memory, not hypotheticals.
Command: /draft-content [topic]

​
Research Workflow

Monitors a topic by ingesting new expert content weekly and produces briefings that cross-reference with your existing knowledge base. Surfaces what matters and flags what conflicts. Expert sources: Conference talks, podcast interviews, and expert breakdowns in your field. Add new ones weekly. Instruction file: 
# What Counts as a Key Insight
- A claim backed by data, not opinion.
- A framework that reframes an existing problem.
- A contradiction with something already in memory.

# Briefing Format
- 3-5 key insights, ranked by relevance.
- For each: the claim, the source, and how it connects to existing notes.
- Flag contradictions explicitly. Quote both sides.
Command: /weekly-briefing

​
Copywriting Workflow

Writes landing page copy, emails, and ads using proven conversion frameworks. Pulls from expert breakdowns on hooks, objection handling, and CTA patterns so the output follows tested structures, not generic templates. Expert sources: Talks from conversion experts covering headline formulas, objection handling, hook frameworks, and CTA patterns. Instruction file: 
# Frameworks
- Landing pages: PAS (Problem-Agitate-Solve) for awareness, AIDA for consideration.
- Emails: One CTA per email. Hook in the first line.
- Ads: Lead with the outcome, not the feature.

# Constraints
- Never use "revolutionary," "game-changing," or "unlock your potential."
- CTAs must be specific. "Get the checklist" over "Learn more."
- Match the audience's language. Pull phrasing from customer reviews in memory.
Command: /write-copy [product] [audience]

​
Scriptwriting Workflow

Reviews or drafts scripts using expert principles on dialogue, pacing, and structure. Works for screenplays, podcast scripts, video essays, or any narrative format where timing and voice matter. Expert sources: Masterclass-style breakdowns from screenwriters, showrunners, or dialogue coaches on subtext, scene construction, and story structure. Instruction file: 
# Dialogue
- Subtext over exposition. Characters talk around the point, not at it.
- Each character has a distinct speech pattern. Test by covering names.
- Cut any line that only delivers information.

# Pacing
- Scenes under 3 pages unless tension justifies length.
- Alternate high-tension and low-tension scenes. Never stack two quiet scenes.

# Structure
- Three-act framework. Midpoint reversal is mandatory.
- Every scene must turn. If the status quo is the same at the end, cut it.
Command: /review-script [file] or /draft-scene [brief]

​
Operations Workflow

Runs recurring business processes following documented SOPs. Built from recordings of your best operator walking through each process, so the workflow follows the same decision tree a trained team member would. Expert sources: Screen recordings or walkthroughs of your best operator executing each process step by step. One recording per process. Instruction file: 
# Process: [Process Name]
1. Pull the latest data from [source].
2. Check [condition]. If true, proceed. If false, escalate to [person].
3. Format output as [format]. Include [required fields].
4. Run quality check: [specific criteria].
5. Deliver to [destination]. Confirm receipt.

# Escalation Rules
- If any step fails, log the failure and notify [channel].
- Never skip a quality check. If unsure, escalate.
Command: /run-process [process-name]
These are starting points. The workflow improves every time you feed it more expert content. The instruction files are yours to edit, version, and share.