Loading...
Loading...
Found 201 Skills
Enforce repository coding standards for Swift 6.2 concurrency, Swift language rules. Use when reviewing or implementing Swift code changes.
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
Go coding standards and style conventions grounded in Effective Go, Go Code Review Comments, and production-proven idioms. Use when writing or reviewing Go code, enforcing naming conventions, import ordering, variable declarations, struct initialization, or formatting rules. Trigger examples: "check Go style", "fix formatting", "review naming", "Go conventions". Do NOT use for architecture decisions, concurrency patterns, or performance tuning — use go-architecture-review, go-concurrency-review, or go-performance-review instead.
Use before writing or editing any Python code — scripts, functions, bug fixes, cron jobs, data-processing one-offs, or additions to an existing .py file — even if the request sounds quick, casual, or "just a simple script." Applies whether the user names a .py file, describes what the script should do, or asks you to add/fix a function in Python. Covers required standards: type hints, no global variables, logging instead of print, wrapping any I/O (HTTP, DB, subprocess, file) in try/except, commenting the why not the what, writing a real test, and where to place design docs. Does not apply to conceptual Python questions with no code to write (e.g. explaining language features, comparing list vs tuple, explaining what an existing traceback means when the user hasn't asked for a fix, package install help, or learning-resource recommendations), and does not apply to non-Python languages.
代碼實作階段觸發。強制執行統一的編碼規範,支援 Java、TypeScript、Go 多語言。包含 Input/Output 模式、依賴注入、不可變物件等規範,確保代碼風格一致性。
Enforces which Dart 3 construct each declaration earns — sealed class + exhaustive switch with no `default:`/`case _:`, the three class modifiers (`sealed`/`final`/`abstract interface class`) and skip the rest, records as intra-layer tuples only, immutable value types (`final` fields, `const` ctor, value equality) hand-rolled when trivial and `freezed` when boilerplate dominates, explicit stable identity, total non-throwing domain functions, make-illegal-states-unrepresentable, and firm method/build/file/nesting complexity limits (the single-source-of-truth table other skills cite) — while banning `late`/`!`/`dynamic` honesty dodges. Use when authoring or reviewing any Dart type or declaration: class vs enum vs record vs typedef, hand-rolled vs `freezed`, adding a `switch`/`if-case`, writing `copyWith` or `==`/`hashCode`, deciding identity, keeping a domain function total, or hitting a length/nesting limit.
Comprehensive coding standards and best practices for maintainable, consistent software development across multiple languages and paradigms
Enforce C++ coding standards including camelCase or snake_case variables, PascalCase classes, and consistent file naming.
Correct-by-construction TypeScript and Effect standards. Use for TypeScript engineering, Effect code, or when another skill needs the user's coding standards.
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
Standards de codage universels, bonnes pratiques et patrons pour le développement TypeScript, JavaScript, React et Node.js.
Draft scaffold; incomplete and not for normal use. Cross-platform mobile development patterns. Extends core-coding-standards with mobile-specific rules. Use when building mobile apps.