Skip to content
Apps with loveApps with loveAWL Claude Code

Set up a SvelteKit app with @awl packages

Owner: Maximilian LembergReviewed: 19 September 2026

Starting point: A new or existing SvelteKit app and a GitLab personal access token for the @awl registry. Goal: Login, session, i18n, metrics and HTTP client run on the @awl/* packages, as far as the project needs them.

  1. Wire the app with sveltekit-app-setup. The skill first reads package.json, src/hooks.server.ts and src/app.d.ts, then builds up layer by layer: registry, auth, session, i18n, observability, HTTP client, Tailwind. Layers the project does not need are left out.

    Tell Claude
    Set up sveltekit app: OIDC login, session and i18n with the @awl packages.

  2. Look up single packages with awl-npm-packages. The catalogue shows which package solves what, with a cheat sheet of signatures and options per package.

    Tell Claude
    Which awl package fits a form with validation?

  3. Add a smoke test: check toBeHydrated and toBeAccessible on /. The Playwright configuration itself comes from testing-web.

    Tell Claude
    Write a sveltekit e2e smoke test with Playwright.

When something goes wrong

Section titled “When something goes wrong”
  • pnpm install cannot find an @awl/* package → registry setup in awl-npm-packages
  • A Svelte package from @awl only fails at runtime → the optimizeDeps.exclude entry in vite.config.ts is missing, see awl-npm-packages
  • The Docker build cannot find the private packages → building-docker-images