Loading...
Loading...
Found 66 Skills
Create standardized UTM tracking for all campaigns. Ensure consistent naming conventions across team and generate tracking reports.
Apply language-agnostic naming conventions using the A/HC/LC pattern. Use when naming variables, functions, or reviewing code for naming consistency.
Create SQL examples for OceanBase documentation with proper formatting, meaningful names, and separated results. Use when writing or reviewing example sections in OceanBase documentation.
Establish a naming convention system for design elements, components, and tokens with clear rules and examples.
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".
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.
Brainstorm and validate names for plugins, skills, agents, and commands. Use when naming a new plugin, choosing atom names, validating naming conventions, or when user mentions "name plugin", "name skill", "naming convention", "brainstorm names", "what should I call", "plugin name", "good name for".
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
In large applications, information architecture determines whether users can find, understand, and act on data. Naming matters. The UI should mirror the data model and signal how data can be transformed. Dangerous or irreversible changes always require a confirm dialog. Use when designing navigation, naming entities, structuring large feature sets, or modelling data-driven UI.
Audits database schemas for naming conventions, type consistency, nullability patterns, and missing constraints. Provides violations report with recommended fixes. Use for "schema validation", "database linting", "schema standards", or "consistency checks".
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.
Enforce C++ coding standards including camelCase or snake_case variables, PascalCase classes, and consistent file naming.