AlexandrAI AGENTS.md
agents-md

Gumroad Support Manager Agent Guide

Project-specific AGENTS.md guidance for the Gumroad support manager role, buyer support expectations, FAQ assets, refund scope, support copy, and QA handoff.

AGENTS.md

Guidance for coding agents working on the Gumroad support manager role.

Project Overview

The support manager prepares one Gumroad product for buyer questions. It is a manual support-readiness pass, not an inbox monitor or background support agent. Its job is to make support scope, refund logic, FAQ assets, and buyer usage expectations clear before QA and publishing.

Source Files

  • agents/support-manager.md defines the role.
  • skills/customer-support-playbook/SKILL.md defines FAQ, reply, refund, and support-scope rules.
  • products//product.json carries support, refund_policy, description_html, and templates.
  • products//meeting.md records Support Plan.
  • agents/qa-manager.md checks support copy and support assets.

Setup Commands

There is no support-only script. Support readiness is checked through product render and QA:

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>

Change Rules For Agents

  • Make support expectations visible in the Gumroad description and PDF when relevant.
  • Route buyers to the email on their Gumroad receipt unless the owner supplied another support channel.
  • Keep refund conditions in refund_policy unless the owner explicitly wants public refund copy.
  • Add support-faq.md when buyers need usage guidance.
  • Add support-replies.md when repeated seller responses are likely.
  • Keep support assets short, concrete, and aligned with the actual product files.
  • Do not promise custom consulting, unlimited revisions, response times, or professional advice.
  • Do not invent customer messages or support history.

Support Risk Review

Check whether buyers may ask where to start, how to customize templates, what to do with broken files, whether outcomes are guaranteed, whether custom advice is included, or whether the product fits their niche.

Meeting Output

Write Support Plan with expected buyer questions, support copy, included support assets, out-of-scope requests, and refund handling.

Verification

Confirm product.json includes support and refund_policy, description_html includes visible support and disclaimer copy, and templates include support assets when the risk review calls for them.

Security Notes

Do not publish private support inboxes, buyer messages, buyer emails, private account ids, or hidden contact channels. Public support copy should describe scope, not expose operations.

PR Checklist

  • Support copy is present and accurate.
  • Refund policy is fair and scoped to file or description problems.
  • Out-of-scope requests are explicit.
  • Support assets match the product.
  • QA receives support risks and support asset filenames.