AlexandrAI AGENTS.md
agents-md

Gumroad Content Producer Agent Guide

Project-specific AGENTS.md guidance for the Gumroad content producer role, PDF quickstart sections, editable artifacts, LLM skill files, support assets, and originality boundaries.

AGENTS.md

Guidance for coding agents working on the Gumroad content producer role.

Project Overview

The content producer writes the paid product itself: PDF quickstart sections plus the editable template, skill, harness, tracker, worksheet, example, or support files that go into the ZIP. The goal is a useful AI execution kit, not a blog post or generic prompt bundle.

Source Files

  • agents/content-producer.md defines the role.
  • skills/pdf-template-product-builder/SKILL.md defines PDF and artifact standards.
  • products//product.json is the product source of truth.
  • scripts/product_artifacts.py renders guide, PDF, ZIP, cover, and QA inputs.
  • agents/support-manager.md receives support-sensitive content.
  • agents/qa-manager.md verifies usefulness, originality, and policy safety.

Setup Commands

bashpython3 scripts/gumroad_status.py snapshot --output-dir research
UV_LINK_MODE=copy UV_PROJECT_ENVIRONMENT="$HOME/.cache/gumroad-codex-agent-venv" uv run python scripts/product_artifacts.py render products/<slug>/product.json
UV_LINK_MODE=copy UV_PROJECT_ENVIRONMENT="$HOME/.cache/gumroad-codex-agent-venv" uv run python scripts/product_artifacts.py qa products/<slug>
python3 scripts/gumroad_cli.py dry-run products/<slug>

Use render and QA after product.json contains real sections and templates.

Change Rules For Agents

  • Make every PDF section teach a concrete task.
  • Include task, context, steps, decision rule, example, mistake, and next action where useful.
  • Create templates with usage notes, fields, examples, and completion criteria.
  • For premium products, target substantial guide depth and at least 24 useful artifacts unless the owner chooses a smaller offer.
  • Include actual LLM skill, harness, AGENTS.md, examples, or QA files when the product promises them.
  • Keep automation manual, inspectable, credential-safe, documented, and reversible.
  • Include support FAQ, support replies, or buyer usage guide when buyer confusion is likely.
  • Remove filler sections and duplicate checklist variants.

Template Rules

Template filenames must be safe repo-relative paths with no hidden files, parent traversal, or absolute paths. JSON artifacts must be valid JSON and must not contain embedded credentials, private URLs, or irreversible live actions by default.

Verification

bashUV_LINK_MODE=copy UV_PROJECT_ENVIRONMENT="$HOME/.cache/gumroad-codex-agent-venv" uv run python scripts/product_artifacts.py render products/<slug>/product.json
UV_LINK_MODE=copy UV_PROJECT_ENVIRONMENT="$HOME/.cache/gumroad-codex-agent-venv" uv run python scripts/product_artifacts.py qa products/<slug>

Inspect build/guide.md, the generated PDF, the template ZIP, and qa_report.json before handoff.

Security Notes

Do not include customer data, credentials, private account ids, private endpoints, hidden services, cron loops, or autonomous bulk execution in buyer artifacts.

PR Checklist

  • Sections match the product promise.
  • Templates have real jobs and are not empty shells.
  • Description_html matches actual files.
  • Source and claim notes are present when factual or market claims are used.
  • Support-sensitive assumptions are handed to the support and QA roles.