Approved Practices

For when the work is dark, mysterious, and must still compile.

Welcome to a growing collection of coding standards, style preferences, and tooling conventions.
This isn’t The Law™ — but it is The Manual I Wish I Had Yesterday™.

Whether you’re revisiting an old repo, spinning up a new one, or just arguing about tabs vs spaces (again), this guide’s here to bring consistency with a light touch.

🔎 What’s inside

These sections are living documents — just like the code they support:

• 📐 Typography
  Font choices, heading hierarchy, and why Comic Sans is still banned

• 🎨 Colors
  Brand palettes, contrast checks, and the hex codes I always forget

• 🗣️ Voice & Tone
  Writing like a human (even in 404 pages and commit messages)

• 🧱 Layout Guidelines
  Page grids, spacing rhythm, and the occasional rant about “centered” buttons

• 💾 Tool Configs
  .editorconfig, pre-commit hooks, linter settings — so your tools don’t fight each other

• 💻 Code Style
  Python, JS, and C# conventions (with examples and formatting rules)

• 🧰 Templates
  Email snippets, markdown doc starters, and presentation slide skeletons

💡 Philosophy

This guide is backend-first, frontend-curious, and allergic to decision fatigue.
It values clarity, flexibility, and knowing when to break the rules we wrote ourselves.

“A foolish consistency is the hobgoblin of little minds — but also, maybe just lint your files.”

If you’re ready to explore the conventions, head into the Style Guide — or take a detour through the Code Style forest.