---
name: coding-bible
description: >-
  Use whenever writing, reviewing, or refactoring code anywhere in the ecosystem — backend
  (FastAPI / Python), infrastructure (Proxmox / Docker / networking), graph work (Neo4j /
  Cypher), or frontend. Encodes the engineering standards, conventions, and guardrails to
  follow before producing or changing code. Apply proactively on any coding task, not only
  when "standards" or "conventions" are mentioned.
license: MIT
---

# Coding Bible

<!--
  PASTE YOUR EXISTING CODING BIBLE CONTENT BELOW.
  Suggested shape (keep the body lean; split per-domain rules into references/):
-->

## When to use
<!-- Any code-producing or code-reviewing task across the stack. -->

## Universal principles
<!-- Stack-agnostic rules: style, naming, error handling, commit discipline. -->

## Domain rules
<!-- Per-area guardrails. Long ones belong in references/, e.g.:
     - references/neo4j-cypher.md   (verify-before-write, Chalices canonical, no TimeFrame nodes)
     - references/fastapi.md
     - references/proxmox-docker.md
   Point to each from here so they load only when relevant. -->

## Review checklist
<!-- The pass an agent runs before declaring code done. -->