agentsclimarketplace

Dart private variable safety convention

Skill ECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt3.5_8/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.From its SKILL.md

Install
npx -y skills add ECNU-ICALK/AutoSkill --skill dart-private-variable-safety-convention

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

SKILL.md

2.6 KB, 414 tokens by cl100k_base, as published. Nobody here has run it

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., USE_GETTER_myVar) to visually signal that direct access is dangerous or discouraged.
  • Getter Usage: Encourage accessing variables through a nicely named getter (e.g., myVar) rather than the private variable directly.
  • 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., _myVar) without the screaming caps prefix if the user context implies this specific convention is active.
  • Do not access private variables directly without the "UNSAFE" comment notation.

Interaction Workflow

  • When generating or reviewing Dart code, apply the USE_GETTER_ prefix to private fields.
  • 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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.