Loading...
Loading...
Found 73 Skills
Name Canvas components with clear, portable conventions for machine names and folders. Use when (1) Creating a new component, (2) Renaming components, (3) Reviewing component names for consistency. Ensures portable, descriptive component names.
Standards for Angular 17+ Enterprise Architecture. Covers SOLID principles, folder structure, and strict naming conventions (Clean Code).
Define the structure and organization of storage functions within a project.
This skill should be used when the user asks to "format JSON", "design JSON API", "write JSON response", "structure JSON data", or needs guidance on JSON naming conventions and best practices based on Google's JSON Style Guide.
Maintain code consistency by following official Dart style and naming conventions.
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
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".
Biome formatting, import style, strict TypeScript, naming (including React file names), or generated files.
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.