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 / framework mix.

• references/general.md — Cross-language principles (simplicity over cleverness, error handling, naming, DRY-when-it-pays)
• references/python.md — Python conventions (PEP 604 unions, docstrings, imports, ruff / mypy / pyright configuration)
• references/litestar.md — Litestar-specific baseline (guards, DTOs, DI, plugin use)
• references/typescript.md — TypeScript conventions (when paired with a frontend skill)
• references/testing.md — Testing conventions (pytest, vitest, fixtures, coverage)
• references/ci-cd.md — CI/CD conventions (GitHub Actions, matrix builds, caching)

How sibling skills consume this

Every SKILL.md in this plugin has a ## Shared Styleguide Baseline section near the bottom. That section links to a subset of these references — only the ones that apply to the skill's language / framework mix. For example: