naiv-qr/AGENTS.md
Ole-Morten Duesund 8fa1809d9d Initial commit: Share-as-QR Firefox extension with bun build
MV3 WebExtension that turns the active tab's URL into a scannable QR
code via a toolbar popup. The popup runs locally — no network requests.

Build pipeline: `bun build` bundles popup.js + the vendored
kazuhikoarase/qrcode-generator (MIT, pinned to 83b7e8f) into a single
~23 KB minified ESM file under dist/. web-ext operates on dist/, so
the packaged zip contains only what actually ships (~28 KB).

Scripts:
- bun run build    — bundle + copy assets into dist/
- bun run lint     — build + web-ext lint (0 errors / 0 warnings)
- bun run package  — build + produce a signable .zip
- bun run start    — build + launch Firefox with the extension loaded

Tracks dogcat epic firefox-share-as-qr-35mw and its 5 child tasks
(scaffold, vendor lib, popup UI, icons, README).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-11 16:04:22 +02:00

6.6 KiB

DOGCAT WORKFLOW GUIDE

Rules

Run dcat prime after compaction, clear, or new session BEFORE writing any code for a new bug, feature, or change: ask the user if you should create an issue first. No exceptions for 'small' tasks — the rule exists for traceability, not because the task is complex. When creating or updating issues, write them so a fresh agent with no prior context can pick them up. Include the why, relevant file paths, error messages, and acceptance criteria — don't assume shared knowledge. When creating issues, set appropriate labels using --labels based on the issue content (e.g. cli, tui, api, docs, testing, refactor, ux, performance, etc.). Do NOT batch-mark an entire backlog as in_progress upfront. Mark each issue in_progress right when you start working on it. When running multiple dcat commands, make separate parallel tool calls instead of chaining with && and echo separators. Before setting in_review: verify your work and cite actual output.

Quick Start

Allowed issue types, priorities, and statuses: Types: bug, chore, epic, feature, question, story, task Priorities: 0 (Critical), 1 (High), 2 (Medium, default), 3 (Low), 4 (Minimal) Statuses: draft, open, in_progress, in_review, blocked, deferred, closed

dcat create and dcat update both support --title, --description, --priority, --acceptance, --notes, --labels, --parent, --manual, --design, --external-ref, --depends-on, --blocks, --duplicate-of, --editor

  1. Create: $ dcat create "Title" --type bug --priority 1 -d "Description"

  2. List issues: $ dcat list - All open issues $ dcat list <parent_id> - Children of a parent $ dcat ready - Ready to work (no blockers) $ dcat blocked - All blocked issues Use --namespace or --all-namespaces to filter.

  3. Update: $ dcat update --status in_progress

  4. Close: $ dcat close --reason "Fixed"

Essential Commands

dcat create