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.
npx skills add ECNU-ICALK/AutoSkill --skill dart-private-variable-safety-convention --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 V
- Prompt
- Triggers
What does the Dart Private Variable Safety Convention skill do?
Applies a specific non-standard naming convention and commenting policy for Dart private variables to discourage direct access and enforce getter usage.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill dart-private-variable-safety-convention --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.