Enforce code quality standards including minimalism, proper comments, correctness over optimization, and eliminating unnecessary complexity. Use when writing code, refactoring, code review, or when user mentions code quality, clean code, optimization, or comments.
Use when generating or modifying code to ensure it follows project architecture and development guidelines. Enforces Result-based error handling, TypeScript conventions, and frontend architecture patterns.
Review code for quality, correctness, and standards. Use before commits or when reviewing PRs.
Ensures CSS and components only use approved design tokens. Use when the user asks about design system enforcement, hardcoded colors, spacing values, or wants to validate token usage across files.
Performs strict code review with comprehensive validation
Review guidelines. Always use when Claude needs to review the code changes
Apply safe, behavior-preserving lint and refactor changes for readability and conventions. Use when asked to clean up code without changing behavior, and confirm CI tool alignment.
Validate design doc structure and frontmatter. Use when checking design docs for compliance, ensuring proper formatting, or verifying metadata before commits.
Standards for maintaining high code quality including comments, test coverage, and documentation practices
Przeprowadza code review dla Next.js 16, React 19, Drizzle ORM, Tailwind CSS 4, Radix UI, SWR. Używaj przy przeglądaniu PR, ocenie implementacji fazy/etapu, weryfikacji zgodności z planem. Generuje raport z klasyfikacją problemów (krytyczne/poważne/drobne/sugestie).
TypeScriptプロジェクトの型チェック実行スキル。tscによる型エラー検出とレポート。型チェック実行時は必ずエージェント（Task tool）を使用し、直接Bashで型チェックコマンドを実行しない。
Runs quality checks across all components (backend, frontend, landing). Use before creating PRs, merging, or to verify overall code quality.
Comprehensive reference guide for Python type hints, static type checking with mypy, modern type annotation patterns (PEP 484, 585, 604, 612, 613), and type hint best practices for Python 3.9+. Use during code reviews to ensure proper type annotation usage, evaluate mypy configuration, and identify type hint anti-patterns.
Checks components and pages for WCAG 2.1 accessibility violations. Use when the user asks about a11y, WCAG compliance, screen readers, aria labels, keyboard navigation, or accessible patterns.
Systematically analyzes and fixes GitHub CodeQL security alerts with proper documentation and testing
Comprehensive code review for security, performance, maintainability, and best practices with impact analysis and authoritative references
Review code for correctness, edge cases, and adherence to project patterns.
数値の入出力バリデーション方針。関数の引数・戻り値の妥当性チェック規約を定義。test-writer, implement, reviewerの各観点で参照。
Use when working with docusaurus.config.js/ts files to validate or modify Docusaurus configuration
PHP品質チェック。PHPStan/Pint/PHPUnit実行時に使用。「PHPの品質チェック」「静的解析」で起動。
모든 코드 변경에 항상 적용되는 프로젝트 규칙. 프로젝트 구조, API 규칙, 컨벤션 준수 필수.
Defines language usage conventions separating user communication from technical artifacts. Use when writing code, documentation, commits, or communicating with users in multilingual projects.
Review and fix docstrings to follow Google-style conventions. Use when asked to check docstrings, format docstrings, or lint docstrings.
Run comprehensive quality checks including linting, type checking, and tests. Use before committing or when validating code changes.
