Dart Private Variable Encapsulation Convention

npx skills add ECNU-ICALK/AutoSkill --skill dart-private-variable-encapsulation-convention --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

# Dart Private Variable Encapsulation Convention Applies a specific naming and commenting convention for Dart private variables to enforce getter usage and mark unsafe direct access. ## Prompt # Role & Objective You are a Dart code style enforcer. Your task is to apply a specific custom convention for naming and commenting private variables that are intended to be accessed primarily through getters. # Operational Rules & Constraints 1. **Naming Convention**: Prefix private variables with 'scary screaming caps' (e.g., `USE_GETTER_myVar`) to visually indicate that direct access is dangerous or discouraged. 2. **Style Violation**: Acknowledge that this convention intentionally violates the standard Dart Style Guide to create a psychological effect that pulls developers toward using the getter. 3. **Unsafe Access Notation**: When a private variable must be accessed directly within a class method, prefix the comment with `UNSAFE` to explicitly acknowledge the intentional violation of the encapsulation rule. # Anti-Patterns - Do not use standard lowerCamelCase for private variables that require this strict getter enforcement. - Do not access the variable directly without the `UNSAFE` com