Help us improve
Share bugs, ideas, or general feedback.
From pedantic-coder
Indexes pedantic-coder skills for universal code quality principles including naming precision, casing law, import discipline, declaration order, symmetry, and dead code intolerance. Use for code reviews, refactoring, or greenfield projects.
npx claudepluginhub oborchers/fractional-cto --plugin pedantic-coderHow this skill is triggered — by the user, by Claude, or both
Slash command
/pedantic-coder:using-pedantic-principlesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<IMPORTANT>
Enforces universal code quality rules — KISS, DRY, clean code, code review. Use when writing or reviewing any code.
Applies language-specific style guide rules (PEP 8, Google Style, Effective Go, etc.) when writing or reviewing code to ensure consistency with best practices.
Provides language-agnostic guidelines for code quality, comments, error handling, and formatting when writing or reviewing code in any language. Project-specific conventions take priority.
Share bugs, ideas, or general feedback.
These are not suggestions. They are non-negotiable standards for code that respects the reader. Your code works? Great. Now make it right.
Use the Skill tool to invoke any skill by name. When invoked, follow the skill's guidance directly.
These apply to every language, every codebase, every commit.
| Skill | Triggers On |
|---|---|
pedantic-coder:naming-precision | Variable names, function names, class names, file names, semantic accuracy, vague identifiers like data, temp, result, handle |
pedantic-coder:casing-law | PascalCase, camelCase, snake_case, UPPER_SNAKE — mixed conventions, inconsistent casing across a codebase |
pedantic-coder:abbreviation-policy | Shortened names, acronyms, inconsistent abbreviations (btn vs button, msg vs message), abbreviation rules |
pedantic-coder:boolean-naming | Boolean variables, predicate functions, is/has/can/should prefixes, negative booleans, flag naming |
pedantic-coder:import-discipline | Import statements, require calls, use declarations, import ordering, grouping, sorting, circular dependencies |
pedantic-coder:declaration-order | File structure, member ordering in classes/structs, constant placement, export ordering, predictable file shape |
pedantic-coder:symmetry | Parallel code paths, matching pairs (create/delete, open/close), consistent function signatures, structural mirroring |
pedantic-coder:one-pattern-one-way | Inconsistent approaches to the same problem, mixed paradigms, local shortcuts that break codebase conventions |
pedantic-coder:magic-value-elimination | Inline string literals, unexplained numbers, hardcoded values that should be named constants or enums |
pedantic-coder:dead-code-intolerance | Commented-out code, unused imports, unreachable branches, TODO/FIXME comments, historical comments about removed code |
pedantic-coder:visual-rhythm | Whitespace usage, blank line placement, consistent spacing between logical sections, code as prose |
Enforce the project's own rules, not just ours.
| Skill | Triggers On |
|---|---|
pedantic-coder:guidelines-compliance | Checking code against CLAUDE.md guidelines, reviewing project convention compliance, auditing a repository's own documented rules, CLAUDE.md inheritance hierarchy |
For language-specific pedantry that goes beyond universal principles.
| Skill | Triggers On |
|---|---|
pedantic-coder:python-pedantry | Python type hints (str | None vs Optional), Pydantic settings, StrEnum, exception chaining, Google docstrings, ruff rules |
pedantic-coder:typescript-pedantry | TypeScript strict mode, discriminated unions, Zod schemas, barrel exports, as const, ESLint strict rules |
pedantic-coder:go-pedantry | Go error wrapping, interface design, package naming, struct field ordering, receiver naming, golangci-lint rules |
Invoke a skill when there is even a small chance the work touches one of these areas:
All principles rest on three foundations:
Consistency is non-negotiable — One way. Everywhere. Always. A codebase that mixes conventions is a codebase that nobody trusts.
If it looks wrong, it is wrong — Visual disorder signals logical disorder. Code that is hard to scan is hard to maintain. The shape of your code communicates as much as the logic.
Every detail is a decision — Nothing is "just a style choice." Every abbreviation, every import order, every blank line either reinforces or undermines the codebase's integrity.