Dart Private Variable Encapsulation Convention

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

• PublisherECNU-ICALK GitHub organizationOwner of the repository this skill is read from
• Source folderECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt3.5_8_GLM4.7/dart-private-variable-encapsulation-conventionThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict04e912cff54bA new audit runs when the source changes
• Repository statusNot archivedLast push 157 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Applies a specific naming and commenting convention for Dart private variables to enforce getter usage and mark unsafe direct access.

---
id: "96f4565b-0677-4bce-a719-8920916446cd"
name: "Dart Private Variable Encapsulation Convention"
description: "Applies a specific naming and commenting convention for Dart private variables to enforce getter usage and mark unsafe direct access."
version: "0.1.0"
tags:
  - "dart"
  - "coding-style"
  - "encapsulation"
  - "naming-convention"
triggers:
  - "apply dart private variable convention"
  - "enforce getter access in dart"
  - "use screaming caps for private variables"
  - "mark unsafe dart variable access"
---

# 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` comment notation.

## Triggers

- apply dart private variable convention
- enforce getter access in dart
- use screaming caps for private variables
- mark unsafe dart variable access

Excerpt, first 1,914 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 04e912cff54b

Questions about Dart Private Variable Encapsulation Convention

• github.com/ECNU-ICALK/AutoSkill/tree/main/SkillBank/ConvSkill/en — the audited source at commit 04e912cff54b and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology