// Use when adding or editing Nango database migrations - covers migration directory selection, timestamped .cjs naming, matching recent migration style, down migration decisions, and foreign key ON DELETE conventions.
Use when creating new agent skills or improving existing ones - ensures skills are discoverable, scannable, and effective through proper structure, discovery optimization, and real examples
Use when modifying or visually debugging Nango frontend UI, including packages/webapp, packages/connect-ui, browser interactions, screenshots, and visual regressions. Prefer browser-controlled or headless Playwright checks; use Peekaboo only for native macOS, visible-browser, or Accessibility tree inspection.
Use when adding documentation for a new Nango integration - creates main page, setup guide, and updates docs.json and providers.yaml following established patterns
Use when running the Nango application locally for development and browser testing - covers Docker services, dev commands, service URLs, and troubleshooting startup issues
Use when building the Nango monorepo or verifying TypeScript compilation - covers build commands, project references, common tsc errors, and package dependency order
Use when running tests in the Nango monorepo - knows unit vs integration configs, vitest commands, Docker setup, and common test patterns
| name | creating-database-migrations |
| description | Use when adding or editing Nango database migrations - covers migration directory selection, timestamped .cjs naming, matching recent migration style, down migration decisions, and foreign key ON DELETE conventions. |
Identify the right migration directory.
packages/database/lib/migrations/.Before writing a migration, read 2-3 recent migrations in the same directory and follow their style.
Name new main database migrations with the timestamped CommonJS format:
<YYYYMMDDHHMMSS>_<description>.cjs
Example:
20260420120000_create_customer_keys.cjs
Decide exports.down explicitly.
exports.down should be left empty.Choose foreign key delete behavior from the relationship:
ON DELETE CASCADE for ownership relationships where the child cannot exist without the parent.ON DELETE SET NULL for optional references where the child should survive parent deletion..cjs migration format.exports.down behavior was confirmed or explicitly requested.CASCADE for ownership and SET NULL for optional references.