Show HN: LangCSS – An AI Assistant for Tailwind
77 points| langcss | 1 year ago |langcss.com
This is my personal project that is an IDE and AI assistant for creating tailwind components and pages. You can chat to create designs, then make small edits yourself, and continue chatting to refine them. I am always working to improve the UX.
I have a time limited demo page here: https://langcss.com/demo, or you can sign up for free and use one of the 3 models for free.
Please let me know what you think! Feedback is welcome.
Originally this used NextJS (Hosted on Docker) and Azure Open AI. It now uses Vite/.NET (Still on Docker) in order to use a more familiar back end language. DB is postgres. AI is Groq/OpenAI Azure/Claude. (Groq for free version).
I think my next focus will be to make it so you can select parts of the design and run AI on those parts, which gets around the speed and context issues of working on larger designs. I also want to make a vanilla CSS (so no Tailwind!) mode. And look at integrating DaisyUI for the Tailwind users.
Previous submission: https://news.ycombinator.com/item?id=40143498
Since then there is now a proper back end, rather than just losing your work when you close the tab! It will save your session and you can have many projects. It also handles the custom @apply and custom Tailwind config, but admitedly not as well as play.tailwind.com yet!
[+] [-] dev213|1 year ago|reply
- Allow submission of a message with some sort of keyboard shortcut (enter and shift + enter only add a new line)
- Disable the "Send" button while the completion is loading, this prevents accidentally clicking send twice, causing the process to fail.
edit: formatting and typo
[+] [-] langcss|1 year ago|reply
[+] [-] abiraja|1 year ago|reply
[+] [-] cunningfatalist|1 year ago|reply
- Make a simple admin CRUD layout
- Add some widgets
- Add a login/logout section in the navbar
- Make it all responsive
The first three steps worked amazingly. But the final step was probably just too difficult and I got some broken-looking site.
Still nice though, good job.
[+] [-] dmix|1 year ago|reply
Most of the other 'studio' apps for CSS frameworks assume you're non-technical and overly hide the code or get too fancy with the output/editing.
I'm assuming the demo hides the code part because they want you to pay, so people don't just use the 20min demo repeatedly? It would have been nice to try to see how my own manual changes are handled.
[+] [-] langcss|1 year ago|reply
[+] [-] jamisonbryant|1 year ago|reply
One other unusual (but slightly entertaining) thing the model did was it used a different image for the notification "icon" every go-round. I have absolutely zero idea where it was getting the little icons (hallucinating?? maybe making a HTTP request??) but it was really interesting to see.
A neat tool, I will send it to my frontend guy at work and see what he thinks.
[+] [-] Brajeshwar|1 year ago|reply
It is not going to be Tailwind or more new frameworks. Honestly, I think all of these Bootstrap, Foundation, and Tailwind, etc. are like middle-layer abstractions are for designs that are neither small nor large. Bootstrap won because of the out-of-the-box UI designs that looked nice overall, and so did Tailwind. By the way, I love Tailwind's color palette, and I continue to steal from it all the time.
CSS (the actual raw CSS) has become so usable, easy and just works while browsers are so advanced these days, that I don't think we even need to reset/normalize/sanitize the styles.
The tools we need will soon be the ones that will integrate directly with IDEs, akin to how the likes of Figma are going. Imagine a designer either does an overall design or works on modules of components or StyleTiles that are reflected in the CSS either on its own or part of the Javascript-ified HTML markups. When a developer changes something, it is reflected back to the designer's tool so that the designer also knows what changed.
I believe this is where the AI-assisted ones will shine — their ability to bridge the relationship between the design and the code. The interface to interact with that can be the drawing tools (Photoshop, Affinity, Figma) for designers, prompts, or harry's wand (it does not matter).
In fact, for small projects, finish it off with a prompt and get a single Stylesheet blob with HTML, and for the larger ones, it can spit out its own Tailwind that talks back to the design tool.
References;
- https://getbootstrap.com
- https://get.foundation
- https://tailwindcss.com
- https://meyerweb.com/eric/tools/css/reset/
- https://necolas.github.io/normalize.css/
- https://csstools.github.io/sanitize.css/
- https://www.figma.com
- https://styletil.es
[+] [-] sabbaticaldev|1 year ago|reply
[+] [-] sgt|1 year ago|reply
> make me a nice round button
Success! Ok, let's try something very basic.
> it needs to have two parts, image on left side and text on right side
Then I got a system error
[+] [-] langcss|1 year ago|reply
[+] [-] ramon156|1 year ago|reply
[+] [-] ellisdg|1 year ago|reply
[+] [-] dmondok|1 year ago|reply
[+] [-] nocababges|1 year ago|reply
[+] [-] tazu|1 year ago|reply
[+] [-] toastercat|1 year ago|reply
[+] [-] replwoacause|1 year ago|reply
[+] [-] betimd|1 year ago|reply
[+] [-] langcss|1 year ago|reply
AI: Swapped out the back end so that is now working.
Signup: Now fixed - I have manually confirmed signups created in the time it was not sending.
[+] [-] Bharathkumar12|1 year ago|reply
[+] [-] ike0790|1 year ago|reply
[+] [-] Brajeshwar|1 year ago|reply
Can we do a LangCSS instead but for CSS? That will help someone new to learn better; otherwise, we are building abstraction on top of an abstraction of an abstraction.
Do one for CSS, then have features to convert that to the Tailwind or FooBar Framework of the future. See, Tailwind will also eventually go away, just as Bootstrap, Foundation, or Bourbon did. Developers who depend on the tools that help them write in these frameworks will always play catch-up and never learn the real thing (CSS, in this case).
[+] [-] afavour|1 year ago|reply
Tailwind is one of them and much like React it’s become such an abstraction over the underlying environment that you can become completely ensconced in its world without venturing to the APIs underneath.
[+] [-] langcss|1 year ago|reply
By the way the AI isn't because Tailwind is hard or obtuse to use. The AI is because you might need help with your design. Tailwind happens to be the output mode.
[+] [-] _andrei_|1 year ago|reply
[+] [-] datavirtue|1 year ago|reply
I LOVE Tailwind but see a clear need still for Bootstrap.
[+] [-] mhh__|1 year ago|reply
I'd go the other way here.
What did they do such that it's profitable (let's suppose it is for now) to have an AI tool: tailwind goes inline in the html, getting a lot of context to the LLM is much cheaper than having a bunch of random classes floating around
[+] [-] bigblind|1 year ago|reply
I'm toying a bit with this tool, and I think it's incredibly useful for prototyping.
[+] [-] unknown|1 year ago|reply
[deleted]
[+] [-] amsterdorn|1 year ago|reply
I'd much rather pay for ChatGPT, run Vite locally and prompt "You are a tailwind assistant that generates CSS..."
[+] [-] usernamed7|1 year ago|reply
[+] [-] throwaway054624|1 year ago|reply
But I see it as mostly useful in the beginning when you are starting, or want to create standalone components. It would be great if it was implemented as a plugin to an IDE and could understand and modify an existing project.
[+] [-] unknown|1 year ago|reply
[deleted]
[+] [-] fleetfox|1 year ago|reply
[+] [-] unknown|1 year ago|reply
[deleted]
[+] [-] pvg|1 year ago|reply
https://news.ycombinator.com/newsguidelines.html
[+] [-] unknown|1 year ago|reply
[deleted]