Generate code using nx generators. INVOKE IMMEDIATELY when user mentions scaffolding, setup, structure, creating apps/libs, or setting up project structure. Trigger words - scaffold, setup, create a ... app, create a ... lib, project structure, generate, add a new project. ALWAYS use this BEFORE calling nxdocs or…
Import, merge, or combine repositories into an Nx workspace using nx import. USE WHEN the user asks to adopt Nx across repos, move projects into a monorepo, or bring code/history from another repository.
Find and add Nx plugins. USE WHEN user wants to discover available plugins, install a new plugin, or add support for a specific framework or technology to the workspace.
Helps with running tasks in an Nx workspace. USE WHEN the user wants to execute build, test, lint, serve, or run any other tasks defined in the workspace.
Explore and understand Nx workspaces. USE WHEN answering questions about the workspace, projects, or tasks. ALSO USE WHEN an nx command fails or you need to check available targets/configuration before running a task. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?', 'What depends on…
The strategic authority for LenserFight. Translates ambiguous requests into product decisions, scope cuts, acceptance criteria, and implementation priorities.
Review React Native and Expo Go code changes for mobile performance, memory usage, CPU pressure, battery impact, network efficiency, and behavior under stressful real-world conditions. Use when reviewing apps/mobile, libs/ shared with Expo, or any React Native component, hook, navigation flow, screen, Expo module, API…
Review React and Vite web app code changes for browser performance, memory usage, CPU pressure, bundle size, network cost, rendering speed, hydration cost, and behavior under high traffic, slow devices, weak networks, and large datasets. Use when reviewing apps/web, libs/ used by the web app, or any React component…
Review whether a change set is ready for release across code, migrations, tests, docs, and rollout planning. Use before production releases, high-risk merges, or milestone sign-off.
Audit Nx monorepo structure, layer responsibilities, dependency drift, public APIs, and misplaced logic. Use for architecture review, library placement, boundary erosion, duplication, and repo health checks.
Enforce performance-safe query and rendering patterns across this Nx monorepo. Use when working on Vite freezes, Supabase overfetching, pagination, caching, CPU hotspots, memory pressure, or large seeded datasets.
Review repositories, cache behavior, data-access boundaries, and error mapping. Use when persistence code becomes leaky, caching is suspicious, or feature code reaches into transport/storage details.
Detect staged and unstaged git changes, classify them by type (feat/fix/refactor/docs/chore/test/style/perf), group into logical commit units, then commit each group separately with user approval. Use when the user wants to commit their current work, wants help writing a commit message, or says /commit or…
Review Supabase SQL functions, RPC exposure, return contracts, and API-facing database surfaces. Use for public API design, function hardening, response stability, and deciding between direct table access and RPC.
Review Postgres indexes, triggers, write amplification, and performance risk in Supabase migrations. Use for slow queries, missing indexes, trigger-heavy designs, stale propagation issues, and DB-side performance tuning.
Review Tailwind-based UI for consistency, accessibility, responsiveness, interaction states, and maintainability. Use for design system drift, component polish, UX quality, or accessibility review.
Guard shared UI contracts across web and mobile in lenserfight. Use when editing libs/ui, shared components, design tokens, hooks, or platform-specific entrypoints such as index.ts and index.native.ts.
Plan test coverage by layer, risk, and behavior. Use when adding features, fixing regressions, or deciding what to test in domain, data, UI, and integration layers.
Review and improve automated tests for NestJS modules, contracts, and critical flows. Use when changing services, controllers, guards, repositories, billing, wallet, execution, or auth behavior.
Review Vite app performance, bundle shape, route splitting, assets, rendering cost, and caching strategy. Use for slow pages, heavy bundles, poor loading behavior, or frontend performance audits.