# std-coding-style

> Coding style best practices including naming conventions, formatting, and code organization

- Author: Lilu Douglas
- Repository: devalexanderdaza/opencode-workflow
- Version: 20260114232758
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/devalexanderdaza/opencode-workflow
- Web: https://mule.run/skillshub/@@devalexanderdaza/opencode-workflow~std-coding-style:20260114232758

---

---
name: std-coding-style
description: Coding style best practices including naming conventions, formatting, and code organization
---

## Coding style best practices

- **Consistent Naming Conventions**: Establish and follow naming conventions for variables, functions, classes, and files across the codebase
- **Automated Formatting**: Maintain consistent code style (indenting, line breaks, etc.)
- **Meaningful Names**: Choose descriptive names that reveal intent; avoid abbreviations and single-letter variables except in narrow contexts
- **Small, Focused Functions**: Keep functions small and focused on a single task for better readability and testability
- **Consistent Indentation**: Use consistent indentation (spaces or tabs) and configure your editor/linter to enforce it
- **Remove Dead Code**: Delete unused code, commented-out blocks, and imports rather than leaving them as clutter
- **Backward compatibility only when required:** Unless specifically instructed otherwise, assume you do not need to write additional code logic to handle backward compatibility.
- **DRY Principle**: Avoid duplication by extracting common logic into reusable functions or modules