coding-guidelines

Enforce repository coding preferences for readability and consistent style.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/ViewableGravy/better-ecs --skill coding-guidelines-viewablegravy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-guidelines
Source: https://github.com/ViewableGravy/better-ecs/tree/main/.github/skills/coding-guidelines
Command: npx skills add https://github.com/ViewableGravy/better-ecs --skill coding-guidelines-viewablegravy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain a consistent and readable codebase by providing clear guidelines on coding preferences, reducing ambiguity and improving maintainability.

Core Features & Use Cases

  • Enforces Readability: Promotes clear naming, targeted comments, and avoidance of overly complex expressions.
  • Standardizes Practices: Offers specific recommendations for array destructuring and conditional logic.
  • Use Case: When implementing a new feature or refactoring existing code, consult these guidelines to ensure your changes align with the project's expected style and are easy for other developers to understand.

Quick Start

Follow these coding guidelines when writing new code or refactoring existing code.

Frequently Asked Questions about coding-guidelines

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

FAQPage Schema
How do I maintain consistent coding style and readability when refactoring TypeScript?

To maintain consistent coding style during refactoring, apply clear naming conventions, use targeted comments, and avoid nested ternary expressions to improve readability and reduce ambiguity.

What are the best practices for writing readable application code?

Best practices for readable application code include enforcing clear variable names, adding targeted comments, and standardizing array destructuring and conditional logic to ensure maintainability.

Does this coding guidelines skill apply to writing new library code?

Yes, these coding guidelines apply to writing new application or library code, ensuring new changes align with the project's expected style and are easy for developers to understand.

How do I review implementation structure before finalizing code edits?

Review implementation structure by checking for clear names, targeted comments, and avoidance of complex expressions to ensure the final edits follow standard coding preferences.

Why should I avoid nested ternary expressions in my codebase?

Avoid nested ternary expressions to enforce readability, as overly complex expressions reduce code clarity and make application logic harder for other developers to maintain.