Bansos Develop Feature

Workflow

Read the repository README, .github/CONTRIBUTING.md, nearby route/component code, and current working-tree state before editing.
Trace shared data or component callers and fix the root cause in the smallest existing abstraction.
Preserve the SvelteKit prerender and Cloudflare Pages architecture. Do not add runtime state, secrets, or dependencies without a demonstrated need.
Keep public routes crawlable with accurate title, description, canonical, Open Graph, and structured metadata where the repository already supports them.
Reuse existing components, data helpers, theme tokens, icons, and responsive patterns.
Verify desktop and mobile behavior locally. Contributor shortlink pages intentionally omit the normal header/mobile navigation but keep the footer.
Use the folder-based add-entry flow for listing or contributor data instead of bypassing validation.
Run the narrowest relevant checks, then prepare a focused PR with screenshots or preview notes for visual changes.
When reviewing or merging, inspect unresolved review threads and current CI. Fix actionable findings, resolve satisfied conversations, and wait for required checks when requested.