# Banatie Content Repository

This repository contains all content for the Banatie blog and marketing materials.

## Overview

Content is created using a multi-agent system with **7 Claude Desktop agents** handling different aspects of content creation, while **Claude Code** manages the repository structure.

## Quick Start

### For Content Creation (Claude Desktop)

1. Open one of the agent projects in Claude Desktop
2. Each agent has Filesystem MCP access to this repository
3. Follow the agent's workflow to create/edit content

### For Repository Management (Claude Code)

```bash
cd /projects/my-projects/banatie-content
claude

# Use slash commands:
/status              # See pipeline status
/validate {slug}     # Check article validity  
/move {slug} {stage} # Move article between stages
```

## Repository Structure

```
banatie-content/
├── CLAUDE.md               ← Claude Code instructions
├── .claude/commands/       ← Slash commands for Claude Code
├── shared/                 ← Shared knowledge for all agents
├── style-guides/           ← Author voice definitions
├── research/               ← Competitive intelligence (@spy)
├── desktop-agents/         ← (temp) System prompts for Claude Desktop
├── 0-inbox/                ← Raw ideas
├── 1-planning/             ← Briefs (@strategist)
├── 2-outline/              ← Outlines (@architect)
├── 3-drafting/             ← Drafts + Critiques (@writer + @editor)
├── 4-human-review/         ← Human editing
├── 5-optimization/         ← SEO + Images (@seo + @image-gen)
├── 6-ready/                ← Ready to publish
├── 7-published/            ← Archive with metrics
└── assets/                 ← Generated images
```

## Content Pipeline

```
Research → Planning → Outline → Draft → Review → Optimization → Ready → Published
   @spy    @strategist  @architect  @writer  @editor   @seo/@image   Human    Human
```

## Agents

| Agent | Role | Model |
|-------|------|-------|
| @spy | Competitive research | Sonnet |
| @strategist | Topic planning | Opus |
| @architect | Article structure | Opus |
| @writer | Draft writing | Sonnet→Opus |
| @editor | Quality review | Opus |
| @seo | SEO optimization | Sonnet |
| @image-gen | Visual assets | Sonnet |
| @style-guide-creator | Create author personas | Opus |

## Authors

| ID | Persona | Topics |
|----|---------|--------|
| `henry` | Technical Expert | Tutorials, guides, API integration |
| `nina` | Creative Designer | AI art, design, creative workflows |

## Key Files

- `shared/banatie-product.md` — Product description
- `shared/target-audience.md` — ICP details
- `shared/content-framework.md` — How the system works
- `style-guides/henry-technical.md` — Henry's writing style
- `style-guides/banatie-brand.md` — Brand guidelines

## Language

- **Files:** Always English
- **Communication with agents:** Russian
- **Technical terms:** Always English

## Article Structure

Each article lives in `{stage}/{slug}/`:

```
{stage}/{slug}/
├── meta.yml          ← Required metadata
├── brief.md          ← From @strategist
├── outline.md        ← From @architect
├── draft-v{N}.md     ← From @writer
├── critique-v{N}.md  ← From @editor
└── final.md          ← Human edited
```

## meta.yml Required Fields

```yaml
slug: article-url-slug
title: "Article Title"
author: henry                    # REQUIRED
status: planning                 # planning | outline | drafting | review | optimization | ready | published
created: 2024-12-21
content_type: tutorial
primary_keyword: "main keyword"
```

---

**Repository Owner:** Oleg  
**Last Updated:** December 2024