Dot-Files

Pre-flight design review through JJ Philipp's lenses, applied before opening a Moov PR or while shaping a ticket. Use when about to open a PR on a moovfinancial repo (moov-money, events, transfers, card-gateway, notifications, frontend, infra, etc.), shaping a Linear ticket before coding, or self-reviewing a diff for design issues that would draw red-line review comments. Applies six durable principles — vocabulary-as-contract, resist invented machinery, events-as-spine, trust-as-verified-identity, smallest-viable-contract, reason-by-consequence — and outputs short lowercase questions in JJ's voice, not a checklist.

Make purchases using Ramp agent cards via browser checkout, then complete all transaction requirements (memo, tracking categories, receipt, trip). Use when asked to buy something with an agent card, make a payment using Ramp, spend from a fund, complete missing transaction items, or test the agent card payment flow. Also use when asked about agent card access, availability, or how to get started with Agentic Cards. Requires ramp CLI and browser-automation skill.

Guide a user through submitting a Ramp financing application via the CLI. Use when: "apply to ramp", "create application", "sign up for ramp", "submit a ramp application", "onboard a new business". Do NOT use for: existing account management, transaction queries, or receipt uploads.

Review and approve pending transactions, bills, reimbursements, and requests. Use when: 'approve', 'pending approvals', 'what needs my approval', 'review transactions', 'approve bills', 'reject', 'approval queue', 'clear my approvals'. Do NOT use for: transaction analysis, receipt uploads, or spend tracking.

Automate Google Chrome for web tasks — navigate sites, fill forms, click elements, take snapshots, and extract content. Powered by playwright-cli (pw) with a persistent browser profile. Use when asked to interact with a website, fill out a checkout form, scrape content, or perform any browser-based workflow.

Go engineering style guide for designing packages, services, and CLIs. Use for new Go code, refactors, reviews, API design, error and logging patterns, config and constructor decisions, testing, and benchmarks.

Find your transactions missing receipts and upload them. Use when: 'missing receipts', 'receipt compliance', 'upload receipt', 'attach receipt', 'receipt sweep', 'transactions without receipts'. Do NOT use for memo/coding/fund cleanup (use transaction-cleanup) or approving transactions (use approval-dashboard).

Submit an out-of-pocket reimbursement from a receipt. Use when: 'submit reimbursement', 'reimburse me', 'I paid out of pocket', 'expense a receipt', 'file reimbursement', 'OOP expense', 'I bought something for work'. Do NOT use for: approving reimbursements (use approval-dashboard), uploading receipts to card transactions (use receipt-compliance), or editing existing reimbursements.

Write tests for requested code changes and validate affected packages.

Complete missing items on your transactions — memos, accounting categories, funds, and attendees. Use when: 'add memo', 'categorize transactions', 'missing items', 'transaction cleanup', 'fix my transactions', 'set tracking category', 'assign to fund', 'bulk memo update'. Do NOT use for: receipt uploads (use receipt-compliance) or approvals (use approval-dashboard).

Upload vendor documents such as W-9/W-8 tax forms, contracts, COIs, payment instructions, and onboarding paperwork, then check bulk upload OCR and matching status. Use when: 'upload a W9', 'attach a vendor contract', 'bulk upload supplier docs', 'check vendor document status', 'upload a COI for a vendor'. Do NOT use for card transaction receipts (use receipt-compliance) or bill invoice attachments (use bills commands).