Be complete about what is included
The package needs a complete prompt, template metadata, preview source, thumbnail, and the assets those files reference. Downloaded HTML should resolve its local dependencies. The description should state whether the preview is interactive or a visual concept and what a user will need to implement or connect.
A business template must not claim that a simulated payment, email, OCR result, or cloud save is real. A website template should not fabricate customer proof or imply that illustrative locations and products are operating businesses.
Check the states beyond the first screenshot
Inspect the desktop and mobile layouts and the controls needed to complete the main flow. Check labels, keyboard focus, text readability, empty results, input validation, loading, and failure feedback. For calculations, compare actual expected values; for exports, open the downloaded result.
Avoid hiding a broken interaction behind a cosmetic success message. If an integration is outside the supplied demo’s scope, explain that boundary and the setup required for a real implementation.
Preserve provenance and maintainability
Keep source credits and applicable image and font licenses with the template. Include the files needed to reproduce the preview, and keep credentials and private data out of the public repository. Use fictional example data that is clearly distinguishable from a real account.
Stable slugs, useful commit messages, and review evidence make later updates easier to assess. Changes to the collection run through the same validation and publication flow, so fixes reach the hosted preview and the downloadable package together.