/publish "Blog Title Here"

Steps:

1. CONTENT: Research topic, write draft, add SEO
2. DESIGN: Generate hero image, format visuals
3. DEV: Create MDX file, deploy to production
4. MARKETING: Generate social posts, schedule distribution

→ Research trending content on topic
→ Create outline based on your style
→ Write 1,500-2,000 word draft
→ Add FAQ section for SEO
→ Include internal links

→ Generate hero image matching brand
→ Create OG image for social sharing
→ Format any code blocks or diagrams

→ Create MDX file with frontmatter
→ Run build verification
→ Deploy to production
→ Verify live URL

→ Generate LinkedIn post
→ Create Twitter thread
→ Draft newsletter snippet
→ Schedule posts (if integrated)

# /publish

When I say "/publish [title]", execute this workflow:

## Phase 1: Content

- Research: Find 3-5 top articles on this topic
- Outline: Create H2/H3 structure matching my blog style
- Draft: Write 1,500+ words with code examples where relevant
- SEO: Add 5+ FAQ questions at the end

## Phase 2: Assets

- Hero: Generate image with topic visualization
- Meta: Create title (60 chars), description (155 chars)

## Phase 3: Deploy

- File: Create content/blog/[slug].mdx
- Build: Verify no errors
- Deploy: Push to production

## Phase 4: Social

- LinkedIn: 1,300 char post with hook
- Twitter: 5-7 tweet thread
- Output: Display all content for review

Wait for my approval before deploying.

/weekly-ops

Steps:

1. ANALYTICS: Pull traffic, engagement, revenue data
2. CONTENT: List published content and performance
3. BUSINESS: Revenue summary, new leads, tasks completed
4. PLANNING: Next week priorities

## Weekly Operations Report: Jan 20-26, 2026

### Traffic & Engagement

- Website visits: 2,340 (+15% vs last week)
- Blog views: 1,230 (top: "Jarvis Tutorial" at 450)
- Newsletter: 234 opens, 12% click rate

### Content Published

1. "Build Your Own Jarvis" - 450 views
2. "Creator Intelligence Systems" - 320 views
3. "Getting Started Guide" - [scheduled for Tuesday]

### Revenue

- Pro tier signups: 3 ($891)
- Consulting inquiries: 2

### GitHub

- Stars: 47 (+23 this week)
- Issues opened: 5
- PRs merged: 2

### Next Week Priorities

1. Complete tutorial video
2. Launch newsletter campaign
3. Publish 3 more blog posts

# /weekly-ops

Generate weekly operations report:

## Data Sources

- Read analytics from /dashboard if available
- Count blog posts published this week
- Check git log for commits
- Review products.json for revenue indicators

## Report Format

1. **Summary**: 3-bullet overview
2. **Content**: What was published, performance
3. **Business**: Revenue, leads, growth
4. **Technical**: GitHub activity, deployments
5. **Next Week**: Top 3 priorities

Output as formatted markdown.

/onboard "Client Name" type:consulting

Steps:

1. BUSINESS: Create CRM entry, project folder structure
2. CONTENT: Generate welcome email, kickoff agenda
3. DEV: Set up project repository (if needed)
4. ADMIN: Create invoice, set reminders

{
  "client": "Acme Corp",
  "type": "consulting",
  "status": "onboarding",
  "startDate": "2026-01-21",
  "contact": {
    "name": "Jane Smith",
    "email": "jane@acme.com"
  }
}

Subject: Welcome to FrankX - Let's Build Something Great

Hi Jane,

Excited to kick off our work together...
[Personalized based on project type]

# /onboard

When I say "/onboard [client] type:[project-type]":

1. Create client folder at /clients/[client-slug]/
2. Generate brief.md with:
   - Client name, contact info
   - Project type and scope
   - Key dates and milestones
3. Draft welcome email matching my tone
4. Create invoice template
5. Add to task list: "Schedule kickoff call"

Output all generated content for review.

/repurpose "blog-post-slug"

Steps:

1. READ: Extract key points from blog post
2. SOCIAL: Generate LinkedIn post, Twitter thread
3. VIDEO: Create video script outline
4. EMAIL: Draft newsletter version

Every creator I talk to wants the same thing:

"I want my own Jarvis."

Not another chat tool. Not another subscription.

A personal AI that:
→ Knows your projects
→ Remembers your preferences
→ Executes your workflows
→ Gets smarter over time

Here's how to build it (free): [link]

1/ Every creator wants their own Jarvis.

Here's how to build one (for free):

🧵

2/ The problem with AI tools...
[continues for 7 tweets]

Hook (0-10s): "What if you had your own Jarvis?"
Problem (10-45s): Generic AI doesn't know you
Solution (45-90s): The Agentic Creator OS
Demo (90-180s): Show the workflow
CTA (180-210s): Get it free on GitHub

# /repurpose

When I say "/repurpose [slug]":

1. Read content/blog/[slug].mdx
2. Extract:
   - Main thesis
   - Top 3 takeaways
   - Best quotes
   - Key stats

3. Generate:
   - LinkedIn: 1,300 chars, hook + value + CTA
   - Twitter: 7-tweet thread, numbered
   - Video: Outline with timestamps
   - Email: 300 words, conversational

Output all versions for review and scheduling.

/review feature:authentication

Steps:

1. DEV: Scan code changes, identify issues
2. CONTENT: Generate documentation
3. TEST: Suggest test cases
4. SHIP: Create PR description

## Review: Authentication Feature

### Changes Analyzed

- lib/auth.ts (82 lines added)
- middleware.ts (23 lines modified)
- app/api/auth/route.ts (new file)

### Findings

✅ Good: Rate limiting implemented
✅ Good: Input validation present
⚠️ Note: Consider adding refresh token rotation
❌ Issue: Missing error logging in catch block

### Recommendations

1. Add error logging at line 45
2. Consider implementing token refresh
3. Add integration tests for edge cases

# Authentication System

## Overview

JWT-based authentication with email/password login.

## Endpoints

- POST /api/auth/login - Authenticate user
- POST /api/auth/logout - Clear session
- GET /api/auth/me - Get current user

## Usage

[Code examples]

# /review

When I say "/review feature:[name]":

1. Find recent changes related to [name]
2. Analyze for:
   - Security issues
   - Performance concerns
   - Code quality
   - Missing tests
   - Documentation gaps

3. Generate:
   - Review summary with findings
   - Documentation draft
   - Test suggestions
   - PR description

Output review for my approval before creating PR.