litestar-styleguide
This is the shared style baseline that every other skill in this plugin references. It exists so that cross-cutting rules (PEP 604 unions, async I/O, ruff + mypy + pyright, test file naming, CI/CD conventions) live in exactly one place — and individual skills stay focused on their framework or tool-specific surface.
What's in here
Each reference covers one slice of the code-style baseline. A sibling skill links to only the files relevant to its language / framewor
[Description truncada. Veja o README completo no GitHub.]