coding-guidelines

Apply behavioral guidelines to reduce coding errors during implementation and review.

Updated Feb 27, 2026

Search Tags:#refactoring #llm #safety #coding #guidelines #code-review

Ready to run

npx skills add https://github.com/Gabrielloopes33/nexIA --skill coding-guidelines-gabrielloopes33

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: coding-guidelines
Source: https://github.com/Gabrielloopes33/nexIA/tree/main/.copilot/skills/coding-guidelines
Command: npx skills add https://github.com/Gabrielloopes33/nexIA --skill coding-guidelines-gabrielloopes33

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Behavioral guidelines to reduce common LLM coding mistakes. These principles bias toward caution over speed—for trivial tasks, use judgment.

Core Features & Use Cases

Think-before-code prompts surface assumptions and tradeoffs.
Simplicity First: limit changes to what’s necessary and clearly scoped.
Surgical Changes: modify only what you must, preserving existing behavior.

Quick Start

Apply these guidelines whenever you write, modify, or review code to reduce errors.

Frequently Asked Questions about coding-guidelines

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

FAQPage Schema

How do I reduce coding mistakes during LLM-assisted refactoring and code review?▼

To reduce coding mistakes during refactoring and code review, apply behavioral guardrails like think-before-code, simplicity-first, and surgical changes to surface assumptions and limit modifications to necessary, clearly scoped adjustments.

What is the best way to enforce surgical changes when modifying existing code?▼

Enforcing surgical changes involves modifying only what is necessary to preserve existing behavior, limiting scope to minimal verifiable modifications, and biasing toward caution over speed to reduce common coding errors during implementation.

How do think-before-code prompts help surface assumptions and tradeoffs in software engineering?▼

Think-before-code prompts help surface assumptions and tradeoffs by enforcing a pause to evaluate implementation decisions before writing code, ensuring caution over speed and reducing errors during development tasks.

When should I use simplicity-first guidelines for my development tasks?▼

Use simplicity-first guidelines during implementation, code reviews, and refactoring to limit changes to what is necessary and clearly scoped, ensuring minimal verifiable modifications that reduce common LLM coding mistakes.

Can I apply these coding guidelines to trivial implementation tasks?▼

Yes, you can apply these coding guidelines to trivial implementation tasks, though they bias toward caution over speed, so you should use your own judgment to determine the necessary level of guardrails for minor changes.