stelow-workflow-coding-standards

Product Coding Standards

Self-contained. This skill includes universal coding principles — no external prerequisite skills needed.

---

Core Principles

1. KISS — Keep It Simple, Stupid

Prefer the boring solution. Clever code is a liability for both humans and LLMs.

• No function >50 lines (Go: 100 lines)
• No file >400 lines (Go: 500 lines)
• Cyclomatic complexity per function <10
• Max 3 indentation levels (use early returns / guard clauses)

2. DRY — Don't Repeat Yourself

Wait for the third repetition before abstracting. Premature DRY creates the wrong abstraction.

• Logic duplication → extract shared function
• Configuration duplication → centralize in constant/config
• Template duplication → create partial/component
• Duplication >5% of file is a warning sign

3. Convention over Configuration

Follow established conventions of the language/framework before introducing custom config.

• Sensible defaults, standardized names, predictable directory structure
• Explicit configuration only when deviating from convention
• Predictable patterns are a force multiplier for LLMs and developers

4. Progressive Disclosure

Simple by default, complexity behind toggles.

• Essentials first, advanced later
• Skills should structure content in 3 tiers: metadata → instructions → references
• Avoid overwhelming with options upfront

5. Polymorphism When Useful

Interfaces for extensibility only when it adds real value.

• Prefer concrete types over premature abstractions
• Don't create interfaces for a single implementation
• Add interfaces when you have 2+ concrete implementations

6. Locality of Behavior (LoB)

Behavior lives close to where it's used — in the template/view that owns it.

• Use the framework's native declarative attributes before custom JavaScript
• Inline JS only when framework doesn't offer native behavior
• Frontend is a dumb reactive terminal — minimum possible logic on the client

7. Separation of Concerns (SoC)

For backend code and multi-layer frameworks.