mcpField
B
basmilius

basmilius

github.com/basmiliusDevelopment096 installsUpdated 3d ago
Repository

About basmilius

basmilius is a set of guides for using the @basmilius npm packages across utilities, typed HTTP data access, and Vue 3 application primitives. It helps developers working with these packages find the relevant guide and patterns for each layer.

Key features

  1. 01Framework-agnostic utility guidance
  2. 02Typed DTO and HTTP service patterns
  3. 03Vue 3 store and composable guidance
  4. 04Package-specific reference catalogs
  5. 05Cross-layer implementation recipes

Use cases

  1. 01Finding a helper for dates or downloads
  2. 02Defining DTOs, adapters, and services
  3. 03Building Vue data tables or forms

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/basmilius/skills --skill basmilius

After installing, type/basmiliusin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
common-patterns.md
common-reference.md
common.md
http-client-patterns.md
http-client-reference.md
http-client.md
utils-function-index.md
utils.md

Details

From the project README

Bas Milius packages

The @basmilius npm scope is one stack in three layers, each covered by a guide in references/:

  1. @basmilius/utils - ~45 framework-agnostic helpers (dates via Luxon, colors, numbers, downloads, DOM, timing, geo/astro, seeded PRNG). Usable in any TypeScript project.
  2. @basmilius/http-client - the typed data layer: every body a @dto class, every endpoint group a BaseService, raw snake_case JSON mapped by a static @adapter. Builds on utils.
  3. @basmilius/common - Vue 3 app primitives: a ref-returning defineStore, useService + guarded, useDataTable / useDataReport, useDtoForm, a large composable catalog and thin vue-router wrappers. Assumes Pinia and Vue Router, builds on both packages above.

Shared assumptions: a Vue 3.6 pre-release where Vue is involved (exact range per the package's peerDependencies), luxon as a peer for dates. @flux-ui/* is a separate library with its own skill (flux-ui); @basmilius/vite-preset is deliberately not covered.

Routing: read the package guide before writing code

The per-package traps and judgment live in the guides, not here. Read the matching guide first, then dip into the signature/pattern files as needed:

Working onRead firstThen as needed
A date/number/color/download/DOM helper, or anything imported from @basmilius/utilsreferences/utils.mdreferences/utils-function-index.md (every function with exact signatures and the browser-vs-pure split)
DTOs, adapters, services, requests, (de)serialization, the Vite plugin, tsconfig decorator flagsreferences/http-client.mdreferences/http-client-reference.md (full export surface), references/http-client-patterns.md (worked DTO -> adapter -> service recipes, error handling, dirty-save)
Stores, data tables/reports, forms, URL state, composables, router helpers, exceptionsreferences/common.mdreferences/common-reference.md (composable catalog with signatures), references/common-patterns.md (worked stores, useService, useDataTable view, useDtoForm, useUrlState)

Tasks often span layers: a data table view touches common (useDataTable), http-client (the service and DTOs) and sometimes utils (formatting). Read each involved guide; they are short and cross-link where the layers meet.

Related skills

  • vue-build-feature / code-style - the library-neutral Vue architecture and SFC patterns these packages slot into; common is the concrete data/state layer vue-build-feature defers to.
  • flux-ui - the Flux UI component library (separate @flux-ui scope).

Comments

Markdown supported