GitHub ↗

SVELTEKIT FOUNDATIONS · AGENT-READY

Built for you.
And your agent.

Give your next idea a solid starting point. SvelteKit foundations, composable modules, and project context your coding agent can work with.

Start building Explore the agent workflow

Open source · MIT · Yours to shape

your-app / workspace
A solid starting point
AuthenticationBetter Auth
Your dataDrizzle + PostgreSQL
SvelteKit + your codeDashboard starter example
AGENTS.mdConventions. Reuse. Context.
+ optional modules

FAMILIAR TOOLS. CONNECTED FOUNDATIONS.

SvelteSvelteKitSkeletonTailwindBetter Auth Dashboard starterDrizzle Dashboard starter
2focused starters
13optional modules
JSONagent-readable UI copy
MITsource you own

01 / CONTEXT BEFORE CODE

Give your agent
a project it can read.

The architecture, components and conventions are already there. SVForge makes them discoverable, so you can ask your agent to build on the project instead of explaining the foundations every time.

Context shipped with your project

One place for project conventions.

AGENTS.md describes the implementation rules, component reuse order, design system and i18n conventions. Point your agent here before it starts coding.

Less re-explaining.
More building on what exists.

Ask your agent to inspect the context, reuse the shared components, and add modules when they fit your feature.

  1. 01 Read the project context
  2. 02 Reuse components and modules
  3. 03 Build the product-specific parts
  4. 04 Run checks, tests and the build

Instructions guide the agent. svforge check checks the project rails, alongside Svelte checks and tests.

PARAGLIDE / COPY YOUR AGENT CAN EDIT

Your UI copy.
In readable JSON.

Paraglide keeps static interface text in message catalogs, separate from component markup. Your agent can read the keys, adjust wording and translate messages in one place. Changes stay easy to review in a diff.

French and English are the starter defaults, not a limitation. Add the locales your product needs and keep the same keys across catalogs. Editorial and business content stay in their own storage.

A STARTING PROMPT FOR YOUR AGENT

Bring the idea.
Let the context do its part.

Read AGENTS.md, llms.txt and .svforge.json first. Inspect the component and module catalogs. Plan this feature using the existing foundations, explain what needs custom code, then implement it and run the project checks.

02 / CHOOSE YOUR FOUNDATION

Two starters.
Room for your own ideas.

Start light or start with auth and data. Both give you a normal SvelteKit project you can shape.

template:base

The clean slate.
With the groundwork done.

For sites and applications that need a coherent foundation before adding product-specific capabilities.

  • Svelte 5 + TypeScript
  • Skeleton UI, Tailwind and dark mode
  • Paraglide i18n with editable JSON catalogs
  • SEO helpers, Vitest and agent context
Start with Base
template:dashboard

An application starter.
Auth and data included.

The Dashboard starter includes accounts, an authenticated workspace and PostgreSQL. A foundation for your application, with an admin interface already included.

  • Everything in Base
  • Better Auth + Drizzle + PostgreSQL
  • Admin dashboard and user management
  • Zod patterns and database setup scripts
Start with Dashboard

03 / ASSEMBLE WHAT YOU NEED

Your stack.
One useful piece at a time.

Modules add reusable capabilities to your application. Their implementation lives in your source, ready for you and your agent to extend.

npx sv add @svforge/uploads

Add a capability when your product needs it.

Explore module docs →

04 / LIGHT THE FORGE

Start with a foundation.
Build something yours.

Pick your starter, apply it with the Svelte CLI, then give your agent the project context and your first feature.

Your code stays in your app. No opaque SVForge application runtime after scaffolding.

your terminal · Bash 
npx sv create my-app
cd my-app
npx sv add svforge=template:base+testing:vitest
Then use your project's dev script to start building.

A FEW PRACTICAL DETAILS

Before you
start building.

Is SVForge another framework?

SVForge is a collection of community addons for the Svelte CLI. SvelteKit remains your application framework. The generated structure, components and module implementations become part of your project.

Will my coding agent read the context automatically?

That depends on your tool. AGENTS.md is the canonical instruction file; SVForge does not scaffold separate instructions for each assistant. Ask your agent to read it and the project context explicitly when needed.

Can I change the theme, fonts and locales?

Yes. The Skeleton theme, font imports and Paraglide catalogs are editable project files. French and English are the initial locales; you can add others. The defaults are a starting point.

Do I have to use every module?

No. Choose Base or Dashboard, then add the capabilities your application needs. Check each module's prerequisites and configuration in its documentation.

How do checks and upgrades work?

svforge check validates project and design-system rules. Run it alongside Svelte checks, tests and builds. Template and module upgrades provide a reviewable plan and diff; locally modified files are not silently overwritten.

HUMAN IDEAS. AGENT-READY FOUNDATIONS.

You bring the craft.
We bring the starting point.

Start building ↗Explore on GitHub →