Go to file
Oleg Proskurin 15052a1965 feat: instruction patches 2026-01-08 00:55:29 +07:00
.claude/commands feat: setup the content-system 2025-12-22 22:55:01 +07:00
0-inbox docs: more research 2026-01-02 16:06:07 +07:00
1-planning doc: new article 2025-12-29 11:00:41 +07:00
3-drafting doc: pass seo 2026-01-07 03:06:57 +07:00
6-ready doc: add seo edits 2026-01-07 22:08:53 +07:00
assets editor fix 2026-01-07 22:29:30 +07:00
desktop-agents feat: add validation agent 2025-12-28 23:02:36 +07:00
project-knowledge chore: remove outdated 2025-12-27 18:42:02 +07:00
research feat: add screenshots to the article 2026-01-07 00:46:33 +07:00
scripts feat: update script 2025-12-28 23:02:09 +07:00
shared feat: instruction patches 2026-01-08 00:55:29 +07:00
style-guides docs: more docuemnts 2025-12-28 22:29:40 +07:00
wiki/tutorials wiki: add tutorial 2025-12-29 00:12:58 +07:00
.env feat: setup dataforseo 2025-12-25 23:35:20 +07:00
.gitignore feat: add package.json and deps 2025-12-28 23:01:47 +07:00
.mcp.json feat: setup dataforseo 2025-12-25 23:35:20 +07:00
CLAUDE.md feat: add validation agent 2025-12-28 23:02:36 +07:00
README.md feat: finalize content-system 2025-12-23 21:50:44 +07:00
batch-processing.md phase 2 2025-12-27 16:57:35 +07:00
content-framework.md feat: add validation agent 2025-12-28 23:02:36 +07:00
human-editing-checklist.md phase 2 2025-12-27 16:57:35 +07:00
manual.md feat: projects setup 2025-12-27 20:06:54 +07:00
package-lock.json feat: add package.json and deps 2025-12-28 23:01:47 +07:00
package.json feat: add package.json and deps 2025-12-28 23:01:47 +07:00

README.md

Banatie Content Repository

Multi-agent content creation system for Banatie blog.

Quick Start

For Content Creation (Claude Desktop)

  1. Open agent project in Claude Desktop
  2. Say /init to start
  3. Select file to work on
  4. Follow agent workflow
  5. Confirm handoff to next stage

For Repository Management (Claude Code)

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

# Commands:
/status              # Pipeline overview
/validate {slug}     # Check file validity
/move {slug} {stage} # Move file between stages

The Pipeline

@spy → 0-inbox → 1-planning → 2-outline → 3-drafting ⟲ → 4-human-review → 5-optimization → 6-ready → 7-published
              @strategist   @architect   @writer       Human          @seo            Human      Human
                                         @editor                      @image-gen

File Structure

One markdown file per article, moves between folders:

{stage}/{slug}.md

File grows by accumulating sections:

  • Brief (from @strategist)
  • Outline (from @architect)
  • Draft → Text (from @writer, edited by human)

Agents

Agent Role Model
@spy Research Sonnet
@strategist Topic planning Opus
@architect Article structure Opus
@writer Draft writing Sonnet
@editor Quality review Opus
@seo SEO + GEO Sonnet
@image-gen Visual assets Sonnet
@style-guide-creator Author personas Opus

Authors

ID Persona Topics Status
henry Technical Expert Tutorials, API guides Complete
nina Creative Designer AI art, design Pending

Key Files

File Purpose
shared/content-framework.md How the system works
shared/human-editing-checklist.md Human review tasks
style-guides/AUTHORS.md Author registry
style-guides/henry-technical.md Henry's voice

Language

  • Files: English
  • Agent communication: Russian

Last updated: December 2024