'naming-conventions' 검색 결과

Audit CSS class names for inconsistency and ambiguity, then organize them using BEM, a convention that names components, their elements, and variations. Check the rendered interface across screen sizes and interaction states when reviewing changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Auditing inconsistent CSS class names
• Renaming component classes using BEM
• Separating utility classes and JavaScript hooks

Name C# symbols, events, prototypes, FTL keys, resources, and compatibility surfaces consistently.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.