Djinn UI
The First True shadcn/ui Equivalent for the Django Monolith.
Stop wasting weeks building UI components from scratch or fighting rigid frontend frameworks. Djinn UI is a CLI-driven component registry that delivers beautifully styled, accessible, and responsive Tailwind CSS components directly into your Django templates.
No vendor lock-in. No heavy JS frameworks. No locked pip libraries. Just clean, native Django code that you own completely.
🚀 The Paradigm Shift
Modern frontend ecosystems (React, Next.js) have premium, plug-and-play component delivery systems like shadcn/ui. Meanwhile, Django developers have been left choosing between heavy runtime packages with custom template syntax, or locked third-party packages that are impossible to customize without brutal CSS overrides.
Djinn UI brings the copy-paste ownership model to the Python world. It isn't a runtime dependency. It is a scaffolding engine.
How it compares:
| Feature | Locked Pip Packages | Heavy Runtime Tools | Djinn UI |
|---|---|---|---|
| Delivery Model | Distributed via pip |
Complex Server Logic | CLI Scaffolding |
| Runtime Overhead | Low (but rigid) | High (Custom engines) | Zero (Native Django) |
| Customization | Painful CSS overrides | Limited by library API | 100% Free (It's your code) |
| AI Workflows | Hidden from LLMs | Hard for AI to reason | Built-in MCP Server |
🎨 The Web Builder & Canvas
Djinn isn't just a CLI—it is a visual component ecosystem. Djinn UI ships with a fully interactive local Drag & Drop Canvas Builder and Component Explorer.
- Interactive Canvas: Drag and drop Djinn components visually to build full layouts, then instantly copy the generated, production-ready Django template code.
- Custom Namespaces (
@internal/): Create and host your own private design systems for your team or agency. Usedjinn add @internal/dashboard-cardto pull components securely. - Preset Sharing: Instantly share complex, pre-configured component layouts with your team using short-links (
/c/xyz123).
🤖 Built for the Agentic Era
Djinn UI is the only Django component registry designed from the ground up for AI-assisted workflows (vibecoding).
It ships with a built-in Model Context Protocol (MCP) Server. When you connect it to AI agents like Cursor or Claude, your assistant can natively read, understand, and scaffold your custom UI setup.
Example Prompt for Cursor: "Use my Djinn components to build a beautiful SaaS billing dashboard page with a 3-tier pricing breakdown."
📦 Installation & Usage
Get up and running in less than 60 seconds.
1. Install the CLI via PyPI
pip install djinn-ui
2. Initialize Djinn in your Django Project
djinn init
This configures your components directory and ensures compatibility with your Tailwind CSS setup.
3. Add a Component
Want a clean, fully-styled dashboard layout or a functional modal? Just call the Djinn:
(Insert a fast-paced GIF here showing
djinn add dashboardalongside the rendered browser output!)
djinn add dashboard
The raw, clean HTML (and any optional Alpine.js interactions) is instantly dropped right into your project's local templates directory.
4. Render Natively
Use standard, vanilla Django {% include %} tags out of the box:
{% include 'components/ui/dashboard.html' %}
🧩 Tech Stack Philosophy
Djinn UI is built for developers who believe in the power and simplicity of the clean monolith. It pairs perfectly with:
- Django (Native templating, no complex SPA decoupled overhead)
- Tailwind CSS (Utility-first styling, easily configured via
tailwind-mergeutility tag{% cn %}) - HTMX & Alpine.js (For crisp, lightweight, SPA-like reactivity without leaving your Python ecosystem)
🗺️ Roadmap & Ecosystem
- Core CLI Architecture & Core Scaffolding Engine
- Built-in MCP Server for AI/LLM context injection
- Foundational UI blocks (Buttons, Inputs, Modals, Cards)
- Visual Drag & Drop Component Canvas
- Custom Namespace Routing for Private Design Systems
- Premium "Djinn Pro" block expansion (SaaS landing pages, complex charts, data tables)
- Multi-variant theme generator
📄 License
Distributed under the MIT License. See LICENSE for more information.
Metadata
Release files for djinn-ui 0.1.11
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 |
|---|---|---|---|---|
| djinn_ui-0.1.11.tar.gz | 76.1 kB | Without provenance | Details for djinn_ui-0.1.11.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| djinn_ui-0.1.11-py3-none-any.whl | Python 3 | none | any | Details for djinn_ui-0.1.11-py3-none-any.whl |
Total release size: 253.4 kB
Release files / djinn_ui-0.1.11.tar.gz
| Download URL | djinn_ui-0.1.11.tar.gz |
|---|---|
| Size | 76.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
23e411558cf6b387e5f1c046fa23ea386eb18ab77bc54d45e250636d50531a36
|
|
BLAKE2b-256 checksum How to use checksums |
77b952a712e556141a4a246d249a470d59a3b62b7a60d019ae400066a78e2545
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / djinn_ui-0.1.11-py3-none-any.whl
| Download URL | djinn_ui-0.1.11-py3-none-any.whl |
|---|---|
| Size | 177.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
779015b7380d8cbe7991a36fbad93d054f3b4f3f5a8c171430260d38007b57a7
|
|
BLAKE2b-256 checksum How to use checksums |
52c97b985493443c9a1c44ff50c19ef16898fa61de4cc1ed62f48d9f77541713
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for djinn-ui 0.1.11
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.