Testing & Development Skills

Optimizes API performance through query optimization, caching strategies, and connection pooling. Profiles slow queries with EXPLAIN ANALYZE, identifies N+1 patterns in Drizzle queries, adds caching layers (Workers KV or Redis), tunes connection pool settings, and implements response compression.

Runs integration tests, contract tests against the OpenAPI spec, and load tests using k6. Validates that the API implementation matches the specification, meets performance requirements, and handles concurrent load. Produces a comprehensive test report.

Zod schemas and request/response validation middleware for Hono APIs. Generates Zod schemas from Drizzle tables using drizzle-zod, creates request validation middleware for body, query params, and path params, adds response validation in dev/test mode, and attaches OpenAPI metadata to Zod schemas.

Generates deployment configuration based on the target platform specified in build-spec.json. For Cloudflare Workers, generates wrangler.toml with bindings. For Node.js, generates Dockerfile and docker-compose.yml with PostgreSQL. For AWS Lambda, generates a SAM template (API Gateway HTTP API), esbuild bundling config, and an OIDC deploy workflow. Always generates GitHub Actions CI/CD workflow and .env.example.

Generates Hono route handlers, service layer, and middleware that make the failing tests from Phase 2 pass. Reads build-spec.json for the endpoint inventory, creates route files with proper typing, implements business logic in a service layer, wires up Drizzle queries, and adds Zod validation middleware. Tests are run after each route group to confirm GREEN.

Parses OpenAPI 3.x specifications (YAML or JSON) or conducts a structured interview to generate one from scratch. Produces a canonical build-spec.json that drives all downstream pipeline phases. Use this skill at the very start of any new API project, when the user supplies an OpenAPI file, or when they want to describe an API conversationally.

Writes failing integration tests BEFORE route handlers exist, following strict test-driven development. For every endpoint in build-spec.json, generates Vitest integration tests covering happy paths, validation errors, auth requirements, and edge cases. Tests must be confirmed RED before Phase 3 proceeds. This is a hard gate in the Nerva pipeline.