qaio-desktop

Build Qaio App locally (macOS). Clean stale artifacts, pnpm tauri build, notarize DMG manually (Tauri skips), staple, verify, copy to ~/Desktop/Qaio-{version}.dmg. Fallback when CI broken.

Debug bugs in Qaio. NEVER guess. Read log files first (backend + frontend). Add targeted tracing/logger if not enough info. Never ask user to copy-paste terminal output.

Ship new Qaio version. Bump semver across all packages, tag, push, let CI build + sign + notarize. STOP at draft — user publishes manually. Defaults patch bump. Minor needs explicit user permission.

Process a batch of PDF or CSV bank and credit-card statements end to end: extract every transaction (parallel Haiku subagents), canonicalize the party names, categorize against your locked chart of accounts (parallel Sonnet subagents), detect inter-account transfers, and assemble a reviewed Google Sheets workbook with a formula-driven P&L. Reconciliation mismatches surface as warnings, low-confidence categorizations land in Suspense — I never invent an account code, never silently plug a number, never post to your accounting system.

Set up your books from scratch with one founder interview that captures entity, fiscal year, accounting method, registered accounts, payroll posture, revenue model, investor cadence, and tax preparer, then writes the live bookkeeping brief every other skill reads first. Sub-mode `mode=opening-balances` captures your opening trial balance from a spreadsheet, CSV, or prior-accountant export. I never connect a bank, post to a general ledger, or move money from this skill — facts and a brief, full stop.

Tell me the basics about your company so I can give you better legal help. I ask a few quick questions about your entity, cap table, contracts in force, templates, and any open risks. You only need to do this once, and I keep it updated as things change.

Tell me the basics about your company, your customer, and how you talk so I can give you better marketing help. I ask a few quick questions about your product, positioning, ideal customer, voice, and what you're selling right now. You only need to do this once, and I keep it updated as things change.

Tell me how your company actually runs so every other ops skill stops asking the same questions. I capture your priorities for the quarter, your operating rhythm, key contacts, vendor posture, hard nos, and voice into one living doc. You only do this once and I keep it updated as things change.

Set up the operational tracking you need so you're not flying blind. Pick what you need: a single metric I snapshot daily against your warehouse, or a full dashboard spec with sections, visualizations, cadence, and read-only SQL behind every chart. I draft the spec, you or your BI tool renders it.

Pull together panel feedback after an interview loop into themes, contradictions, rubric scores, and a hire / no-hire memo. You decide; I just give you the cleanest read of what the panel actually said.

Tell me how you do HR - values, leveling (IC and manager, L1-L5), comp bands, review-cycle rhythm, policy canon, escalation rules, voice, and hard nos - so I can give you sharp drafts and answers. This is the foundation doc every other people Action reads first.

Tell me the basics about your company, your ideal customer, your pricing stance, deal stages, and how you handle objections so I can give you better sales help. I ask a few quick questions and write the playbook every other skill reads first. You only need to do this once, and I keep it updated as things change.

Tell me the basics about your product, your customers, and how you handle support so I can give you better help. I ask a few quick questions about your product, response-time targets, VIP list, routing rules, and known gotchas. You only need to do this once, and I keep it updated as things change.