llamenos-hotline

Use when adding log statements, editing files that log, debugging log output, or reviewing PRs/code that touches logging. Enforces scoped structured logging (no console.*, no PII in logs, namespaces, createLogger/createDebugLog). Also use this when reviewing diffs — check for console.* usage, PII leaks in log extras, wrong logger primitive, or missing namespace conventions.

Orchestrate and run tests across all four suites (unit, integration, API E2E, UI E2E) with automatic service management, orphan process cleanup, worktree port tracking, and env validation. Use this skill whenever the user asks to run tests, check test health, verify changes work, or when you've completed implementation and need to validate. Also use proactively after any code change to verify it passes. Triggers on: "run tests", "check tests", "does this pass", "verify", "make sure tests pass", or after completing implementation steps.

Guide full-stack feature development with zod-validated schemas and OpenAPI-documented endpoints. Use this skill for ANY feature work that touches API endpoints, data types, or encrypted fields — including frontend components that consume API data. Trigger when adding new API endpoints, modifying route handlers, creating React Query hooks, building forms that submit to the API, working with encrypted fields (hub-key or envelope), creating or editing zod schemas, converting routes to @hono/zod-openapi, or adding new resource entities. Also trigger when the user mentions API validation, OpenAPI, Scalar docs, zod schemas, request/response types, shared types, or type duplication. This skill enforces the schema-first, single-source-of-truth pattern where all types are derived from zod schemas in @shared/schemas/ and used by both backend and frontend — no duplicate type definitions.

Write tests for the Llamenos project following established patterns, principles, and project conventions. Covers all four suites: unit, integration, API E2E, and UI E2E. Use this skill whenever writing new tests, adding test coverage, implementing features that need tests (all of them), or following TDD. Complements test-runner (which handles execution) and test-driven-development (which handles the red-green-refactor cycle). Triggers on: "write tests", "add tests for", "test coverage", "TDD", implementing any new feature or fix, or when a test file needs to be created or modified.