Skip to content
Development
Skill

/litestar-plugins

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

From plugin
litestar
1431 skills1 agent1 hook
Install
$ npx -y skills add litestar-org/litestar-skills --skill litestar-plugins --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/litestar-plugins

Context preview

The summary Claude sees to decide when to auto-load this skill.

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

SKILL.md

litestar-plugins.SKILL.md
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](references/plugins.md)
  • Pair with [litestar-autowire](../litestar-autowire/SKILL.md) for

domain-package controller and listener discovery.

  • Pair with focused first-party plugin skills when available.

<workflow>

Workflow

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

</workflow>

<guardrails>

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.

</guardrails>

<validation>

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.

</validation>

<example>

Example

from litestar import Litestar
from litestar_autowire import AutowireConfig, AutowirePlugin

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

</example>

References Index

  • [plugins.md](references/plugins.md)

Official References

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

Shared Styleguide Baseline

  • [General](../litestar-styleguide/references/general.md)
  • [Python](../litestar-styleguide/references/python.md)
  • [Litestar](../litestar-styleguide/references/litestar.md)
Read more
Ships withlitestar

Opinionated, first-party agent skills, plugins, subagents, slash commands, and MCP servers for the Litestar framework and its ecosystem — publishable to every major AI agent and IDE from a single repo.

Get the whole plugin

Other skills on litestar.