Skip to content
Back to skills

Preferences

ASecurity

User's general coding preferences

  • 6 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 18, 2026
ai-agents

Security analysis

A100/100

Scanned November 18, 2026

npx -y skills add AxGord/claude-workflow --skill preferences --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Preferences?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Preferences
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/axgord-preferences/badge)](https://www.skillsdirectory.com/skills/axgord-preferences)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: preferences
description: User's general coding preferences
---

## User's personal coding preferences

Set by the user; they override base skills.

### The linter IS the preference

Machine-checkable preferences (immutability, member order, visibility,
`_`-prefix, magic numbers, ternary returns, swallowed exceptions, dead
weight, field init at declaration, English comments, duplication, listener
symmetry) live in `preferences-lint` and are compiled into each project's
lint config by `lint-setup`. The PROJECT's config is authoritative. No lint
config here → load `preferences-lint`; unavailable too → say so in the report.

### Judgement the linter cannot make

- Event-listener methods: `xxxHandler`, not `onXxx`.
- No braces around a single-statement body (`if`/`for`/`function`).
- Comment only the non-obvious; never paraphrase the line.
- "Should never happen" → throw, never a quiet return.
- Abstraction: no helper for a 2–3-field literal that reads fine inline; no
  interface/base/factory before a second concrete consumer exists.
- A shared constant/style with one caller → modify it in place, don't add a
  variant beside it (check usages first).
- N operations differing only in the destination → one helper taking the
  destination as a callback; pass `Point`, not `x, y`.
- Helpers: closure over method context → local `inline function`; pure →
  `private static inline` at the class bottom, shared → global utility.

### Working with the user

- "Confirm before X" where the answer is "same as the established default" →
  state it in one line and proceed; ask only at a real fork with a visible
  trade-off.
- A narrowly scoped request gets a narrowly scoped answer — no reassurances
  about adjacent areas.
- Never allocate an identifier an external system owns (translation key, DB
  id, ticket number): wire exactly the ids handed over and list the missing
  ones — a guessed id hides behind the fallback and later collides.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.