nijanthan-dev

Use when the user needs TaxMate Australia guidance for records and proof standards.

Use when the user wants a TaxMate Australia individual return prep pack, broad individual tax checklist, or full-runtime HTML handoff setup.

Execute TaxMate Australia repo PR closeout, local validation, and release delivery. Use when fixing or merging TaxMate Australia GitHub PRs, handling review comments, encoding repeated review lessons into validation checks/tests, running Gitleaks gates, merging Release Please PRs, verifying published tags/releases, or cleaning TaxMate worktrees/branches after release.

Use when the user asks for TaxMate Australia, Australian tax prep linked to ATO sources, or an unclear Australian tax topic.

Use when the user needs TaxMate Australia accountant-facing Excel workbook outputs from reviewed tax-prep data.

Use when the user needs TaxMate Australia accountant handoff packs, source bundles, manual-copy guidance, or print-first HTML handoff setup.

Use when the user needs TaxMate Australia guidance for ABN and business income or expenses.

Use when the user needs TaxMate Australia guidance for general CGT concepts and records.

Audit or change Prompt Better release packaging, installers, Homebrew formulae, release workflows, local Act validation, build metadata, SBOMs, checksums, attestations, or supported Go versions. Use for every packaging/release issue, review, fix, PR, or toolchain update.

Route explicit prompt compilation, lint, checkpoint, and local governance requests to the smallest PromptBetter MCP tool.

Use when designing, reviewing, migrating, or debugging Databricks data engineering projects, Lakeflow or Spark jobs, Declarative Automation Bundles, CI/CD, workspace isolation, Unity Catalog environment layout, notebook-heavy repos, testing gates, observability, service principals, OIDC, or production deployment workflows.

Guide ViewFoundry SwiftUI work before generator implementation. Use when Codex needs to plan or execute imagegen mockup to SwiftUI sandbox iterations, inspect simulator screenshots, verify primary-device pixels, update ViewFoundry references/templates, or keep future TypeScript-to-SwiftUI generation work inside the staged project contract.