litestar-plugins

Sterne13

Forks0

Aktualisiert23. Juli 2026 um 16:30

Auto-activate for plugins=, InitPlugin, CLIPluginProtocol, SerializationPluginProtocol, OpenAPISchemaPluginProtocol, AutowirePlugin, or app plugin lists. Not for package installation.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Quelle

litestar-org

litestar-org/litestar-skills

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

2 Dateien

SKILL.md

readonly

name	litestar-plugins
description	Auto-activate for plugins=, InitPlugin, CLIPluginProtocol, SerializationPluginProtocol, OpenAPISchemaPluginProtocol, AutowirePlugin, or app plugin lists. Not for package installation.

Litestar Plugins

Use this skill for plugin composition, first-party plugin setup, plugin protocol authoring, and app startup wiring.

Code Style Rules

Prefer first-party Litestar plugins where they exist.
Keep plugin configuration near app setup or settings modules.
Use InitPlugin for reusable app initialization; keep protocol names for legacy code and non-init hooks.
Keep domain routes and plugin lifecycle concerns separated.

Quick Reference

Plugin patterns: plugins.md
Pair with litestar-autowire for domain-package controller and listener discovery.
Pair with focused first-party plugin skills when available.

Workflow

Identify whether the task is app composition or plugin authoring.
Use existing first-party plugins before custom glue.
Register plugins in app setup with settings-backed config.
Test startup, shutdown, CLI, or schema behavior touched by the plugin.

Guardrails

Do not hide route logic inside plugin setup.
Do not add a custom plugin where a plain provider or middleware is enough.
Do not scatter plugin config across unrelated modules.
Do not bypass first-party plugins for common integrations.

Validation Checkpoint

Plugin config is settings-backed when environment-specific.
Startup and shutdown behavior are covered.
Plugin protocols match the integration point.
App setup remains readable.

Example

from litestar import Litestar
from litestar_autowire import AutowireConfig, AutowirePlugin

app = Litestar(
    plugins=[
        AutowirePlugin(
            AutowireConfig(domain_packages=["app.domain"]),
        )
    ],
)

References Index

plugins.md

Official References

https://docs.litestar.dev/ - Litestar documentation
https://docs.litestar.dev/latest/reference/ - Litestar API reference

Shared Styleguide Baseline

Mehr aus diesem Repository

gleiches Repository

advanced-alchemy

litestar-org/litestar-skills

Auto-activate for advanced_alchemy imports, alembic/, SQLAlchemyAsyncRepositoryService, SQLAlchemyAsyncConfig, repository_type, service_class, filters, or storage. Not for raw SQLAlchemy without Advanced Alchemy — use SQLAlchemy guidance.

2026-07-2313

litestar-auth-guards

litestar-org/litestar-skills

Auto-activate for guards=, Guard, ASGIConnection, JWTAuth, JWTCookieAuth, SessionAuth, role or tenant checks, or WebSocket auth. Not for frontend route protection.

2026-07-2313

litestar-autowire

litestar-org/litestar-skills

Auto-activate for litestar_autowire, AutowirePlugin, AutowireConfig, domain_packages, AutowireIntegration, AutowireLoader, clear_autowire_cache, or automatic controller/listener/task discovery. Not for manual Router composition — keep explicit wiring when discovery adds no value.

2026-07-2313

litestar-di

litestar-org/litestar-skills

Auto-activate for Provide, NamedDependency, SkipValidation, Dependency(skip_validation=True), dependencies=, litestar.di, Dishka FromDishka, Inject, or providers. Not for plain parameters.

2026-07-2313

litestar-dto-openapi

litestar-org/litestar-skills

Auto-activate for MsgspecDTO, DTOConfig, litestar.dto, OpenAPIConfig, response DTOs, schema_extra, RequestEncodingType, or /schema. Not for persistence models alone.

2026-07-2313

litestar-email

litestar-org/litestar-skills

Auto-activate for litestar_email, EmailPlugin, EmailConfig, EmailService, EmailMessage, SMTPConfig, ResendConfig, SendGridConfig, MailgunConfig, SESConfig, or InMemoryBackend. Not for marketing-campaign platforms — use their dedicated SDKs.

2026-07-2313

Litestar Plugins

Use this skill for plugin composition, first-party plugin setup, plugin protocol authoring, and app startup wiring.

Code Style Rules

Prefer first-party Litestar plugins where they exist.

Keep plugin configuration near app setup or settings modules.

Use InitPlugin for reusable app initialization; keep protocol names for legacy code and non-init hooks.

Keep domain routes and plugin lifecycle concerns separated.

Quick Reference

Plugin patterns: plugins.md

Pair with litestar-autowire for domain-package controller and listener discovery.

Pair with focused first-party plugin skills when available.

Workflow

Identify whether the task is app composition or plugin authoring.

Use existing first-party plugins before custom glue.

Test startup, shutdown, CLI, or schema behavior touched by the plugin.

Guardrails

Do not hide route logic inside plugin setup.

Do not add a custom plugin where a plain provider or middleware is enough.

Do not scatter plugin config across unrelated modules.

Do not bypass first-party plugins for common integrations.

Validation Checkpoint

Plugin config is settings-backed when environment-specific.

Startup and shutdown behavior are covered.

Plugin protocols match the integration point.

App setup remains readable.

Example

from litestar import Litestar from litestar_autowire import AutowireConfig, AutowirePlugin app = Litestar( plugins=[ AutowirePlugin( AutowireConfig(domain_packages=["app.domain"]), ) ], )

References Index

Official References

Shared Styleguide Baseline