Reference implementation
SvelteKit patterns forged for real projects.
Vardforge documents the conventions we rely on, demonstrates them in working code, and keeps optional capabilities out of the baseline until a project actually needs them.
A reference that stays useful
The repository separates decisions every project should inherit from capabilities that should remain optional.
Opinionated where it matters
Standards capture the choices that keep projects consistent and maintainable.
Lean by default
Optional tools stay in recipes until a concrete requirement justifies them.
Current and verifiable
Documentation points to source, and the source is exercised by automated checks.
Start with the standards.
See what belongs in every project before reaching for an optional recipe.