From litestar-skills
Shared code-style baseline for every skill in this plugin. Use when authoring or reviewing code in a Litestar / Python / TypeScript project — PEP 604 unions, async I/O, Google docstrings, msgspec over Pydantic, ruff / mypy / pyright tooling, pytest conventions, CI/CD rules. Produces: links to language-specific style references consumed by sibling skills via their `Shared Styleguide Baseline` sections. Use when: writing a new skill, reviewing code in this repo or a consumer project, or resolving a style disagreement. Not for framework-specific guidance (see the individual skills: litestar, sqlspec, advanced-alchemy, msgspec, etc.) — this skill is the cross-cutting baseline, not a framework guide.
npx claudepluginhub litestar-org/litestar-skills --plugin litestar-skillsThis skill uses the workspace's default tool permissions.
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.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Builds scalable data pipelines, modern data warehouses, and real-time streaming architectures using Spark, dbt, Airflow, Kafka, and cloud platforms like Snowflake, BigQuery.
Builds production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. For data pipelines, workflow orchestration, and batch job scheduling.
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.
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)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:
skills/litestar/SKILL.md links to general.md + python.md + litestar.mdskills/litestar-vite/SKILL.md links to general.md + typescript.md + litestar.mdskills/litestar-testing/SKILL.md links to general.md + testing.md + python.md + litestar.mdThe sibling skill extends the baseline with its own tool-specific Code Style Rules, Quick Reference, Guardrails, and Validation — but it does not duplicate the baseline. If a convention is generic (type hints, naming, imports), it belongs here.
references/<lang>.md and link from skills that use it.python.md once; all sibling skills inherit it.skills/<name>/SKILL.md).## Shared Styleguide Baseline section — it already lists a subset of the references here.references/ here. Specific → keep it in the sibling.## Shared Styleguide Baseline section resolves to files that exist under references/Reason: explanationreferences/<lang>.md — not scattered into sibling skillsA reviewer finds that two sibling skills independently wrote "use ruff format not black". Instead of leaving duplicates, pull the rule into references/python.md:
- **Use `ruff format`, never `black`.** Reason: ruff is the single toolchain for
lint + format; running two formatters produces style drift.
Then in each sibling's SKILL.md, replace the duplicate with a pointer:
## Shared Styleguide Baseline
- [Python](../litestar-styleguide/references/python.md)
</example>