Goal: readable, maintainable, explainable code.
silkietools/.github stores org defaults used across repositories.
- Submit code you can explain end-to-end.
- For new features, prove added lines are worth maintenance liability.
- Remove dead code; do not ship commented-out logic or unused helpers.
- Avoid clever or spaghetti patterns; optimize for fast reasoning.
- Use explicit, descriptive names for files, folders, functions, variables.
- Keep behavior unambiguous; avoid unclear abbreviations.
- Keep pull requests focused on one logical change.
- Functional change summary
- Why code exists
- Why extra lines are worth liability
- Validation or test evidence
- emojis == straight to jail (emoticons are fine)
- make me read too much == straight to jail
- writing complete sentences == straight to jail
- docstrings that explain a code signature when anyone can read the fucking method == straight to jail