litestar-static-files
Static Files
Execution Workflow
- Decide whether the app needs normal asset serving, downloadable files, or static HTML mode.
- Mount assets with
create_static_files_router()under an explicit path and controlled directories. - Set delivery behavior intentionally: inline vs attachment, HTML mode, name, schema visibility, and router metadata.
- Choose cache behavior that matches asset mutability and deployment strategy.
- Lock down file system boundaries, especially symlink behavior and any remote/custom file system integration.
- Verify URL reversal,
404behavior, and template references before treating the mount as stable.
Core Rules
- Prefer
create_static_files_router()for current Litestar static-file serving. - Keep static directories separate from writable upload or user-content directories.
- Use explicit URL prefixes such as
/staticor/assetsunless HTML mode intentionally owns/. - Treat directories as relative to the working directory unless you pass explicit absolute paths.
- Use
send_as_attachment=Trueonly when download behavior is intentional. - Use
html_mode=Trueonly when the mounted directory should behave like a static site root.
More from alti3/litestar-skills
litestar-responses
Build Litestar responses with typed return values, explicit Response containers, layered response classes, headers, cookies, status-code control, redirects, files, streams, server-sent events, ASGI app returns, and background tasks. Use when shaping outbound HTTP behavior, correcting response contracts, or choosing the right Litestar response primitive. Do not use for request parsing, validation, or authentication policy design.
22litestar-logging
Configure Litestar logging with `LoggingConfig`, `queue_listener`, exception logging policy, selective stack-trace suppression, standard logging, picologging, Structlog, and custom logging config subclasses. Use when establishing or refactoring application logging behavior, request-level logs, or production-safe error logging in Litestar. Do not use for metrics/tracing instrumentation or exception-response contract design.
22litestar-authentication
Implement Litestar authentication with custom authentication middleware, built-in security backends, JWT and session flows, route inclusion and exclusion rules, and typed auth context on `Request` / `ASGIConnection`. Use when establishing identity, issuing or validating credentials, or attaching authenticated user context in Litestar. Do not use for generic request parsing, broad security audits, or unrelated transport concerns.
22litestar-middleware
Design and apply Litestar middleware for cross-cutting concerns such as CORS, CSRF, allowed-host checks, compression, rate limiting, logging, sessions, request enrichment, policy enforcement, and custom ASGI pipeline control. Use when behavior must wrap broad route sets consistently across the ASGI stack. Do not use for route-specific business rules, simple response mutation better handled by lifecycle hooks, or auth/guard policy work that belongs in security-focused skills.
20litestar-routing
Design and implement Litestar routing with app/router/controller composition, handler decorators, path and parameter modeling, route indexing/reverse lookups, ASGI mounting, and layered route metadata. Use when creating or refactoring endpoint topology and URL contracts. Do not use for purely internal service logic unrelated to HTTP route structure.
18litestar-dto
Configure Litestar DTO behavior for inbound parsing and outbound serialization, including layer-scoped `dto`/`return_dto`, `DTOConfig` policies, `DTOData` update workflows, and custom `AbstractDTO` implementations. Use when API payload contracts differ from internal model structures. Do not use when internal models can be exposed safely without transformation.
18