coding-guidelines

To enforce behavioral coding guidelines, apply rules that require thinking before coding, simplicity first, surgical changes, and goal-driven execution to minimize LLM errors during development tasks.

The best way to apply coding guidelines during refactoring and debugging is to make surgical changes, edit only what is necessary, and define verifiable success criteria to maintain existing behavior.

Code review guidelines for maintainability are followed by surfacing assumptions, revealing tradeoffs, and using minimal straightforward solutions without unnecessary abstractions to reduce common coding mistakes.

You need behavioral coding guidelines when writing, modifying, or reviewing code, specifically triggering on implementation tasks, code changes, refactoring, bug fixes, or feature development to reduce errors.

Defining custom coding guidelines requires a YAML frontmatter with name and description in SKILL.md, followed by a clear Markdown body containing the activation instructions for the behavioral rules.

Your LLM introduces unnecessary abstractions because it lacks enforced simplicity-first guidelines; applying behavioral rules ensures minimal, straightforward solutions and requires asking when uncertain to prevent mistakes.