Web Prompt guide
Web prompts document reproducible web design and interaction. Unlike image-only works, you submit a screenshot cover, an HTTPS page URL, and a detailed prompt.
Screenshot requirements
- Required; capture the hero or key UI state
- Must match what your prompt describes
- If iframe preview fails, the screenshot is the source of truth
Writing the prompt
Describe layout, visuals, copy, and interactions — do not paste the URL only. Aim for ≥80 characters.
Page type: Landing page Layout: top nav + hero split + 3 feature columns Visual: dark bg, gradient CTA, rounded cards Copy: English headline + Chinese subhead Interaction: hero button hover scale
Good vs weak examples
✓ Good prompt
SaaS landing: split hero, purple gradient CTA, three-tier pricing…
✗ Weak prompt
"https://example.com looks nice"
Review & publishing
- All web UGC requires manual review
- Trusted users are not auto-published
- Some sites block embeds — rely on the screenshot