Loading...
Loading...
Found 47 Skills
Project code structure and file organization. Use when creating files, organizing components, or deciding where code should live.
Swift style guidelines covering naming conventions, code organization, and best practices for writing idiomatic Swift code.
Use when naming or renaming TypeScript identifiers, especially cryptic names, ambiguous parameters, I-prefixed interfaces, Hungarian notation, misleading side effects, or requests for clearer names.
Use when writing or reviewing Move smart contracts on Sui. Applies to naming structs, error constants, regular constants, events, getter functions, capability types, hot potato types, and dynamic field keys. Use whenever creating new types, functions, or constants in Move code.
Standards for Angular 17+ Enterprise Architecture. Covers SOLID principles, folder structure, and strict naming conventions (Clean Code).
Maintain code consistency by following official Dart style and naming conventions.
Use when refactoring code with poor names, when asked to improve naming, or when a user struggles to name a class/method/variable. Symptoms include -Manager/-Util suffixes, single-letter variables, process/handle/do verbs, primitive obsession, god methods with multiple responsibilities.
Enforce C++ coding standards including camelCase or snake_case variables, PascalCase classes, and consistent file naming.
Verify code quality including naming conventions, organization, documentation, and general best practices. Use when asked to "verify quality", "check code quality", or "review code organization".
Enforce consistent React component naming conventions using domain + role patterns. Use when creating, reviewing, or refactoring components.
Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.