skills.rest
rodrigotoledo
rodrigotoledoCOMMUNITY
Explore all skills by this author →
Website𝕏@foolkgsGitHub

coding-guidelines

Prescribe deterministic, minimal-change coding guidelines for developers and AI copilots.

Updated Jun 18, 2026
Search Tags:#quality#refactor#review#coding#guidelines#best-practices
One-click install
npx skills add https://github.com/rodrigotoledo/trading-exchange --skill coding-guidelines-rodrigotoledo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coding-guidelines
Source: https://github.com/rodrigotoledo/trading-exchange/tree/main/packages/skills-catalog/skills/%28development%29/coding-guidelines
Command: npx skills add https://github.com/rodrigotoledo/trading-exchange --skill coding-guidelines-rodrigotoledo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, modifying, or reviewing code — implementation tasks, code changes, refactoring, bug fixes, or feature development. Do NOT use for architecture design, documentation, or non-code tasks.

Core Features & Use Cases

  • Think Before Coding: State assumptions explicitly. Surface tradeoffs. If something is unclear, ask.
  • Simplicity First: Keep code minimal, avoid unnecessary abstractions, and avoid over-engineering.
  • Surgical Changes: Touch only what you must; map changes to the user's request.
  • Goal-Driven Execution: Define verifiable steps and plan; loop until results are achieved.

Quick Start

Apply these guidelines when writing, reviewing, or modifying code to minimize mistakes and keep changes surgical.

Frequently Asked Questions about coding-guidelines

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

FAQPage Schema
How do I minimize coding mistakes when reviewing or refactoring code with an AI copilot?▼

To minimize coding mistakes, apply deterministic, minimal-change guidelines that enforce plan-driven steps, change-local edits, and test-oriented validation during code reviews and refactoring. This keeps modifications surgical and mapped directly to your request.

What are the best practices for keeping code changes surgical during feature development?▼

Best practices for surgical changes include touching only what is necessary, mapping edits to the user's request, avoiding unnecessary abstractions, and explicitly stating assumptions and trade-offs before implementation.

How do I enforce goal-driven execution and verifiable steps in my coding workflow?▼

Enforce goal-driven execution by defining verifiable steps and a clear plan before coding, then looping through the implementation until the results are achieved and validated against the original goal.

Can I use these coding guidelines for architecture design and documentation tasks?▼

No, you cannot use these coding guidelines for architecture design or documentation. They are strictly designed for writing, modifying, reviewing, and debugging code tasks to keep changes minimal and targeted.

Why does my AI copilot introduce over-engineered solutions during bug fixes?▼

AI copilots introduce over-engineered solutions when simplicity is not enforced. Applying guidelines that prioritize minimal code, explicit trade-offs, and avoiding unnecessary abstractions prevents over-engineering during bug fixes.

Related Skills

Explore More Software Engineering Skills→
KubrickCodeKubrickCode
1

work-execution-plan-documentation

Create structured work execution plans with goals, scope, and task order.

Community
Basic
Paradiddle131Paradiddle131
1

autoresearch

Run single-change experiments to optimize measurable goals with an auditable log.

Community
Advanced
maslennikov-igmaslennikov-ig
2

code-reviewer

Automate pull-request code review across six languages with structured reports.

Community
Advanced
simonwjacksonsimonwjackson

se-zoom-out

Maps modules, primary callers, and key domain concepts from code.

Community
Intermediate