Bansos Add Entry

Goal

Turn a source link or user-provided promo details into one clean bansos.dev entry with clear evidence, contributor attribution, and a valid submission path.

Workflow

1. Read the source page or user-provided evidence before writing copy. If the source is current, browse or otherwise verify the latest terms, dates, pricing, quotas, and eligibility.
2. Extract only fields supported by bansos.dev: id, title, provider, description, benefits, promoCode, validity, requirements, tips, publishedAt, contributor, ctaLink, tags, featured, and status.
3. Prefer the public CLI path unless the user explicitly asks for maintainer/direct mode.
4. Validate locally with npx bansosdev add ... --mode json before asking a user to submit, opening an issue, or preparing a PR.
5. If the user asks you to implement directly in the repo, update src/lib/data/bansos.json through the repo script where possible and preserve existing formatting.
6. Create a concise PR/issue body that mentions the source link, contributor, validity, and any uncertainty.

Data Rules