Abilian Design System
This is a design system for business applications built on Litestar and Jinja, written in plain CSS with no front-end toolchain. A small set of knobs is the whole overridable surface; everything else is derived from them.
Documentation · Token and class reference · llms.txt
pip install abilian-ds # or: uv add abilian-ds
abilian-ds sync
It has no runtime dependencies and needs no build step.
The idea
Styling goes through a closed vocabulary: a --ads-* custom property or an ads-* class. There is no utility layer, no arbitrary-value syntax and no style= attribute. bg-gray-100, p-4 and text-[13px] generate no CSS at all, and abilian-ds lint rejects them before they can sit in a template looking plausible.
That closure is what makes the rest possible:
- Knobs are the overridable surface; everything else derives. Set
--ads-brandand its hover, active, tint, border and foreground shades follow. Set--ads-space-scaleand every padding, gap, margin and control height follows. One declaration on:rootchanges 361 of 501 elements on a page. - Both themes in one value. Every colour holds light and dark through
light-dark(). There is nodark:variant anywhere and so no second styling pass to forget. - State that a person can perceive is an attribute. The current item is
aria-current, a toggle isaria-pressed, an invalid field isaria-invalid. The stylesheet keys off those, so the look cannot exist without the meaning. - Measured parity with Tabler. A harness compares the two property by property and reports 0 differences.
- Accessibility with tests behind it: contrast in both themes, reflow at 320px, 200% text-only zoom, keyboard traversal, pointer target size and Windows high contrast, swept across every route on every run.
What sync gives you
static/css/ads/ads.css the stylesheet — one file, one request
static/css/ads/shell.js what the dropdowns, drawers and theme toggle need
static/css/ads/situ.css only if you use situ
templates/ads/shell.html the application frame, extended not copied
templates/ads/nav.html navigation rendered from data
templates/ads/form.html field, select, textarea, checkbox, button macros
Paths live in [tool.abilian-ds] in your pyproject.toml, so the commands take no flags:
[tool.abilian-ds]
templates = ["templates"]
prefix = "ads-"
A page
{% extends "ads/shell.html" %}
{% block title %}Contacts · Acme{% endblock %}
{% block brand_name %}Acme{% endblock %}
{% block heading %}Contacts{% endblock %}
{% block actions %}<button class="ads-btn ads-btn--primary">New contact</button>{% endblock %}
{% block body %}
<div class="ads-card"><div class="ads-card__body ads-stack">
<div class="ads-cluster">
<span class="ads-avatar ads-avatar--sm">AR</span>
<strong class="ads-truncate">Amélie Rousseau</strong>
<span class="ads-badge ads-tone-success">active</span>
</div>
</div></div>
{% endblock %}
The navigation is data, because markup drifts:
nav = [{"section": "Directory",
"items": [{"href": "/contacts", "label": "Contacts", "icon": "users"}]}]
Configure Jinja with undefined=StrictUndefined. It turns a misspelt component argument into an error, where it would otherwise yield an unstyled element.
The commands
| command | what it does |
|---|---|
abilian-ds sync |
vendor the stylesheet, the shell script and the macros into your project |
abilian-ds lint |
check templates against the design system |
abilian-ds tokens |
regenerate TOKENS.md from the stylesheet |
lint is the contract. Green means on-system:
templates/page.html:1: unknown-class: bg-gray-100: not in the design system
templates/page.html:2: dark-variant: dark:text-white: colours carry both themes, there is no dark pass
templates/page.html:2: arbitrary-value: text-[13px]: bypasses the token scale
templates/page.html:2: inline-style: style='color: red': a decision belongs in CSS
It also hashes every vendored file against what the package would produce, so a local edit to ads.css shows up as a finding.
What it does not do
- No icon set. The shell uses an
icon()Jinja global if you register one; an icon set is a licence you cannot change once it is baked in. How to wire one up. - No JavaScript framework.
shell.jsis a page of delegated event handlers with no dependencies. Components that need more (a rich data grid, a live region) are situ's job, andsitu.cssbridges the two palettes. - No CSS-in-JS, no theme builder UI, no component library for React. This is Jinja and CSS.
Status
Beta. The vocabulary, the linter and the shell are stable enough to build on; the 0.x version number covers the rest. See CHANGES.md.
Licence
Apache 2.0. Copyright © 2026 Abilian SAS.
Metadata
Release files for abilian-ds 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| abilian_ds-0.1.1.tar.gz | 92.1 kB | Without provenance | Details for abilian_ds-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| abilian_ds-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for abilian_ds-0.1.1-py3-none-any.whl |
Total release size: 192.4 kB
Release files / abilian_ds-0.1.1.tar.gz
| Download URL | abilian_ds-0.1.1.tar.gz |
|---|---|
| Size | 92.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6fd61ad3aab87d40340a15bd640c4ed068b00b814f501a673e6f668770902951
|
|
BLAKE2b-256 checksum How to use checksums |
36d54f70ada80cc5009cba8622170c5dcace11a1e11d51bc9f3400e5c2956ccb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / abilian_ds-0.1.1-py3-none-any.whl
| Download URL | abilian_ds-0.1.1-py3-none-any.whl |
|---|---|
| Size | 100.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a399ca7e947ed33d0686d58b193ff7a5af6eb5394686c0dd0d6e8859a356e199
|
|
BLAKE2b-256 checksum How to use checksums |
041a933aa5c6473746d3944b4129ba00affd29d30ca6580e45ed9eccf0aec9f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for abilian-ds 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.