AlexandrAI AGENTS.md
agents-md

Gumroad Product Page Designer Agent Guide

Project-specific AGENTS.md guidance for the Gumroad product page designer role, cover image standards, preview image planning, simple HTML copy, and publish visual gates.

AGENTS.md

Guidance for coding agents working on the Gumroad product page designer role.

Project Overview

The product page designer turns the product files into an honest Gumroad listing. The role owns final page structure, cover direction, preview image plan, exact artifact proof, and visual publish gates. It must show what the buyer gets without inventing proof.

Source Files

  • agents/product-page-designer.md defines the role.
  • skills/gumroad-page-designer/SKILL.md defines page and image standards.
  • skills/demo-driven-product-page/SKILL.md defines the active pitch pattern.
  • skills/gumroad-page-designer/references/gumroad-page-patterns.md summarizes page formulas.
  • products//product.json carries description_html, cover_prompt, cover_alt_text, and page_design_notes.
  • products//assets/cover.png is the custom cover gate for publish.

Setup Commands

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>

Rerun render and QA after replacing cover or preview assets.

Change Rules For Agents

  • Use Gumroad-native levers: title, subtitle, cover, previews, rich description, FAQ, tags, price, support, and disclaimer.
  • Select a fitting formula: template pack, prompt pack, skill or harness pack, workspace, or beginner guide.
  • Start with a buyer pain and one memorable page message.
  • Show exact inventory early: PDF, templates, file formats, examples, skill files, or trackers.
  • Prefer product proof visuals over decorative imagery.
  • Use deterministic overlays for readable cover text; do not rely on generated text.
  • Block publish if no custom cover exists or the cover looks generic, misleading, blurry, or unrelated.
  • Do not use fake testimonials, fake ratings, revenue imagery, competitor marks, or guaranteed outcome claims.

Cover Standard

Preferred covers look like real consultant-prepared materials: printed guide pages, worksheets, file manifests, folders, markdown or skill file previews, real desk surface, natural shadows, and wide marketplace-safe composition. Avoid app-icon style, plastic cards, floating objects, dark stock-photo scenes, money imagery, and unreadable AI text.

Verification

Open the rendered cover or preview images before publish. Confirm build/manifest.json marks the cover as custom after render and that qa_report.json has no blocking visual or page-copy failures.

Security Notes

Preview assets and page copy are public. Do not expose private account details, buyer data, secrets, local paths, private endpoints, or stale copy from another product.

PR Checklist

  • First-screen hook is buyer-specific.
  • Exact file proof is visible.
  • Page_design_notes records formula, core message, shared pain, proof assets, CTA, and risks avoided.
  • Cover_prompt and cover_alt_text are specific.
  • Custom cover gate is satisfied before publish.