Use after implementing a change and before committing/PR. Reviews the current diff for correctness, security, database pitfalls (Postgres/Drizzle or MongoDB), TanStack Query cache bugs, and Next.js mistakes. Read-only; returns findings ranked by severity.
Use for anything data-fetching or mutation related in the client - wiring TanStack Query (queryOptions/mutationOptions factories, key design, SSR prefetch + hydration, invalidation, optimistic updates), migrating useEffect-fetch code to Query, or fixing stale/refetch bugs. Writes code and verifies it.
Use when designing or changing database schemas - new tables/collections, relations, embedding vs referencing, index strategy, migrations, or fixing slow queries. Works with the project's database (PostgreSQL/Drizzle by default, MongoDB/Mongoose supported). Read-only advisor; returns a schema design with indexes and…
Use when a bug's cause is unknown - wrong data on screen, failing request, crash, or flaky behavior in a Next.js + TypeScript app on Postgres/Drizzle or MongoDB. Traces the bug to root cause across UI, API, service, and DB layers. Read-only; reports the cause and a proposed fix, does not change code.
Use before implementing any non-trivial feature. Turns a feature request into a concrete fullstack implementation plan (Next.js + TypeScript + Postgres/Drizzle or MongoDB) — data model, API surface, UI components, and test plan. Read-only; returns a plan, never writes code.
Use to add or extend tests for a feature or bug fix in a Next.js + TypeScript app on Postgres/Drizzle or MongoDB. Writes Vitest tests for services, schemas, and components; runs them until green.
Conventions for Next.js route handlers, server actions, Zod validation, and service-layer design. Use when adding or changing any API endpoint, server action, or backend service function.
Adding authentication and authorization to a Next.js app (Postgres/Drizzle or MongoDB) - Auth.js setup, session checks, protecting routes/actions/handlers, and role-based access. Use when implementing login, signup, sessions, or permissions.
Conventions for React components in Next.js App Router - server vs client split, props contracts, Tailwind styling, and async UI states. Use when building or restructuring UI components.
Deployment checklist for Next.js apps - Vercel or Docker/Node hosting, hosted Postgres (Neon) or MongoDB Atlas, env management, and production readiness. Use when shipping an app to production or setting up CI.
Conventions for Mongoose schemas, models, indexes, and queries in TypeScript. Use when creating or changing a MongoDB collection, writing queries, or debugging query performance.
The data layer for every app - TanStack Query v5 for all client-side reads and writes. queryOptions/mutationOptions factories, query key design, Next.js App Router prefetch + hydration, mutations, invalidation, and optimistic updates. Use whenever a component reads data, writes data, or a cache goes stale.
Testing strategy and Vitest conventions for Next.js + TypeScript apps on Postgres/Drizzle or MongoDB - what to test, how to test services against a real in-process database, and component testing. Use when writing tests or setting up test infrastructure.
Bootstrap a new fullstack web app with Next.js (App Router), TypeScript, PostgreSQL/Drizzle (default) or MongoDB/Mongoose, TanStack Query, shadcn/ui, Tailwind, Zod, and Vitest. Use when starting a new project or when the user says "new app", "scaffold", or "set up a project".
Use to implement a planned feature end-to-end in a Next.js + TypeScript app (Postgres/Drizzle default, MongoDB supported) - schema, service, server action, TanStack Query data layer, and UI. Give it a concrete plan or ticket; it writes code, runs typecheck/lint/tests, and reports what it built.
Conventions for PostgreSQL with Drizzle ORM in TypeScript - schema definitions, relations, indexes, migrations with drizzle-kit, and query patterns. Use when creating or changing a Postgres table, writing queries, or debugging query performance. (Mongo projects use mongodb-data-modeling instead.).
★not rated 4 1mo agoA62 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: