| name | context |
| description | Loads Serverless OpenClaw project context. Provides background knowledge needed for development including project overview, tech stack, architecture decisions, and data models. |
| user-invocable | false |
Serverless OpenClaw Project Context
This skill provides core project context. It is automatically referenced during implementation tasks.
Project Overview & Key Decisions
See PRD.md for details:
- Project definition, goals, tech stack
- 7 key architecture decisions with rationale
- Monorepo structure (6 packages: cdk, gateway, container, lambda, web, shared)
- DynamoDB 5-table schema
- Core data flows
Phase Status
| Phase | Status |
|---|
| Phase 0 (docs + setup) | Complete |
| Phase 1 (MVP — Fargate + Web + Telegram) | Complete (10/10) |
| Phase 2 (Lambda agent migration) | Complete |
AGENT_RUNTIME feature flag: fargate | lambda | both (current default)
Test coverage: 233 unit tests + 35 E2E tests = 268 total
Critical Constraints (Must Follow During Implementation)
- No NAT Gateway — Use Fargate Public IP + VPC Gateway Endpoints
- No secrets on disk — Secrets Manager → environment variables only. Never write API keys/tokens to
openclaw.json
- Telegram webhook-only — Long polling not allowed (API mutually exclusive)
- Bridge Bearer token required — Authentication on all endpoints except
/health
- IDOR prevention — userId determined server-side (JWT/connectionId reverse lookup). Ignore client input
- RunTask API — Use
capacityProviderStrategy only. Cannot specify launchType simultaneously
- Cost target — ~$1/month. No ALB, Interface Endpoint, or NAT Gateway creation allowed
Related Documents
