Planning artifacts: QR Code Generator (Related to #22)

[github-actions]

Related to #22

What's in this PR

Planning artifacts generated from the approved QR Code Generator proposal (issue #22).

Three new files under specs/004-qr-code-generator/:

File	Purpose
spec.md	Feature specification — 3 prioritised user stories, functional requirements, acceptance scenarios, success criteria
plan.md	Implementation plan — technical context, phase design, file structure, key design decisions
tasks.md	Task breakdown — 46 numbered tasks across 6 phases, organized by user story for independent delivery

Scope summary

• US1 (P1 MVP): Plain URL/text input → live QR preview → PNG + SVG download, no watermark
• US2 (P2): Foreground/background color pickers, error correction selector, output size slider, Reset to Defaults
• US3 (P3): WiFi, vCard, and SMS structured template forms with auto-assembled format strings

Architecture

• 100% client-side — Canvas API + vendored qrcode library (~15 KB UMD bundle)
• Ships as tools/qr-code-generator.html + tools/qr-code-generator/main.js + tools/qr-code-generator/style.css
• Zero server requests; GitHub Pages compatible; offline-capable after first load
• Complexity rating: 2/10 (encoding fully delegated to the library)

Review checklist

• User stories and acceptance scenarios match the approved issue scope
• Task sequencing and phase structure are clear
• No-backend rule satisfied throughout
• Vendor strategy (committed UMD bundle) follows project conventions

🤖 Generated with [Claude Code]((claude.com/redacted)

• Fixes [PROPOSAL] - QR Code Generator #22

Generated by Product Architect: Spec-Gen for issue #22 · ◷