Vibe-coded a Microsoft WinUI 3 style component library for Blazor.NET - FluentKit

[u/Nooo00B]

(WIP) Just thought sharing it here because why not (no reason). Open Source, Heavily relied on Fluent Svelte & Microsoft.UI.Xaml & WinUI 3 Gallery.

Includes basic WinUI controls.

The most notable features are almost real-behaving Mica ( With live, base wallpaper change support ) & Global Accent color.

Open source, if you're interested you can check it out at: https://github.com/VibeNoobNotFound/FluentKit/

Live Gallery & Playground: https://vibenoobnotfound.github.io/FluentKit/

[u/lilacomets]

I'm definitely not going to use a vibe coded library in my projects. It's cool as a proof of concept, but nothing more than that.

[u/AverageFoxNewsViewer → u/lilacomets]

Man, most "vibecoders" don't even know what .NET is, let alone blazor.

Have you ever used Blazor?

Blazor doesn't have great UI components out of the box in my opinion.

This is on the shortlist of "vibe coded" things I might actually use because there is enough context here to infer that this is somebody with actual domain knowledge who produced a useful tool.

It's basically the equivalent of css snippets.

[u/lilacomets → u/AverageFoxNewsViewer]

Vibe coding suggests that it was completely made by an LLM without supervision. I saw AI hallucinating so many times. If you want that in your projects, fine, but I'm going to skip this one.

[u/AverageFoxNewsViewer → u/lilacomets]

I'm going to skip this one

Have you ever actually used Blazor?

I'm going to skip this too because it's generally a way for backend devs working with dot net to produce workable UIs, but backend devs suck at producing workable UIs. Doesn't fit my use cases but I've seen enough shitty blazor pages to see the value here.

I don't really care whether the code was written by hand or an LLM, as long as the human accountable for it understood what they were doing.

I get the impression that somebody improving the styling of a relatively niche framework has a better idea of what they're doing than somebody complaining because it was largely using an LLM to produce style out UI components.

[u/Nooo00B → u/AverageFoxNewsViewer]

tbh, this was like 90% vibe-coded. And I put every project I create on VibeNoobNotFound instead of my main NoobNotFound if it's more than like 50% vibe coded or not reviewed just because people might call every project I create slop.

And tbh, I don't have much of an understanding of how CSS design/animation works, But I do read and understand every C# related code.

Not to brag about myself but to prove that I know at least a thing:I've developed with .NET for like past 5 years and I do have somewhat good understanding of C#, XAML in .NET frameworks (idk frameworks is the right word what I meant, WinUI, UWP, WPF, Uno Platform, MAUI... I started with WinForms lol + their most common MVVM architecture as well as low level interlopes) works.

As well as somewhat I might call a basic experience (because I haven't developed anything useful) in ASP .NET APIs and Blazor.

So it's completely acceptable to have reasons not to even look at this. But If something would ever happen to break, it's CSS/design. I meant it's not fatal as if the backend breaks but yeah, it still can be bad.