r/sveltejs

TL;DR: https://windframe.dev/mcp

Hi everyone 👋

I’ve been working on a Tailwind-native MCP that gives coding agents better design context when generating  interfaces.

A lot of AI-generated UI still feels inconsistent because the agent has no real sense of design systems, spacing, typography, or visual structure. It can write Tailwind, but it often lacks the taste and context needed to make the result feel properly designed.

So I built the Windframe MCP around that idea.

It gives coding agents access to curated Tailwind-native styles, design tokens, and styleguides inspired by products like Linear, Notion, and other companies that invest heavily in their design systems.

The difference in output quality has been really impressive. The generated interfaces feel polished and visually cohesive, not like a random collection of Tailwind components.

I’ll keep adding new design styles to the MCP as well, so the library will continue to grow over time.

Give it a try here https://windframe.dev/mcp

Would love any thoughts or feedback :)

Introducing Svelte Dot Matrix Loaders

50+ Animated Dot Matrix loaders for Svelte

• Install using jsrepo / shadcn-svelte
• Easy to customize
• Includes ready-to-use examples

Live: https://sv-matrix.vercel.app
GitHub: https://github.com/SikandarJODD/sv-matrix
Docs: https://sv-matrix.vercel.app/docs/setup

Inspired from original Dot Matrix Loaders by Shawnn
Goal: bring similar experience to svelte ecosystem

i am using shadcn-svelte/jsrepo for distrubiton purpose.
i have provide 7 examples with AI chat, payment, fetch api, form submission, etc..

I’ve just launched https://templattr.com and I’m looking for feedback.
What have you built?

I’ve been building an Eloquent-inspired ORM for Bun called Bunny. I added a multi-tenant aware implementation because I am using this for a SaaS project of mine using Sveltekit + Bun.

It’s designed specifically for Bun’s native sql client, and it currently supports:

- SQLite, MySQL, and PostgreSQL

- Zero runtime dependencies

- TypeScript-first API

- Chainable query builder

- Schema migrations and CLI

- Model relations, observers, soft deletes, and streaming helpers

- Interactive REPL with bunny repl

- Dynamic multi-tenant connection switching

- Landlord / tenant migration groups

- PostgreSQL schema switching and RLS support

A big focus for me has been making multi-tenant apps easier to reason about. The ORM supports tenant resolution at runtime, so apps can switch connections based on request context, subdomain, or header without hardcoding all tenants in config.

Example:

await TenantContext.run("acme", async () => {

const users = await User.all();

});

You can also put a resolveTenant function in bunny.config.ts and reuse the same config in the CLI and app bootstrap.

I’m sharing it here in case it’s useful to anyone building on Bun, especially if you’ve wanted an ORM that feels more like

Eloquent but is Bun-native.

Repo: https://github.com/bunnykit/orm

Would love feedback on:

- the API shape

- multi-tenant design

- SQLite/MySQL/Postgres support

- anything that feels awkward or missing

Motion Core has just reached 500 stars on GitHub! 🥳

To celebrate, I’m releasing a new component:

Glass Logo. Starting now, you can enhance your websites by turning your SVG brand assets into animated glass logos!

https://motion-core.dev/docs/glass-logo

More of an experiment than something serious, but I'm curious what people think.

The game's mechanics are a lot deeper than they might seem at first glance. You can add almost anything into it via /create {something}.

Link: https://asciidia.com

Scale or change your images with a JavaScript. https://youtu.be/fK_-OyolZ_Q

Hi everyone! 👋

I'm fairly new here, so I hope this kind of post is welcome — please let me know if there's a better place to share it!

I just wanted to give a heads-up that jscpd v4.2.0 has landed with official Svelte support, and I thought the community might find it genuinely useful.

---

What is jscpd?

If you haven't come across it before, jscpd is a copy/paste detector for source code. It scans your project, finds duplicated blocks across files, and reports them — a really handy tool for spotting technical debt before it piles up. It supports 150+ languages and formats, and now .svelte is officially one of them.

---

Why does this matter for us?

Svelte's component model makes it wonderfully easy to build UIs quickly — but in larger projects it's easy to accidentally duplicate logic across components: repeated event handlers, similar reactive declarations, copy-pasted template sections. Having a tool that understands .svelte file structure (rather than just treating them as plain text) means you can actually catch those patterns automatically.

---

Getting started is pretty simple:

npm install -g jscpd
jscpd --format svelte ./src

You can also add it to your CI pipeline with a threshold to fail the build if duplication gets too high:

jscpd --format svelte --threshold 5 ./src

---

I've been wanting this for a while in my own Svelte projects, so I was really happy to see it land. Huge thanks to the maintainers for making it happen! 🙏

Full changelog here if you're curious: https://github.com/kucherenko/jscpd/blob/master/CHANGELOG.md

Hope this is helpful to someone — happy to answer any questions if I can! 😊

Big news for svelte devs (I think), I have created (or Claude did if we are being truthful) some svelte tools. I've been using svelte daily at work for the last 3-4 years and I've always been amazed at the lack of dev support in svelte but I am not that amazing of a programmer and neither do I have months to spend developing them, so out of curiosity I asked Claude to create the dev-tools. To my amazement after millions of tokens out of my pocket and a week of back and forth with Claude things actually seem to be fully functional.

They run as a plugin inside Vite devtools, or standalone tab with a little different rendering if you're not using those. Idk how they work without Vite, or if they do at all.

Don't get to hyped, they are not polished and it might be just a "it works on my device" vibed slop thing, but I think it's something that might save some other people dev time. I tried to refine them as much as I could and test them in both demo apps but also some much bigger projects but can't guarantee anything.

You can find the Github repo here:

https://github.com/Zixtar/vite-plugin-svelte-devtools

I'd be happy to hear what's broken, and would like more ideas on new features that could help the svelte development if added, but be mindful I am almost out of tokens for now and I won't touch the code with a 10 ft. pole manually.

Also any criticism towards the "release" part is welcome as well, I have no idea what I'm doing regarding the npm package so if anything is wrong do tell.

Hello beautiful people of reddit, it's been roughly seven months since I've shared Aphex when it was super early on in it's development. I've been at it on and off since then just improving the core packages and functionality of the CMS and it's getting to a pretty good point~ Not an official V1 release yet though since I have a bunch of things I neeeeeed to get done.

BUT, I just wanted to share it as it is - so I can get people interested in testing and submitting bugs, to improve it and prep for production! so do share it around with people you think might be interested!

As for updates, first of all I've since switched from hosting the site on my old ass gaming laptop into a combination of a VPS and a HP Elitedesk 800 G4 in my bedroom - hell yeah! I've spun up three public sites:

1. Aphex CMS landing page (https://getaphex.com/) - snazzy landing page built on Aphex
2. Aphex CMS docs page (https://docs.getaphex.com/) - dev docs built on fumadocs!
3. Aphex CMS demo page (https://demo.aphex.studio/) - demo site page built on Aphex

There are too many changes to list from the last time but I'll highlight the important ones:

• Local API (type safe data interaction within the server) - inspired by PayloadCMS's
• Singleton types + document and field grouping + access control
• Version history
• Publish and Draft lifecycle
• Media browser
• Base Template (pnpm create aphex or https://github.com/IcelandicIcecream/aphex-base)

I've been testing it a bunch on internal and public-facing projects, and it's pretty usable BUT do keep in mind that there are potentially a bunch of breaking changes that will be made within the next few months to prep for an official V1 release. Despite being just a version bump away, there might be changes in how stuff is structured!

What's next (subject to change):

• Visual editing via vercel's stega
• Document and Array thumbnail previews (like Sanity's)
• SQLite adapter for db (potential with turso or libsql)
• Website Template + "Recipes" in docs
• A more polished media browser experience
• Better user and org settings
• Better concurrent document handling

I've been paying out of pocket for everything so far, so if anyone is interested in helping me out - I have Github Sponsors page setup OR I really don't mind some compute to host stuff :)))

Using sveltekit and svelte-shadcn with the same tree structure.