aegis-dept-06-api-gateway
Coding standards, operational procedures, and engineering rules for AEGIS Department 6: Distributed Gateway Hubs & Cross-Service API Routers
SKILL.md.agents/skills/aegis-dept-06-api-gateway/SKILL.md
GitHubDepartment 6: Distributed Gateway Hubs & Cross-Service API Routers
Framework: White Caves Engineering Matrix V2 (1-12-108 Software Core)
Protocol: Bhakti 1-12-108
Director:@Ruchi— Principal API Platform Gateway Architect
Tech Stack: Express.js, REST, WebSocket (socket.io), TypeScript, Zod
9-Node Engineering Roster
| # | Agent | Role | Responsibility |
|---|---|---|---|
| 1 | @Ruchi (Director) |
Principal API Platform Gateway Architect | Designs unified edge routing distribution maps and public API entry gateways. |
| 2 | @Daniela |
Microservice Inter-Service Contract Specialist | Establishes RPC network connection parameters and message communication contracts. |
| 3 | @Mary_Meeker |
Network Payload Scaling Analyst | Monitors transaction request flows to dynamically scale internal gateway load bounds. |
| 4 | @Amy_Hood |
External Webhook Lifecycle Cost Specialist | Audits transaction API costs to guarantee optimized outbound request data weights. |
| 5 | @Susan_Wojcicki |
Content Delivery Network Routing Engineer | Configures edge network proxies to accelerate binary media payload delivery scripts. |
| 6 | @Meg_Whitman |
Container Microservice Node Orchestrator | Manages automated cluster rollover parameters during continuous delivery updates. |
| 7 | @Angela_Ahrendts |
Third-Party Platform Hook Protocol Designer | Standardizes ingress communication maps for handling external developer platform hooks. |
| 8 | @Sheryl_Sandberg |
Cross-Department Contract Alignment Coordinator | Harmonizes endpoint request-response interface properties across isolated codebase tracks. |
| 9 | @Kim_Swift |
High-Velocity Stream Processing Programmer | Optimizes event broadcasting message loops to maintain real-time web socket data syncs. |
Key Codebase Files & Directories
server/routes/server/middleware/server/services/src/utils/apiClient.ts
Mandatory Coding Rules
- API versioning: all public endpoints must be under /api/v1/ prefix
- Request/response contracts must be defined with Zod schemas
- Webhook handlers must validate signatures before processing payloads
- CDN: static assets must be served via edge with Cache-Control headers
- WebSocket: rooms must be scoped per-tenant — no cross-tenant data leaks
- Rate limiting: tier-based — 100/min for standard, 1000/min for premium
- CORS: whitelist only known origins — never use wildcard in production
- Payload compression: responses > 1KB must use gzip encoding
Standard Operating Procedures
API Contract Tests
npx vitest run server/routes/
WebSocket Load Test
npm run test:ws:load
OpenAPI Spec Validation
npx swagger-cli validate openapi.yaml
Aegis V4.1 Governance (All Departments)
- Single Purpose File Law: Every source file must have a single responsibility and remain under 350 lines.
- Canonical 5-Way File Standard: View (
.view.tsx), Logic (.logic.ts), Styles (.styles.ts), Data (.data.ts), Config (.config.ts). - TypeScript Strict: Zero warnings, zero
anybypasses, zero@ts-ignorecomments. - Continuous Deduplication: Zero duplicate handlers, zero ghost directories, zero redundant imports.
- Zero-Backlog Law: All PRs and issues must be resolved before moving to the next sprint.
- Token Preservation Shield: Hard 15,000 token ceiling per task — no runaway retry loops.
- Conventional Commits: All commits must follow
feat|fix|chore|refactor|test|docs(scope): messageformat.