TestID

SvelteKit + TypeScript + Tailwind on Cloudflare Workers

OpenSpec summary

Implementation is anchored to the compliant alternative spec.

The current documentation covers product goals, technical design, and phased execution for the Cloudflare deployment path.

Proposal

Defines the compliant product scope, goals, non-goals, and abuse-control boundary.

Spec

Covers authentication, bilingual UI, template catalog, quota, billing, audit, and Cloudflare constraints.

Design and tasks

Maps the Worker, D1, R2, Queue architecture and the phased implementation plan.

OpenSpec

  • Authenticated access only with social login providers
  • Bilingual Chinese and English interface
  • CSV/XLSX import, single entry, and batch jobs up to 100 images
  • Monthly free quota plus pay-per-image billing
  • Mandatory visible test marking and audit metadata

Spec docs are stored under openspec/

Spec files

proposal.md

Product intent, target outcomes, supported document categories, and compliance boundary.

spec.md

Normative requirements for auth, billing, batch jobs, auditability, and platform constraints.

design.md

Cloudflare-oriented architecture using Workers, D1, R2, and Queues.

tasks.md

Phased implementation checklist from scaffolding to launch readiness.