onedevatlasBeta
Browse the atlas
PersonIndependent

Theo Sun

8maintains3contributes to
GitHub@Soontao

Capabilities15

Provides 8
Async processingCAPAsync processingcapabilityDoing work outside the request that triggered it, with a guarantee that it eventually happens — deferred jobs, retries, and periodic work. Distinct from messaging, which is about telling other systems.AuthenticationCAPUI5AuthenticationcapabilityEstablishing who is calling: validating credentials or tokens, resolving the user, and making that identity available to the application. [Authorization](capability:authorization) decides what that identity may do; [identity provisioning](capability:identity-provisioning) manages its lifecycle across systems.Database connectorsCAPDatabase connectorscapabilityConnecting an application’s data model and queries to a database, including the differences in supported queries, types and schema management between database implementations. Changing an existing schema belongs to [schema evolution](capability:schema-evolution).Feature togglesCAPFeature togglescapabilityTurning behaviour on and off per tenant or per user at runtime, without redeploying, and knowing which toggles are live. System-level switches for delivered objects and runtime flags for unfinished features share the name.Rate limitingCAPRate limitingcapabilityCapping how many requests a service will accept per tenant or per caller, so one consumer cannot exhaust a shared deployment, whether enforced by a policy in front of the application or inside its own process.TelemetryCAPTelemetrycapabilitySeeing what a running service did — traces across handlers and database calls, metrics, and correlation that survives an async boundary.TypeScript patternsCAPTypeScript patternscapabilityHow an application is arranged once it is written in TypeScript — where handlers live, what registers them, and how business logic is kept apart from persistence. Distinct from typing, which is about the model being visible to the compiler; this is about the shape of the code around it.TypingCAPTypingcapabilityMaking the model visible to the compiler — generated types for entities and events so a rename breaks the build rather than production.
Contributes to 7
Agent guidanceCAPUI5Agent guidancecapabilityPackaged knowledge you hand a coding agent so it gets a framework right unprompted — skills, rule files, instruction packs. Distinct from agent tooling, which is about building agentic features into your application, and from [agent access to your code](capability:agent-code-access), where the agent reads the real project instead of being handed a file about it.AttachmentsCAPUI5AttachmentscapabilityStoring a file somebody uploaded next to the record it belongs to, and getting it back out — where the bytes actually live, who may read them, and what the UI shows while they are being scanned.LLM integrationCAPUI5LLM integrationcapabilityCalling a language model from application code with the tenant, destination and credential handling already solved instead using an SDK call with a hand-rolled key.ThemingUI5ThemingcapabilityApplying a consistent visual identity across every control, including the parameters an app may read and the custom themes an organisation may build.Touch operationUI5Touch operationcapabilityOperating an app with a finger, a stylus or a gloved hand on a tablet, kiosk or shop-floor terminal: targets large enough to hit, and input that does not assume a hardware keyboard. Distinct from responsive layout, which is about the width of the screen rather than what touches it.TypeScript supportUI5TypeScript supportcapabilityWriting apps and libraries in TypeScript — the type definitions, the module syntax the loader expects, and the build step that gets from one to the other.Web Components interopUI5Web Components interopcapabilityUsing standards-based custom elements inside an app, and the question of which control set an app should be built from at all, two concerns that are often answered as one.

Entries11

Group by11 of 11 entries
EntrySignals
Maintains8
cds-common-jwt-supportv0.0.2
Functional boundary

JWT authentication for CAP without xsuaa or xssec

cds-feature-togglev0.0.6
Functional boundary

Feature-toggle pattern for CAP CDS

cds-hyper-app-servicev6.1.0
Functional boundary

Typed class-based service layer over CAP ApplicationService

cds-internal-toolv1.7.9
Functional boundary

Reusable internals for authors of CAP extensions

cds-mysqlv7.9.0
Functional boundary

MySQL and MariaDB database adapter for CAP

cds-natsv2.10.1
Functional boundary

NATS messaging service for the CAP Node.js runtime

cds-rate-limitv0.0.6
Functional boundary

Rate-limit pattern for CAP Node.js applications

opentelemetry-cdsv0.1.4
none

OpenTelemetry support for the CDS Node.js runtime

Contributes to3
@ui5/webcomponentsv2.28.1
Functional boundary

SAP's UI elements as standard custom elements

cds2typesv3.0.1
none

CLI generating TypeScript interfaces from a CDS model

UI5 Web Components agent skills
Functional boundary

Two agent skills for accessibility and styling of web components

Details

History14
  • cds-common-jwt-supportlifecycle → retiredThe maintainer's GitHub profile states that the account was archived (profile changed 2026-10-11); the repositories are gone and the package stays published on npm. His words, quoted and dated, in the field made for a maker's statement about an end; nothing written about the person.
  • cds-feature-togglelifecycle → retiredThe maintainer's GitHub profile states that the account was archived (profile changed 2026-10-11); the repositories are gone and the package stays published on npm. His words, quoted and dated, in the field made for a maker's statement about an end; nothing written about the person.
  • cds-hyper-app-servicelifecycle → retiredThe maintainer's GitHub profile states that the account was archived (profile changed 2026-10-11); the repositories are gone and the package stays published on npm. His words, quoted and dated, in the field made for a maker's statement about an end; nothing written about the person.
  • cds-internal-toollifecycle → retiredThe maintainer's GitHub profile states that the account was archived (profile changed 2026-10-11); the repositories are gone and the package stays published on npm. His words, quoted and dated, in the field made for a maker's statement about an end; nothing written about the person.
  • cds-mysqllifecycle → retiredThe maintainer's GitHub profile states that the account was archived (profile changed 2026-10-11); the repositories are gone and the package stays published on npm. His words, quoted and dated, in the field made for a maker's statement about an end; nothing written about the person.
  • cds-natslifecycle → retiredThe maintainer's GitHub profile states that the account was archived (profile changed 2026-10-11); the repositories are gone and the package stays published on npm. His words, quoted and dated, in the field made for a maker's statement about an end; nothing written about the person.
  • cds-rate-limitlifecycle → retiredThe maintainer's GitHub profile states that the account was archived (profile changed 2026-10-11); the repositories are gone and the package stays published on npm. His words, quoted and dated, in the field made for a maker's statement about an end; nothing written about the person.
  • opentelemetry-cdslifecycle → retiredThe maintainer's GitHub profile states that the account was archived (profile changed 2026-10-11); the repositories are gone and the package stays published on npm. His words, quoted and dated, in the field made for a maker's statement about an end; nothing written about the person.
  • cds-mysqlalternative_to → artifact:cap-js-hanacap-js-cds-dbs is the repository the four SAP database services are published from, not one of them — its README says 'Each of the subfolders is published as individual npm module' — so nothing installs it and nothing is an alternative to it. The edge to @cap-js/hana, a package a project would add instead of this one, stands.
  • cds-internal-toollinks.repo → removed404 from the GitHub API. Found by the first full run of scripts/check-links.mjs — the citation had a checked date and nobody had re-read it.
  • cds-mysqllinks.repo → removed404 from the GitHub API. Found by the first full run of scripts/check-links.mjs — the citation had a checked date and nobody had re-read it.
  • cds-natslinks.repo → removed404 from the GitHub API. Found by the first full run of scripts/check-links.mjs — the citation had a checked date and nobody had re-read it.
  • cds-rate-limitlinks.repo → removed404 from the GitHub API. Found by the first full run of scripts/check-links.mjs — the citation had a checked date and nobody had re-read it.
  • First entry seenDiscovered via npm registry · keywords:cds, npm registry, The discovery pass.
For your agent
Ref
actor:theo-sun
JSON
/actors/theo-sun.json
MCP
Connecting an agent