coding-principles

Apply language-agnostic coding principles to guide code structure and naming.

2|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/tundraray/overture --skill coding-principles-tundraray
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-principles
Source: https://github.com/tundraray/overture/tree/main/skills/coding-principles
Command: npx skills add https://github.com/tundraray/overture --skill coding-principles-tundraray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides language-agnostic coding principles to guide maintainability, readability, and quality across projects.

Core Features & Use Cases

  • Maintainability focus: Encourage structures and naming that make code easier to modify and extend.
  • Readability emphasis: Promote self-documenting code and clear conventions.
  • Quality-driven design: Provide guidance for error handling, testing, and refactoring.

Quick Start

  • Review a module or function and apply coding-principles to improve maintainability and readability.

Frequently Asked Questions about coding-principles

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

FAQPage Schema
How do I improve code readability and maintainability during refactoring?

Improve code readability and maintainability during refactoring by applying language-agnostic principles that enforce explicit naming, small functions, clear error handling, and documentation guidelines across any project.

What are universal coding principles for structuring functions and naming variables?

Universal coding principles for structuring functions and naming variables require explicit naming conventions and small function designs to ensure self-documenting code that is easier to modify and extend across any language.

Can I apply language-agnostic coding best-practices to any framework?

Yes, you can apply these language-agnostic coding best-practices to any framework, as the guidelines focus on universal structure, testability, and quality decisions rather than specific syntax or platform dependencies.

How do I use coding principles to enforce quality during code reviews?

Use coding principles to enforce quality during code reviews by checking for explicit naming, small functions, clear error handling, and testability to guide maintainability and readability improvements across the module.

What is the best way to standardize error handling and testability across projects?

The best way to standardize error handling and testability across projects is to codify quality-driven design principles that provide consistent guidance for testing and refactoring, ensuring maintainable code regardless of the language.