Project Library In active development

xvelte

The pieces I always ended up building again. Now they all live in the same drawer.

A personal collection of components, hooks, attachments, styles and utilities for building interfaces with SvelteKit. Copy them into your project, adapt them and they become yours. No need to wrestle with someone else's API to move three pixels.

Type
Library
Status
In active development
Base
Svelte 5 · Tailwind CSS
License
MIT

More than a UI kit

A toolbox, not a showcase.

xvelte was created to gather the reusable code needed to build real applications: from a button through to interface state, localisation or desktop integration.

01 / UI

Components

Composite primitives and interfaces for forms, navigation, data, multimedia, messaging, and desktop tools.

  • Visual system: Tokens, light and dark themes, global styles and semantic icons that maintain a common language without tying the design.

02 / APP

Reusable logic

Hooks, attachments and utilities for resolving interactions and state without rewriting the same piece in every project.

  • Real applications: Localisation with Paraglide and Tauri integrations, alongside the usual SvelteKit web foundation. It does not live only in a pretty gallery.

An important idea

Copying is not the last resort. It is the model.

There is no package with a rigid API, no component registry and no CLI. You choose a stable version, copy only what you need and that code becomes part of the application. You can change the structure, styles, dependencies or behaviour without waiting for a new package option. In return, you are also responsible for what you copy. Freedom, with an instruction manual. Fair enough.

A component already in the project
<script lang="ts">
  import * as Button from "$lib/components/ui/button";
</script>

<Button.Root variant="success">Saved</Button.Root>
Normal, editable code with no magic hidden on another server.

Workflow

From collection to your project

  1. 01

    Choose

    Start from a stable release and review the guide for the piece you are going to use.

  2. 02

    Copy

    Add to the project the component and the specific dependencies it needs.

  3. 03

    Adapt

    Adapt the code to the application without getting trapped in an API designed for everyone.

Real-world use

Made for projects, not for an eternal demo.

The same foundation works for websites, internal dashboards, Electron or Tauri applications and highly interactive interfaces. The documentation site is the test bed; real software is the destination.

View of the xvelte documentation used as the collection's test bed

Contact

Shall we talk about your next project?

Got an idea, a website in need of a renovation or a computer that only works when the technician turns up? Tell me about it. I will explain clearly what can be done, whether it makes sense and what the next step would be.

Right now

Available for selected projects, collaborations and technical enquiries.

Usual response time
1–2 working days
Location
Salvaterra de Miño, Galicia