standards
Plaited code conventions and development standards. Use when writing or editing TypeScript code in Plaited projects, following code conventions (type system, function style, imports), generating code, or verify...
Découvrez les skills tools code quality, comparez leurs dépôts et consultez leurs instructions.
Plaited code conventions and development standards. Use when writing or editing TypeScript code in Plaited projects, following code conventions (type system, function style, imports), generating code, or verify...
TSDoc standards for TypeScript/JavaScript code. Automatically invoked when writing, reviewing, or editing any TSDoc comments, code documentation, or API documentation. (project)
Reviews code changes with brief annotations. Use when user says "review code", "review changes", "what changed", "review pull request", "review PR", "review the pr", "review this pr", "review [name]'s pr", "rev...
This skill should be used when the user asks to "review code", "check best practices", "audit implementation", or when looking for review guidance by technology. 353 patterns from React, Vue, Bun, Node.js, Vite...
This skill should be used when the user asks to "audit code health", "find dead code", "clean up code", "find duplication", or when seeking cleanup opportunities. Identifies dead code, debug cruft, YAGNI violat...
This skill should be used when the user asks to "rename a function", "replace a pattern", "migrate an API", "mass refactor", or when doing AST-based code search. AST-aware search/refactor that ignores strings/c...
This skill should be used before committing code to ensure it meets Breenix quality standards. Use for running clippy checks, fixing compiler warnings, verifying no log side-effects, checking for dead code, and...
Review code for Playwright Guidelines compliance. Use when asked to "review my playwright tests", "check accessibility", or "check my tests against best practices".
This skill should be used when users need to format, clean, lint, or validate Markdown files using the markdownlint-cli2 command-line tool. Use this skill for tasks involving Markdown (including Quarto Markdown...
This skill should be used when users need to lint, format, or validate Python code using the Ruff command-line tool. Use this skill for tasks involving Python code quality checks, automatic code formatting, enf...
Formatting and linting standards using GTS, ESLint, and Prettier. Use when writing or formatting TypeScript code in this project.
Import conventions and ordering rules. Use when writing imports or organizing import statements. Enforces explicit named imports, never wildcards.
Review Brane SDK code for correctness, Java 21 patterns, type safety, and architectural consistency. Use when reviewing PRs, checking code changes, or validating implementations against Brane standards.
Guidelines for automated and manual verification of code changes. When to use: - After making code changes to ensure correctness As part of the implementation workflow
Pack repositories with Repomix for whole-codebase, cross-file analysis. Default to a whole-repo measurement pass, then a filtered whole-repo pack; if it fits under ~1M tokens, stop and hand off to Gemini. Only...
Use when writing or modifying any code. Enforces naming conventions, function design, and code clarity principles.
Use when creating or modifying Firebase Cloud Functions in /functions directory. Enforces function structure and error handling patterns.
定義程式碼品質標準、防止幻覺 (Anti-Hallucination) 與官方文件查證流程。確保所有程式碼皆為最新、穩定且符合最佳實踐。
Use when creating or editing any bash script (.sh) - ensures shellcheck passes after every edit with zero warnings
Use when creating or editing any markdown file (.md) - ensures consistent formatting and zero linting violations through mandatory validation
Identify over-engineering in Ruby - prefer simple data structures (Hash, Struct, Data) and pure functions over unnecessary classes
Breaking change detection patterns and dependency safety analysis for PR reviews
Structured code review framework using Conventional Comments for clear, actionable feedback.
Commit with clear messages explaining WHY, following repository conventions
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é.