Fab2295

@fab2295 source repo

5 skills
0 followers
8 hours ago last updated

▌
Sap Rap Dev · fab2295 bundle
SAP ABAP RESTful Application Programming Model (RAP) development skill. End-to-end scope: business objects (BO), CDS data model, behavior definitions and implementations, service definitions / bindings, file uploads/downloads, metadata extensions, value helps, and RAP testing. Use when the user asks to: build a RAP BO (managed or unmanaged), model CDS view entities / table entities / projection views, write a behavior definition / behavior pool, expose a service via a service definition + binding (OData V4 by default), extend an SAP-delivered RAP BO via metadata / behavior extension, consume a RAP BO via EML, add `@Semantics.largeObject` stream properties for file upload/download, define value helps, test a RAP BO, or add `@UI.*` / `@Search.*` / `@Consumption.*` annotations. STRICT SCOPE — THIS SKILL DOES RAP, AND ONLY RAP. It MUST refuse, with an explicit message, every request outside this scope: - SAP CAP (Node.js or Java) — use `sap-cap-nodejs-dev` or the CAP-Java skill. - Classic ABAP frameworks (BOPF, F

0
installs
▌
Sap Cap Test · fab2295 bundle
Test-only skill for SAP CAP Node.js projects. Its sole purpose is to scaffold and run automated tests using `cds test` (Node.js test runner wrapper) and, when (and only when) explicitly requested by the user, produce coverage with `c8`. The skill writes test files under `test/` (or the project's existing test folder), executes them, and emits two possible report files at the project root: - `CAP-TEST-REPORT.md` — successful run summary (always) - `CAP-TEST-FAILURE.md` — failure report (only if a test fails) Use when the user asks to: - "cria testes", "gera teste para X", "scaffold tests" - "roda os testes", "executa cds test", "run tests" - "testa o serviço X", "cobertura c8" (coverage mode — must be explicit) Strict negatives — this skill NEVER: - edits production code (`srv/**`, `db/**`, `app/**`, `package.json`, `.cdsrc.json`, `mta.yaml`, `xs-security.json`) — it only writes inside the test folder - implements features, refactors, fixes bugs, changes business logic - runs `git add`, `git commit`, `git push

0
installs
▌
Sap Cap Upgrade · fab2295 bundle
Upgrade SAP CAP and SAP-related libraries (@sap/cds*, @cap-js/*, @sap-cloud-sdk/*, @sap/eslint-plugin-cds) in the current working directory. Strategy: latest stable including majors. Runs `cds build` + `npm test` (when present), cross-checks failures against locally mirrored official changelogs (CAP + Cloud SDK JS) and reports ONLY bugs caused by the version bump. Use when the user asks to "upgrade CAP libs", "atualiza CAP", "bump @sap/cds", or similar. Read/upgrade only — never edits source code, never commits, never pushes.

0
installs
▌
Sap Cap Nodejs Dev · fab2295 bundle
SAP Cloud Application Programming Model (CAP) development skill for the **Node.js runtime only**. Domain-first: prefers CDS schema, annotations, projections, and CAP's generic providers over hand-written handler code ("less code → less mistakes"). Use when the user asks to: build CAP applications, define CDS models, design entities / associations / views / projections, add annotations (validation, authorization, UI, search, drafts), configure databases (SQLite / HANA / PostgreSQL through CAP), deploy to SAP BTP (Cloud Foundry or Kyma), wire multitenancy / messaging, or add CAP plugins. Strict scope — this skill ONLY develops SAP CAP Node.js. It MUST refuse, and tell the user why, whenever a request is: - Frontend / UI implementation (Fiori Elements custom code, UI5 controls, React, Vue, HTML/CSS/JS UI work, any browser-side code). CAP-side `@UI.*` annotations in `.cds` are in scope; writing the UI itself is not. - Backend in any other language or stack (Java CAP, Spring, plain Node/Express, NestJS, Python, Go

0
installs
▌
Sap Cap Code Review · fab2295 bundle
Read-only static analysis of SAP CAP Node.js code (a Pull Request, a branch comparison, or a specific file list). Classifies findings as Critical / High / Medium / Low, lists each finding with file:line, function/class, evidence and a *suggested* fix (always flagged as needing human validation), and writes the result to `CAP-CODE-REVIEW.md` at the project root. Use when the user asks to: - "analisa o PR", "code review CAP", "revisa o PR", "analise de código CAP" - "compara branch X com Y" (CAP project) - "revisa esses arquivos do CAP" Strict negatives — this skill NEVER: - generates code, fixes bugs, refactors, edits any source file - creates new projects, scaffolds anything - runs `git commit`, `git push`, `git add`, or any git mutation - touches anything outside the chosen analysis scope - makes any claim that is not anchored in capire docs (in `references/`) Scope: SAP CAP Node.js only. If the project is Java CAP, generic Node.js, or non-CAP, the skill must refuse with an explicit message.

0
installs

5 published skills