Choose the collection and category
Simple Business Apps contains task-oriented application concepts and tools; Landing Pages contains website designs and their supplied routes. Choose an existing category in categories.json that matches the work. If the category does not exist, propose it with its intended audience and examples before adding a new label.
Keep the template slug stable and descriptive. It becomes part of the public detail URL, download path, and source location. Updating an existing entry should preserve that identity unless a maintainer has agreed on a migration.
Include everything needed to use the work
Add the template metadata, complete PROMPT.md, preview source, generated thumbnail, local assets, and their credits. Describe whether the preview is an interactive demo or a visual concept. Explain external integrations and setup requirements rather than implying that a mock control already performs a real operation.
Run the catalog checks and inspect the site locally. Test desktop and mobile layouts, keyboard access, the primary flow, and relevant error states. Verify that downloads contain the files the preview actually needs.
Review, revise, and publish
Open a pull request from your fork with screenshots and a concise description of what works. Automated validation checks the collection and produces a review artifact. A maintainer reviews the implementation, prompt, attribution, and assets; respond to feedback in the same PR.
After approved changes reach main and the release job succeeds, build.host imports the reviewed release. The catalog can update without a dashboard-code deployment. Publication status, source history, and reviewer discussion stay with the contribution.