Stats
Actions
Tags
From vivreal-infra
Use for anything about the Vivreal backend Lambdas at the AWS level — packaging/building/deploying them (failed deploy, "package too large", "template too large", adding a layer, arm64-layer crash, CI/CD, serverless-express/Node/Pino/X-Ray) OR concurrency/scaling/capacity (throttling/429s, "decreases unreserved below 100", reserved-concurrency values, "can we handle N users", the Mongo-connection ceiling). Routes you to references/deploy.md for packaging+deploy and references/scaling.md for concurrency+capacity. Covers all backends — SAM (VR_CMS_API/VR_Secure_API/VR_Main_API/VR_Client_API) and the Serverless-Framework outliers (VR_Client_Auth, Vivreal_EventHandler). Triggers on: deploy lambda, build:deploy, package too large, template too large, --s3-bucket, lambda layer, arm64 layer crash, Extension.Crash, FFmpeg layer, serverless-express, SAM deploy, GitHub Actions deploy, dogfood, Node 20, Pino, X-Ray, reserved concurrency, ReservedConcurrentExecutions, UnreservedConcurrentExecution, lambda throttling, 429, concurrency limit, scaling ceiling, put-function-concurrency, can we handle X users, Little's Law.
How this skill is triggered — by the user, by Claude, or both
Slash command
/vivreal-infra:vivreal-lambdaThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Cross-cutting Lambda knowledge shared by all Vivreal backends. For repo-internal route/service details, see the per-repo `*-knowledge` skills (`vivreal-knowledge` plugin). This skill is the AWS plumbing those repos share. It has two facets — read the one your task needs:
Cross-cutting Lambda knowledge shared by all Vivreal backends. For repo-internal route/service details, see the per-repo *-knowledge skills (vivreal-knowledge plugin). This skill is the AWS plumbing those repos share. It has two facets — read the one your task needs:
references/deploy.md.references/scaling.md.@codegenie/serverless-express (older docs say serverless-express), deployed as AWS Lambda behind API Gateway.VR_Client_Auth is Node 18.x — see vivreal-client-stack-knowledge.)logger.info(obj, 'event_name') — single-arg drops the message body (also a Sentry-ingestion regression signal; see sentry-tracer).hb-api-secrets injected at deploy/runtime — see vivreal-iam-secrets.main (prod) or dogfood (DEV). No manual deploy for a normal change — push the branch.| Repo | IaC |
|---|---|
| VR_CMS_API, VR_Main_API, VR_Client_API | AWS SAM |
| VR_Secure_API | AWS SAM (fragments → generated cloudYamls/allRoutes.yaml) |
| VR_Client_Auth | Serverless Framework (serverless.yml) |
| Vivreal_EventHandler | Serverless Framework + esbuild (state machine pushed separately — see vivreal-site-deploy-pipeline) |
vivreal-iam-secrets (deploy-role + secrets), vivreal-atlas-topology (the Mongo-connection ceiling that scaling defers to), vivreal-auth-architecture (the 403-on-new-route deploy-config miss). Sources of truth: each backend's C:\repos\<repo>\CLAUDE.md; memory project_lambda_concurrency_reallocation.md, project_admin_analytics_integration.md.
Provides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.
npx claudepluginhub hillbombcreations/vivreal-skills --plugin vivreal-infra