ref-sp-dev-coding-patternslisted

# Coding Patterns ## Purpose Provide portable defaults for writing code that is explicit, intention-revealing, easy to test, and easy to maintain across languages. ## When to use this skill - Choosing general coding defaults for a new feature or repository. - Refactoring code that is hard to read, weakly typed, or over-coupled. - Deciding when comments help and when they are noise. - Designing a CLI or automation surface. - Reviewing whether tests actually cover risky behavior. ## Scope Boundaries - Use this skill for language-agnostic defaults such as naming, comments, branching, CLI ergonomics, and testing posture. - Use `ref-sp-dev-projects-architecture` for folder layout, feature boundaries, and shared-utility decisions. - Use `ref-sp-py-python`, `ref-sp-js-javascript`, or `ref-sp-js-typescript` for syntax- and runtime-specific guidance. - Use a repo-local conventions skill (in this repo, `ref-sp-dev-repo-conventions`) when the question is about a specific repository's exact paths or commands. ## Defaults - Prefer strict typing when the language supports it. - Prefer explicit boundaries over clever inference at I/O edges. - Prefer names that scream intent over vague verbs. - Prefer early returns over deep nesting. - Prefer small focused functions over multi-purpose handlers. - Prefer modules whose import has no side effects; defer real work to functions, factories, or explicit initialization. - Prefer safe CLI defaults and discoverable help. - Prefer focused tests