yend724

Git コミットメッセージの規約。Conventional Commits 形式、日本語。 Apply when creating git commits, reviewing commit messages, or when the user asks to commit changes.

React / Next.js の TypeScript 規約。 コンポーネント（.tsx）、hooks、Server Components、Client Components、 Server Actions の実装時に適用する。

コミット前のセルフレビュー。プロジェクトの規約に沿っているかチェックする。 Apply when the user asks to review code, check conventions, or requests a self-review before committing.

スタイリング規約。Tailwind CSS v4 と inline styles の使い分け。 UI コンポーネントやプレビュー領域のスタイリング時に適用する。 Tailwind はアプリ UI に、inline styles はプレビュー領域に使い、混在させない。

TDD（テスト駆動開発）のワークフロー。 新機能やバグ修正の実装時に適用する。 Red → Green → Refactor のサイクルを必ず守る。

Vitest を使った TypeScript テスト規約。 テスト（.test.ts, .test.tsx）の作成・レビュー時に適用する。 純関数テスト、Result 型テスト、React コンポーネントテスト、モックを規定。

関数型プログラミングベースのTypeScriptコーディング規約。 TypeScriptコード（.ts/.tsx）の実装時に適用する。 型、アロー関数、Result型エラーハンドリング、不変性、命名、import、async、pipe/合成を規定。

Zod + neverthrow を使った入力バリデーション規約。 バリデーションスキーマ、外部入力のパース、 API/フォーム境界での Zod → Result ブリッジの実装時に適用する。

Functional programming conventions for TypeScript logic layers. Auto-triggers when writing utilities, services, domain logic, or data transformation logic 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 (app/ directory, next.config, route handlers). 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 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. 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 outside framework-specific rules.

Feature-based frontend architecture conventions. Auto-triggers when creating new files, directories, or organizing project structure. Defines rules for feature-based code organization, module boundaries, dependency direction, and public API design.

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.

Zenn記事のレビューを行う。記事の文体・構成・技術的正確性を過去記事と照らし合わせてチェックする。