Enforce evidence-based completion claims with actual command output. Use before (1) claiming tests pass, (2) claiming a bug is fixed, (3) claiming a task completed successfully, (4) claiming performance improved, (5) saying "ready for review". Prevents phrases like "should pass" or "that should fix it" - requires fresh verification evidence.
Apply fixes to entities/components with best practice validation. Searches library docs for simpler patterns, checks for built-in features, validates fixes maintain performance and architectural integrity. Integrates with breath-synchronization skill for breathing-related fixes. Works with parameter tuning, library pattern replacement, and performance optimization.
Comprehensive code review for pull requests with quality, security, and best practices analysis
ESLint, Prettier, and StyleLint configuration standards for JavaScript code quality and formatting, including flat config setup, rule management, and build integration
Prevents "lazy" coding habits by enforcing full implementation and banning placeholders.
็จๅผ็ขผๅฏฉๆฅ๏ผๅ ่ฃ PAL MCP ็ codereview ๅ่ฝ
Review changes to find high-impact bugs or regressions. Use for code review of local changes or pull requests.
ๆฅญ็ใฎใในใใใฉใฏใใฃในใจใขใผใญใใฏใใฃๆจๆบใซ็ งใใใฆTerraformใณใผใใใฌใใฅใผใใพใใใฆใผใถใผใใณใผใใฌใใฅใผใใในใใใฉใฏใใฃในใฎใขใใใคในใใพใใฏใขใผใญใใฏใใฃใฎๆนๅใๆฑใใๅ ดๅใซไฝฟ็จใใฆใใ ใใใ
ๅฝๅ่ง่ / Naming conventionsใๅจๅๅปบ็ฑปใๅฝๆฐใๅ้๏ผๆ้ๅฝๅใๆฃๆฅๅฝๅๆถไฝฟ็จใๆ ธๅฟๅๅ๏ผ็ฎๆดไผๅ ๏ผไธไธๆๆถๆญงไน๏ผ็ฑปๅๆ็คบๅทฒๆไพ่ถณๅคไฟกๆฏใUse when naming classes/functions/variables, renaming code, or reviewing names. Prioritizes brevity over self-documentation.
Coding conventions and best practices for TypeScript, React 19, and Next.js 15. Use when writing new code, reviewing code quality, or ensuring consistency with Airbnb style guides and project-specific patterns.
ใณใผใๅ่ณชใฌใใฅใผ - ใขใผใญใใฏใใฃใใณใผใ่ญใใใใฉใผใใณในใๅๅฎๅ จๆงใ็ตฑๅ่ฉไพก
Write quality content for HTML documents. Use when writing text content, prose, descriptions, or any human-readable content in HTML files. Ensures spelling and style quality.
Guide for fixing Python strict type checking errors (Pylance/MyPy). Use this skill when resolving unknown type, missing import, or type mismatch errors in Python files. Covers common patterns for TypedDict, generics, casting, and protocol alignment.
Detect spaghetti code and propose specific refactoring solutions. Analyzes detected issues and provides concrete code improvements.
Pre-implementation validation framework requiring โฅ90% confidence before coding. Prevents wrong-direction work by assessing duplicates, architecture alignment, documentation, OSS references, and root cause understanding. Use before implementing features, fixes, or refactoring to save 5K-50K tokens per prevented error.
Generic code review for test code. Use as part of parallel test review execution.
Format code using dotnet format, prettier, and other formatting tools. Use when task involves code style fixes, formatting consistency, or preparing code for commit.
Guidance for writing valid Emacs Lisp code with incremental validation. Use when writing or modifying elisp functions, especially complex nested forms with cl-loop, multiple let* bindings, or lambdas.
ไปฃ็ ๅฎกๆ ธๅฏผ่ชใ่งฆๅ๏ผ็จๆท้็ฅ"็ผ่ฏ้่ฟ"ๆ"่ฏทๅฎกๆ ธไปฃ็ "ๆถไฝฟ็จ๏ผๅฏนๅญไปฃ็ไบงๅบ็ไปฃ็ ่ฟ่ก่ดจ้ๅฎกๆ ธใ่ง่ๆฃๆฅใ่ถ็ๆฃๆฅ๏ผ่พๅบๅฎกๆ ธๆฅๅใ
Review code changes and remove AI-generated patterns like excessive comments, gratuitous defensive checks, type escape hatches, and over-engineering.
Enforce the "Premium" aesthetic and accessibility standards.
ํ ์คํธ ์์ฑ ์ ์ปจ๋ฒค์ ์๋ ์ ์ฉ
