yend-dev

Self-review skill for MDX blog articles. Given an article path, the skill reads the file and reports specific issues at their line locations, spanning frontmatter integrity, Japanese-English typography, markdown structure, and content quality. Auto-triggers when the user asks to review an article file path or when editing files matching `packages/resources/posts/**/*.mdx`.

Functional programming conventions for TypeScript logic layers. Auto-triggers when writing utilities, services, domain logic, or data transformation logic in files matching `*.ts` to ensure pure functions, immutability, and proper side-effect isolation.

Next.js App Router conventions covering file-based routing, caching strategies, Server Actions, Metadata API, and framework-specific patterns. Auto-triggers when working within Next.js App Router projects on files matching `src/**/*.tsx`, `src/**/*.ts`, `proxy.ts`, or `next.config.*`. Covers file-based routing, caching, Server Actions, Metadata API, and framework-specific patterns.

React component design conventions focusing on Server/Client component boundaries, composition patterns, and data flow. Auto-triggers when writing or modifying React components in files matching `*.tsx`, `*.jsx`, `*.ts`, or `*.js` to ensure correct RSC patterns and optimal component architecture.

Testing conventions covering unit tests, component tests, and E2E tests. Auto-triggers when writing or modifying test files matching `*.test.ts`, `*.test.tsx`, `*.spec.ts`, `*.spec.tsx`, or files under `e2e/**/*`. Uses Vitest for unit/component tests and Playwright for E2E tests.

General TypeScript coding conventions for type safety, exported API design, and module structure. Auto-triggers when writing or refactoring TypeScript code in files matching `*.ts`, `*.tsx`, `*.mts`, or `*.cts` outside framework-specific rules.