litestar-styleguide

What problem does it solve?

Without a shared baseline, every Litestar skill would duplicate inconsistent rules for code style, testing, CI/CD, and language-specific conventions, leading to fragmented, conflicting guidance for AI agents building Litestar projects.

Core Features & Use Cases

• Cross-Cutting Style Baseline: Centralizes generic rules for Python (PEP 604 unions, ruff/mypy/pyright), TypeScript, testing (pytest/Vitest), and CI/CD so no individual skill duplicates them.
• Litestar-Specific Conventions: Codifies framework best practices for route handlers, DTOs, dependency injection, guards, and plugin development.
• Single Source of Truth: All other Litestar skills link to this baseline instead of copying rules, ensuring consistent guidance across the entire plugin ecosystem.
• Use Case: When building a Litestar app with advanced-alchemy and Dishka, an AI agent references this skill first to apply consistent type hints, async I/O patterns, and test conventions before implementing skill-specific features.

Quick Start

Use the litestar-styleguide skill to apply consistent Python type hints, async I/O patterns, and Litestar framework conventions when generating new project code.