Use when implementing email and password auth or tuning session behavior in Better Auth. Covers sign-up and sign-in flows, password reset boundaries, cookie-backed sessions, refresh policy, cache strategy, stateless mode, and session-sensitive security tradeoffs.
Use when integrating Better Auth with Next.js App Router or Pages Router. Covers toNextJsHandler, auth route mounting, client setup, RSC and server action boundaries, proxy or middleware-based protection, and session checks across modern Next.js versions.
Use when setting up Better Auth for the first time or routing Better Auth work to the right follow-up skill. Covers package installation, secrets, base URL, auth handler mounting, client creation, and plugin-aware setup decisions.
Use when extending Better Auth with plugins, especially organization management and enterprise SSO. Covers plugin wiring on server and client, CLI migration flow, organization roles and access control, and deciding when SSO or organization plugins belong in the auth design.
Use when configuring social sign-in or provider-based OAuth flows in Better Auth. Covers social provider config, signIn.social, account linking, provider access tokens, generic OAuth, custom scopes, profile mapping, and redirect handling.
Use when a docs page is unclear because it mixes too many purposes. Covers choosing one primary doc type, separating tutorial, how-to, reference, and explanation content, and restructuring technical docs around reader intent.
Choose the right Drizzle ORM driver and runtime integration. Use when tasks mention drizzle-orm/node-postgres, neon-http, mysql2, better-sqlite3, @libsql/client, PGlite, Bun SQL, Cloudflare D1, Durable Objects, Expo SQLite, OP-SQLite, AWS Data API, serverless/edge runtimes, or Drizzle HTTP proxy setup.
Set up Drizzle ORM, choose the right Drizzle package surface, and route Drizzle work to the correct follow-up skill. Use when tasks mention Drizzle installation, first-time setup, drizzle-orm, drizzle-kit, drizzle.config.ts, version selection, upgrading to the v1 beta line, validator-package import moves, or deciding…
Use when triaging GitHub issues or incoming bug reports. Covers fast issue review, category and state decisions, codebase context gathering, next-action recommendations, and preparing issues for implementation without jumping straight into code.
Use when exploring a codebase for architectural improvement opportunities. Covers finding shallow modules, identifying bad seams, proposing deeper boundaries, and turning structural friction into concrete refactor candidates.
Use when planning a refactor before implementation starts. Covers scope clarification, alternatives, testing strategy, tiny-commit sequencing, and writing a refactor plan that stays durable even if the code layout changes.
Use when configuring a repo to enforce Conventional Commits locally without making commit flow annoying. Covers commitlint, Husky commit-msg hooks, minimal config choices, and the rule that semantic commits should improve history quality, not add ceremony.
Use when setting up pre-commit automation in a JavaScript or TypeScript repo. Covers Husky, lint-staged, formatter setup, package-manager-aware hook commands, and keeping commit-time checks realistic.
Use when investigating a bug before fixing it. Covers fast diagnosis, root-cause tracing, narrowing repro paths, checking adjacent code and tests, and producing a concrete fix plan instead of guessing.
Use when a feature needs a real implementation spec before coding starts. Covers goal and success criteria, user-facing behavior, boundaries, non-goals, edge cases, acceptance checks, and the rule that the spec should remove implementation guesswork instead of just sounding thorough.
Use when writing or reviewing a commit message and the real challenge is choosing the correct Conventional Commit type, scope, and summary based on change intent. Covers commit splitting, amend vs new commit decisions, and avoiding vague or misleading commit titles.
Use when implementing authentication or OAuth flows in Fastify, especially authorization code with PKCE, login callbacks, token validation, refresh handling, session or cookie boundaries, and protected route hooks.
Use when building, organizing, or debugging Fastify applications. Covers plugins, routes, schemas, hooks, errors, auth boundaries, logging, testing, and deployment decisions for Fastify backends.
Use DynamicIcon, Lucide Lab, or custom iconNode data in React with the right tradeoffs. Use when tasks mention lucide-react/dynamic, DynamicIcon, icon names coming from a CMS or database, @lucide/lab, the Icon component, custom Lucide nodes, or loading icons outside the core Lucide set.
Set up lucide-react, choose the right import pattern, and route icon work to the right Lucide follow-up skill. Use when tasks mention lucide-react, Lucide installation, icon imports, SVG props, absoluteStrokeWidth, import aliases like HouseIcon or LucideHouse, or deciding whether to use direct imports, DynamicIcon, or…
★not rated 2 5mo agoA92 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: