jaem1n207

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.

Internationalize JavaScript apps with i18next. Use when adding translations, handling plurals, loading locale files dynamically, or i18n for React/Vue/Node.

Perform thorough code reviews with actionable, prioritized feedback. Use when a user asks to review code, check code quality, find bugs, review a pull request, audit code for issues, or get feedback on implementation. Covers correctness, security, performance, readability, and best practices across languages.

Scan code for security vulnerabilities, misconfigurations, and exposed secrets. Use when a user asks to audit security, find vulnerabilities, check for OWASP issues, scan for secrets, review dependencies for CVEs, detect SQL injection, find XSS vulnerabilities, or harden an application. Covers OWASP Top 10, dependency auditing, secrets detection, and generates fix recommendations with severity ratings.

ESLint is the standard linting tool for JavaScript and TypeScript projects. It statically analyzes your code to find problems, enforce coding conventions, and catch bugs before they reach production. ESLint 9 introduced the flat config format, replacing the legacy `.eslintrc` system with a simpler, more composable `eslint.config.js` file. With a rich plugin ecosystem covering React, TypeScript, accessibility, and import ordering, ESLint is the backbone of code quality in modern web development.

Build cross-browser extensions with WXT — the modern framework for Chrome, Firefox, Safari, and Edge extensions. Use when someone asks to "build a browser extension", "Chrome extension with React", "WXT framework", "cross- browser extension", "manifest v3 extension", "build Firefox extension", or "browser extension with TypeScript". Covers content scripts, background workers, popup/options pages, storage, messaging, and publishing.

Audit web pages and components for WCAG 2.2 accessibility compliance. Use when a user asks to check accessibility, find a11y issues, audit for WCAG compliance, fix screen reader problems, check color contrast, ensure keyboard navigation works, or prepare for accessibility regulations like the European Accessibility Act or ADA.

Write and maintain end-to-end tests with Playwright. Use when someone asks to "add e2e tests", "test my web app", "set up Playwright", "write browser tests", "test login flow", "visual regression testing", "test across browsers", or "automate UI testing". Covers test setup, page objects, authentication, API mocking, visual comparisons, and CI integration.

Create domain components following bendd.me's directory structure, barrel export pattern, and validation conventions. Use when adding new React components, creating Zustand stores, setting up hooks, or organizing component files. Triggers on: new component, create component, add hook, Zustand store, barrel export, index.ts, domain folder. NOT for React composition patterns like compound components or render props (use vercel-composition-patterns). NOT for MDX components (use mdx-authoring).

Work with bendd.me's content pipeline — MDXProcessor queries, content directory management, article listing, and static generation. Use when querying articles, filtering content, working with generateStaticParams, modifying route handlers, or understanding the content-to-page pipeline. Triggers on: MDXProcessor, getArticles, formatForDisplay, sortByDateDesc, filterByCategory, generateStaticParams, article route, craft route, content pipeline, static generation. NOT for writing MDX content (use mdx-authoring).

Write, validate, and register MDX components and content for bendd.me blog. Use when creating or editing .mdx files, adding custom MDX components, modifying frontmatter, or working with the MDX rendering pipeline. Triggers on: MDX, frontmatter, article, craft, Callout, Steps, MagicMove, content creation, blog post, createMDXComponent, Zod schema validation. NOT for component directory structure (use component-creation).

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Next.js 16 Cache Components - PPR, use cache directive, cacheLife, cacheTag, updateTag

Upgrade Next.js to the latest version following official migration guides and codemods

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.