coding-standards

Files (2)

• SKILL.md
• SKILL.md.lock

SKILL.md (first lines)

<!-- bodyRef: skills/sources/coding-standards.md -->

<!-- Generated by `harness skills bootstrap`. Edit to tune; re-run to regenerate. -->
<!-- Static skills point at live docs by design — do not hardwire version-pinned API here. -->

Use this skill when writing or reviewing code for quality and maintainability.

## Concepts (timeless)
- Prefer the simplest solution that works; optimize for readability over cleverness.
- Small, focused units: functions do one thing; files stay cohesive (split before they sprawl).
- Favor immutability and pure functions; isolate side effects.
- Name things for intent; avoid magic numbers; delete dead code rather than commenting it out.
- High cohesion, low coupling; depend on interfaces, not concretions.

## Pull current docs first
Each language/framework has idioms + an official style guide and linter — follow theirs:
- your language's official style guide + the project's formatter/linter config
- Use the project's formatter + linter config as the source of truth; don't weaken it to pass.

## Checklist
- [ ] Functions small + single-purpose; files cohesive
- [ ] Clear names; no magic numbers; no dead/commented-out code
- [ ] Side effects isolated; immutable data preferred
- [ ] Matches the project's formatter/linter (config unchanged to "pass")
- [ ] Public surface documented where non-obvious

## Gotchas

_Highest-signal section. Seed empty; grow it from real failures this skill
hits — `harness skills propose` suggests entries here from drift evidence._

- _none observed yet_

From ichiorca/shipsignal, Apache-2.0.

More from ichiorca/shipsignal