4 件 ・ 関連度順
概要と使いどころ
Use when reviewing stylesheets, component styles, and responsive behavior related to Use consistent CSS naming conventions. Check the rendered layout across breakpoints and interaction states before proposing a fix.
日本語の概要は準備中です。原文の説明を表示しています。
Enforces project coding standards during code review: naming conventions (PascalCase for classes, camelCase for methods/variables, UPPER_SNAKE_CASE for constants, kebab-case for files), standard file structure, anti-magic-number policy, file size limits (500/800 lines), security patterns, and design patterns. Use when reviewing code, writing new code, or checking adherence to project conventions.
日本語の概要は準備中です。原文の説明を表示しています。
Name C# symbols, events, prototypes, FTL keys, resources, and compatibility surfaces consistently.
日本語の概要は準備中です。原文の説明を表示しています。
Test naming conventions and best practices specialized skill. Used when naming test methods, improving test readability, and establishing naming standards. Covers three-part naming method, Chinese naming recommendations, test class naming, etc. Keywords: test naming, test naming, naming conventions, naming conventions, three-part naming, three-part naming, method_scenario_expected, method_scenario_expected, how to name tests, test readability, naming best practices, test report, test documentation
日本語の概要は準備中です。原文の説明を表示しています。