clean-architecture-principles
Enforce clean architecture principles including DRY, YAGNI, KISS, Law of Demeter, and Separation of Concerns. Warns when complexity creeps in and questions unnecessary features. Use when designing architecture,...
Découvrez les skills Documentation, comparez leurs dépôts et consultez leurs instructions.
Enforce clean architecture principles including DRY, YAGNI, KISS, Law of Demeter, and Separation of Concerns. Warns when complexity creeps in and questions unnecessary features. Use when designing architecture,...
Defines language usage conventions separating user communication from technical artifacts. Use when writing code, documentation, commits, or communicating with users in multilingual projects.
Comprehensive ColdFusion (CFML) syntax validation and best practices verification. Use when validating ColdFusion code, checking for security vulnerabilities (SQL injection, proper cfqueryparam usage), ensuring...
Fix markdown linting errors in documentation files
Validate and lint structured data files (YAML, JSON, TOML) for consistency, required fields, syntax errors, and schema compliance.
Run all quality checks including linting, formatting, and type checking. Use when user asks to check code quality, run checks, or verify code before committing.
Validates workflow YAML files to ensure structure and schema correctness.
Enforce strict TypeScript type safety rules including no 'any' types, explicit return types, proper interfaces, and type guards. Use when writing TypeScript code, reviewing code, refactoring, or when user menti...
Conduct thorough code reviews for pull requests and pre-commit changes
Comprehensive C# code validation, static analysis, and best practices verification for .NET applications. Use when validating C# code, checking SOLID principles, reviewing async/await patterns, verifying nullab...
Markdownファイルのフォーマットと整形を実行します。見出し構造の修正、コードブロックの整形、リンク検証、表の整列、一貫性のあるスタイル適用を行います。Markdown整形、フォーマット、スタイル統一について言及する場合に...
Expertise in reviewing code for style, security, and performance. Use when the user asks for "feedback," a "review," or to "check" their changes.
Safe, systematic approach to code refactoring with verification and rollback strategy.
Review implementation for security vulnerabilities and best practices. Checks input validation, injection prevention, auth/authz, secrets handling. Use after code review before merge.
Use when writing or reviewing Go code - enforces Rob Pike's proverbs, Dave Cheney's Zen, and Google/Uber style patterns. Triggers before any Go implementation or during code review.
Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Code extension development guidelines, libraries and...
コード修正後にプロジェクトルールへの準拠をチェック。コードを書いた後、修正した後、実装が完了した時に使用。
Review implementation for code quality, style consistency, and best practices. Runs before security review. READ-ONLY - reports issues but does not fix them.
Python conventions and reliability checklist for agents (tests, formatting, typing where appropriate).
Enforces mandatory logging standards using developer.log() instead of print(). Use when writing production code, reviewing code, or fixing logging violations.
Ensures the application builds successfully and fixes any build errors.
Enforce Python 3.12+ coding conventions when editing or creating Python code. Use for tasks that touch .py files, focusing on style, naming, typing, error handling, and performance-oriented idioms.
Use typed errors and consistent error handling across the codebase. Use when adding new error cases or adjusting error behavior.
Úsalo cuando el usuario pregunte "¿Esto está bien?", "Revisa este código", "Optimiza esto" o "Genera un reporte de calidad".
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.