coding-conventions

Enforce language-agnostic coding conventions across multi-language codebases.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/erichugy/agentic.skills --skill coding-conventions-erichugy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-conventions
Source: https://github.com/erichugy/agentic.skills/tree/main/coding-conventions
Command: npx skills add https://github.com/erichugy/agentic.skills --skill coding-conventions-erichugy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Language-agnostic guidelines that enforce consistent coding practices across all languages and frameworks, reducing errors and improving maintainability.

Core Features & Use Cases

  • Enforces input validation, error handling, and resource lifecycle across languages.
  • Guides architecture decisions and naming consistency to improve code quality and readability.
  • Use case: adopt these conventions in a polyglot codebase to ensure uniform behavior in modules and libraries.

Quick Start

Apply these conventions across your codebase to enforce language-agnostic consistency.

Frequently Asked Questions about coding-conventions

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

FAQPage Schema
How do I enforce coding conventions across a multi-language codebase?

You can enforce coding conventions across a polyglot codebase by applying language-agnostic guidelines for input validation, error handling, and resource lifecycle to ensure consistent behavior across all modules and frameworks.

What are language-agnostic coding conventions and when do I need them?

Language-agnostic coding conventions are uniform rules for architecture, naming, and security that apply regardless of framework. You need them in multi-language repositories to improve code readability and reduce maintenance errors across teams.

Can I apply consistent code review standards to TypeScript, Rust, and React?

Yes, you can apply consistent code review standards to TypeScript, Rust, and React by using language-specific variants built on top of foundational language-agnostic rules for error handling and domain values.

What is the best way to standardize input validation and error handling across different frameworks?

The best way to standardize input validation and error handling is to adopt language-agnostic conventions that define uniform practices, ensuring architectural consistency and reliable resource lifecycle management across your entire codebase.

Does this approach include guidelines for server-sent events parsing?

Yes, this approach includes a dedicated streaming reference for server-sent events parsing, ensuring that continuous data streams are handled consistently alongside standard input validation and resource lifecycle rules.