Use when a new broker needs to be added to IRS Helper. Accepts a broker tax statement (PDF, XLSX, or CSV) and orchestrates the full workflow: analysing the file, mapping income types to IRS annex tables, producing an implementation plan, and delegating coding to the developer. Trigger phrases: 'add broker', 'new broker', 'support broker', 'integrate broker', 'broker PDF support', 'broker XLSX support'.
Use when implementing new features, modifying existing code, fixing bugs, adding tests, or improving coverage in the IRS Helper codebase. This is the primary coding skill for all React, TypeScript, and service worker changes. Trigger phrases: 'add feature', 'implement', 'modify', 'fix bug', 'refactor', 'add tests', 'update component', 'new parser', 'change behavior', 'cover with tests'.
Use when the task involves parsing, extracting, or validating data from broker tax statements in any format — PDF (XTB, Trade Republic, Trading 212, ActivoBank, Freedom24, IBKR), XLSX (Binance), or CSV (DEGIRO). Covers understanding how raw file values become IRS table rows, debugging regex or extraction patterns, adding a new broker parser, or validating that extracted rows are correct before XML injection. Trigger phrases: 'parse PDF', 'parse XLSX', 'parse CSV', 'broker PDF', 'broker file', 'extract from file', 'parser', 'pdfParser.ts', 'binanceXlsxParser.ts', 'degiroCsvParser.ts', 'rows not extracted', 'missing rows', 'wrong values', 'add broker', 'new broker support', 'validate parsed data'.
Use when questions involve Portuguese IRS Annex G or Annex J filling rules, field codes, income codes, country codes, capital gains reporting, dividends, interest, CFDs, or how data from international brokers (XTB, Trade Republic, Trading 212, ActivoBank, Freedom24 or others) maps to IRS declaration tables. Trigger phrases: 'which annex', 'which table', 'which code', 'Quadro 8A', 'Quadro 9.2', 'Anexo G', 'Anexo J', 'IRS filling', 'income code', 'country code', 'broker PDF', 'capital gains Portugal', 'dividends IRS'.
Use when implementing or reviewing frontend features to keep UI/UX consistent with the established design system, avoid interaction inconsistencies, and validate wording, translations, and user-facing documentation. Trigger phrases: 'UI consistency', 'UX review', 'design consistency', 'frontend UX', 'wording', 'copy review', 'translation review', 'i18n text', 'documentation clarity', 'component behavior', 'accessibility UX'.