using-pedantic-principles

Enforce naming, casing, and import standards across Python, TypeScript, and Go code.

28|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/oborchers/fractional-cto --skill using-pedantic-principles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-pedantic-principles
Source: https://github.com/oborchers/fractional-cto/tree/main/pedantic-coder/skills/using-pedantic-principles
Command: npx skills add https://github.com/oborchers/fractional-cto --skill using-pedantic-principles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of maintaining high code quality and consistency across a codebase by providing a comprehensive set of rules and guidelines for naming, casing, structure, and more.

Core Features & Use Cases

  • Universal Principles: Enforces consistent application of naming precision, casing rules, boolean naming, import discipline, and more across all languages.
  • Language-Specific Packs: Offers tailored pedantry for Python, TypeScript, and Go.
  • Project Guideline Compliance: Ensures adherence to project-specific conventions and CLAUDE.md guidelines.
  • Use Case: Before committing any code, invoke pedantic-coder:naming-precision to ensure all identifiers are clear and descriptive, or use pedantic-coder:typescript-pedantry to enforce strict TypeScript best practices.

Quick Start

Use the pedantic-coder:naming-precision skill to review all variable and function names in the current file.

Frequently Asked Questions about using-pedantic-principles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce consistent naming conventions and casing rules during code review?

To enforce consistent naming conventions during code review, apply universal principles for naming precision and casing rules across all identifiers. This ensures variables and functions remain clear, descriptive, and standardized across your codebase.

What are the best practices for structuring imports in Python and TypeScript?

Best practices for structuring imports involve applying import discipline rules tailored to Python and TypeScript. Following language-specific guidelines ensures strict adherence to structural conventions, reducing dependency conflicts and improving code readability.

Does this support language-specific coding standards for Go alongside Python and TypeScript?

Yes, it supports language-specific coding standards for Go alongside Python and TypeScript. It provides tailored guidelines for each language to enforce strict best practices, naming, and structural consistency unique to their ecosystems.

How do I ensure my refactoring aligns with project-specific conventions?

To ensure refactoring aligns with project-specific conventions, verify changes against established project guidelines and universal structural rules. This compliance check guarantees new code integrates seamlessly without violating existing architectural standards.

When should I apply universal code quality principles versus language-specific best practices?

Apply universal code quality principles for baseline naming and casing across all languages, and use language-specific best practices when enforcing unique structural rules for Python, TypeScript, or Go. Combining both ensures comprehensive consistency during code reviews.