catatz

Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.

Use structured self-debugging when an agent loops, stalls, drifts, or repeatedly fails.

Baseline coding conventions for naming, readability, immutability, and code-quality review.

Use current primary documentation for library, framework, API, and setup questions.

Use Playwright for CatatZ critical flows, async Server Components, artifacts, and CI E2E tests.

Frontend patterns for React, Next.js, state management, performance, and UI implementation.

Library reference for Next.js 16 Turbopack development and webpack compatibility.

Translate product intent into explicit engineering constraints and implementation-ready capability plans.

Use for authentication, input, secrets, endpoints, uploads, and sensitive financial-data changes.

Use manual context compaction at logical boundaries in long multi-phase tasks.

Use for PostgreSQL performance, query, schema, RLS, and database configuration reviews.

Use for CatatZ tasks involving Supabase database, auth, SSR, RLS, storage, migrations, CLI, or client libraries.

Use test-first development for new features, bug fixes, and refactors.

Run CatatZ build, type, lint, test, security, and diff verification before completion.

Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector).