| name | zoolanding-lambda-workflow |
| description | Zoolanding Lambda workflow for quick stats updates in S3. Use when changing request validation, operation application, optimistic concurrency, tests, local harness behavior, or SAM deployment for zoolanding-quick-stats-lambda. |
| user-invocable | true |
Zoolanding Lambda Workflow
Use this skill for work in the quick-stats Lambda.
Repo Focus
- The contract is operation-driven:
set, inc, delete, merge, append.
- The persisted object is
appName/stats.json in S3.
- This repo owns the Lambda behavior; the frontend repo owns cross-platform integration context.
Workflow
-
Read the contract first.
- Start with
README.md and instructions.md.
-
Keep operation semantics stable.
- Unknown ops and invalid payload shapes should fail clearly.
dryRun, createIfMissing, and ifMatchEtag should stay behaviorally explicit.
- Preserve ordering of
ops application.
-
Prefer focused changes.
- Modify
apply_op or handler flow only where the requested behavior requires it.
- Avoid broad rewrites that blur operation semantics.
-
Verify with tests first when practical.
- Run the unit tests under
tests/ for operation behavior.
- Use
python .\\local_test.py for a handler-level local harness when needed.
-
Keep deployment and docs aligned.
- If env vars, response shape, or API behavior changes, update the docs with the code.
Recommended Repo-Local Skills
- Pair this workflow with the repo-local
karpathy-guidelines skill for scoped implementation, systematic-debugging for root-cause analysis, risk-review for review-only asks, and test-driven-development for behavior-changing code.
- Use the repo-local
zoolanding-pr-followup skill for CI, reviewer, and merge-readiness work.
- For shared workspace customization audits or consolidated cross-repo summaries, use the community prompts Workspace AI Customization Audit and Workspace Change Summary.
- Use the repo-local
zoolanding-production-readiness agent for deploy-gate review and the repo-local zoolanding-config-platform-audit agent when a change may require coordinated updates in the frontend or sibling services.
- Use the repo-local
sam-deploy-check prompt before shipping contract or SAM changes.
Resources