HamzaBHM

View saved version →

---
name: pod-workflow
description: Create and check POD listing drafts and design prompts with HamzaBHM. Automatically process a POD idea or design screenshot for Etsy PNG, Etsy Shirt, Merch by Amazon, TeePublic, or Redbubble. First run the safety gate. If safe, deliver only IP/policy screening status, a platform-specific listing, and a design prompt. Support complete batches on one platform and scale to five other niches only on explicit request. Create listings and prompts for selected scaling ideas. Validate generated listing fields with validate_listing_batch; export CSV with export_listing_batch only on request. Also use for listing-rule questions and checking or exporting existing listing drafts. Never generate images. If risky or cautionary, stop that idea with a short risk message; continue remaining batch items.
---

# HamzaBHM POD Workflow

Preserve the user’s selected platform, original idea, and requested output. Use the tools for actual listing checks and optional CSV export, following [tool mapping](references/tool-mapping.md) and [drafting rules](references/drafting-rules.md).

## Direct rule questions and existing drafts

For questions about supported formats, field limits, or how checks work, call `get_listing_rules` and answer from the actual returned profiles. No platform selection is needed to explain all supported rules. Do not force a creative listing or a safety verdict for a rules question.

When the user asks to check existing listing drafts, preserve their supplied copy and send its fields to `validate_listing_batch`. Report the actual mechanical findings concisely. Do not rewrite the copy unless the user asks for repairs, and do not present a mechanical pass as IP/policy screening or legal clearance. If the platform is missing or Etsy is ambiguous, ask only for the needed platform/subtype.

When the user explicitly asks to export existing invalid drafts with their findings marked, `export_listing_batch` may use `include_invalid: true`. Warn concisely that the CSV contains invalid drafts and show the actual findings. This exception is only for the user’s explicit marked-draft export request; never silently enable it to make a normal generated listing pass. For ordinary export requests, use `include_invalid: false` or omit it and correct or report errors according to the user’s request. Do not claim that an invalid draft is valid or publish it.

For new creative ideas, use the workflow below.

Use this skill when the user sends either:
- a screenshot/image of a design or a design shown on a product, OR
- a phrase, slogan, saying, niche, or design idea,
and identifies the target platform.

Accepted platform intents:
- Etsy PNG
- Etsy Shirt
- Merch by Amazon
- MBA
- TeePublic
- Redbubble

For Etsy, the user must specify PNG or Shirt. For Merch by Amazon, TeePublic, and Redbubble, no product subtype is required.

For a new idea, if the platform is missing, ask only which platform they want and do nothing else yet.
If the user says Etsy without specifying PNG or Shirt, ask only: "Etsy PNG or Etsy Shirt?"

For a valid new idea, complete Steps 1–4 in one response, keeping Step 2 internal. Run Step 5 only when the user explicitly asks to scale. Never generate images or call image-generation tools in this workflow.

# Output and Batch Mode

For every normal SAFE idea, output ONLY these three sections in this exact order:

IP/Policy Check: ✅ No specific risk found

## Listing
[platform-specific fields using all Step 3 rules]

## Design Prompt
[one single-paragraph prompt using all Step 4 rules]

Never display Idea Breakdown, Target Audience, Principal Keywords, Long-Tail Keywords, Best Design Style, Occasion Fit, reasoning, explanations, commentary, or summaries. Do not automatically ask to scale. A brief tool-error note inside Listing is permitted when needed to avoid a false claim of validation.

## Tool-backed listing checks

After drafting a SAFE listing, call `validate_listing_batch` with its generated li

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 3 — file references are metadata, not package contents.