القائمة
Frontend code review for src/web/. 3 parallel agents: performance, architecture, engineering. Supports diff mode. Trigger: "review web", "review frontend".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Mandatory Prismix browser verification for web UI changes. Use when modifying or reviewing frontend-rendered behavior, including src/web files, shared UI components, routes, layouts, CSS/Tailwind classes, visual assets, displayed i18n strings, browser auth flows, or frontend-visible API behavior.
Review and accept external modifications to the working tree (Codex, linters, collaborators). Diff, assess, flag issues. Trigger: "review changes", "review external", "check what changed".
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Backend code review for src/server/. 3 parallel agents: architecture, security+performance, engineering+scalability. Supports diff mode. Trigger: "review server", "review backend".
| name | review-web |
| description | Frontend code review for src/web/. 3 parallel agents: performance, architecture, engineering. Supports diff mode. Trigger: "review web", "review frontend". |
| metadata | {"argument-hint":"[diff] [performance|architecture|engineering]"} |
Audit src/web/ with 3 parallel agents. Plan only — no code changes. Output: docs/web-refactor-plan.md.
Modes: diff = only changed files vs main. Focus arg = single agent. Combinable: /review-web diff performance.
Scope: src/web/ only. Exclude src/web/components/ui/ from architecture (shadcn primitives). Grep-first, Read only for context.
Context (embed in each agent):
React 19 + Vite + TanStack Query v5 + react-hook-form + Zod + shadcn/ui + Tailwind v4. No SSR.
Rules: ts-pattern 3+ branches, lodash-es mandatory, @/shared/number.ts, draft/applied filter pattern,
DEFAULT_PAGE_SIZE from constants, useCallback for handlers, WalletAddress for addresses, SecretInput for secrets.
Grep-first. Check: inline arrows in JSX event props (re-renders), static page imports in app.tsx (no lazy), heavy libs loaded eagerly (recharts, monaco), TanStack Query hooks missing staleTime, duplicate queryKeys, from "lodash" without -es. Max 15 findings.
Glob large files first. Check: files > 400 lines (god components), switch( (ts-pattern violation), .sort(/new Set( (lodash-es), .toFixed( (number.ts), 3+ duplicated UI patterns without shared component, useState duplicating query data. Max 15 findings.
Grep-first. Check: : any/as any/@ts-ignore, from "@/server (cross-boundary), fetch( outside client.ts (raw fetch), "/api/ outside constants.ts (hardcoded URL), type="password" outside login (SecretInput), empty catch blocks, commented-out code. Max 15 findings.
Deduplicate → classify P0 (user-facing) / P1 (dev velocity) / P2 (tech debt) → if previous plan exists mark NEW vs RECURRING → write docs/web-refactor-plan.md → present summary, wait for confirmation.