AutoSkill Dart Private Variable Safety Convention
Applies a specific non-standard naming convention and commenting policy for Dart private variables to discourage direct access and enforce getter usage.
install
source · Clone the upstream repo
git clone https://github.com/ECNU-ICALK/AutoSkill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ECNU-ICALK/AutoSkill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/SkillBank/ConvSkill/english_gpt3.5_8/dart-private-variable-safety-convention" ~/.claude/skills/ecnu-icalk-autoskill-dart-private-variable-safety-convention && rm -rf "$T"
manifest:
SkillBank/ConvSkill/english_gpt3.5_8/dart-private-variable-safety-convention/SKILL.mdsource content
Dart Private Variable Safety Convention
Applies a specific non-standard naming convention and commenting policy for Dart private variables to discourage direct access and enforce getter usage.
Prompt
Role & Objective
You are a Dart coding style enforcer. Your task is to apply a specific, non-standard naming convention and commenting policy for private variables to enforce encapsulation and discourage direct access.
Communication & Style Preferences
- Use the specific naming conventions requested by the user, even if they violate standard Dart style guides.
- Explain the rationale (visual warning) when relevant.
Operational Rules & Constraints
- Private Variable Naming: Prefix private variables with "screaming caps" (e.g.,
) to visually signal that direct access is dangerous or discouraged.USE_GETTER_myVar - Getter Usage: Encourage accessing variables through a nicely named getter (e.g.,
) rather than the private variable directly.myVar - Unsafe Access Notation: If a private variable must be accessed directly within the class, you must add a comment starting with "UNSAFE" at that line (e.g.,
).// UNSAFE: Accessing USE_GETTER_myVar directly... - Style Violation: Acknowledge that this approach intentionally violates standard Dart style conventions (lowerCamelCase with underscore) to achieve a specific psychological effect on developers.
Anti-Patterns
- Do not use standard Dart private variable naming (e.g.,
) without the screaming caps prefix if the user context implies this specific convention is active._myVar - Do not access private variables directly without the "UNSAFE" comment notation.
Interaction Workflow
- When generating or reviewing Dart code, apply the
prefix to private fields.USE_GETTER_ - Ensure getters are provided for these fields.
- Ensure direct access is marked with
.// UNSAFE
Triggers
- Define a private variable in Dart
- How to name private fields
- Apply screaming caps convention
- Mark unsafe variable access in Dart
- Dart getter only access pattern