SmartRecruiters offer breakdown — generate India CTC salary breakdowns and formatted PDF offer letters for candidates in the SmartRecruiters recruiting workflow. Use when structuring compensation packages, calculating take-home salary, computing PF, HRA, Gratuity, or Professional Tax for Indian hires. Also use for side-by-side CTC comparison across multiple offer values (simulate mode) to support salary negotiation in SmartRecruiters. Triggers on: CTC calculation, India salary structure, offer letter India, SmartRecruiters offer, SR offer breakdown, HRA Metro Non-Metro, Employee PF, Employer PF, Gratuity 4.81%, Professional Tax, income tax old regime, aviation allowance, flight allowance, cabin crew salary, INR salary breakdown, India compensation structuring, offer letter PDF generation, CTC simulate, what-if salary, take-home comparison.

Generates ready-to-send .emltpl email files for Outlook on Mac. Use when the user asks to send, draft, compose, write, or prepare an email — or when any workflow produces output that needs to be emailed. Trigger phrases include: "send an email", "draft an email", "compose an email", "create an email to", "write an email", "prepare an email", "email this to", "forward this to".

Bootstrap off-stack ABAP Unit testing plus an abaplint static-analysis gate onto an abapGit-serialised ABAP repository, with no live SAP system. Use when you need to run a repo's existing ABAP Unit tests in CI (GitHub Actions) by transpiling serialised ABAP to JavaScript with the abaplint transpiler and open-abap-core and executing them on Node. Covers pinning the transpiler parse dialect to a specific SAP_BASIS release (e.g. v816), breaking a class-under-test free of heavy DDIC drag with a shim or factory seam, authoring minimal domain-less DDIC fixtures, a reproducible npm ci committed-lockfile setup, and wiring the off-stack unit-test job beside the abaplint lint job on every push and pull request. Triggers on "off-stack ABAP Unit", "transpiled ABAP Unit on Node", "abaplint transpiler CI", "run ABAP tests without a SAP system", "ABAP GitHub Actions unit tests", "abaplint new-repo bootstrap". Scope boundary is load-bearing: it verifies orchestration and pure-ABAP logic only; any class calling classic BAPIs, the database, or HTTP is shimmed and remains an on-stack ATC + ABAP Unit concern, and an off-stack green is CI-grade provenance, not an in-system verification.

Use when building business objects with the ABAP RESTful Application Programming Model (RAP): CDS view entity, behavior definition BDEF, behavior implementation ABAP class, managed RAP, unmanaged RAP, validation, determination, action, draft-enabled, service definition, service binding, OData V4, projection view, business object BO, S/4HANA BTP ABAP environment cloud development.