backend-style

Define explicit conventions for line length, formatting, imports, and naming, then apply them during code writing and review. This Skill encodes rules like 100-char lines, top-of-file imports, and one class per file so the AI follows them automatically.

Validate at the boundary, such as the request handler, serializer, or schema layer, and never re-validate downstream. Internal code and framework guarantees should be trusted once data passes the boundary.

Raise specific exceptions instead of generic Exception or Error types, catch only what you can handle, and let unexpected errors propagate. Bare except clauses and silently swallowed errors are explicitly forbidden.

Yes, the conventions cover both ecosystems, specifying snake_case for Python and camelCase for JS/TS, plus docstring or JSDoc requirements. Formatter and linter commands are placeholders you adapt to your project's toolchain.

Always prefer the project's ORM or query builder, using raw SQL only with a documented specific reason. Optimize with select_related or eager loading for foreign keys and bulk operations for more than 10 writes.