LLM Coding Guidelines

SKILL.md

---
name: llm-coding-guidelines
description: Behavioral guidelines for LLM-based coding agents to reduce common mistakes. Use when writing, editing, or reviewing code to ensure surgical precision, minimal bloat, goal-driven execution, and explicit reasoning before action. Triggers on code generation, refactoring, debugging, and PR review tasks where quality and restraint matter.
---

# LLM Coding Guidelines

## 1. Think Before Coding

Before implementing:
- State assumptions explicitly. If uncertain, ask.
- Present multiple interpretations when ambiguity exists — don't pick silently.
- If a simpler approach exists, say so and push back when warranted.
- If something is unclear, stop, name what's confusing, and ask.

## 2. Simplicity First

Minimum code that solves the problem. Nothing speculative:
- No features beyond what was asked.
- No abstractions for single-use code.
- No "flexibility" or "configurability" that wasn't requested.
- No error handling for impossible scenarios.
- If you write 200 lines and it could be 50, rewrite it.

Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.

## 3. Surgical Changes

Touch only what you must. Clean up only your own mess:
- Don't "improve" adjacent code, comments, or formatting.
- Don't refactor things that aren't broken.
- Match existing style, even if you'd do it differently.
- If you notice unrelated dead code, mention it — don't delete it.

When your changes create orphans:
- Remove imports/variables/functions that YOUR changes made unused.
- Don't remove pre-existing dead code unless asked.

The test: Every changed line should trace directly to the user's request.

## 4. Goal-Driven Execution

Define success criteria. Loop until verified.

Transform tasks into verifiable goals:
- "Add validation" → "Write tests for invalid inputs, then make them pass"
- "Fix the bug" → "Write a test that reproduces it, then make them pass"
- "Refactor X" → "Ensure tests pass before and after"

For multi-step tasks, state a brief plan:
```
1. [Step] → verify: [check]
2. [Step] → verify: [check]
```

## 5. Tradeoff Awareness

These guidelines bias toward caution over speed. For trivial tasks, use judgment. When in doubt, err on the side of restraint.