Process

S oftware E ngineering

Build, test, package — the development pipeline

Most development teams accumulate inconsistent build and test practices over time — one developer runs tests with different flags, another skips type checking entirely, and the CI pipeline becomes the only place where the "real" build happens. Local builds diverge from production, and manual setup instructions rot in wikis nobody reads.

SBX wraps all platform tooling into governed CLI commands that produce reproducible builds and traceable tests across Go and SvelteKit. The same command that builds locally is the same command that builds in CI. Tests trace back to user stories. Type checking is non-optional. The development pipeline is deterministic by design, not by accident.

// BUILD_PIPELINE

Reproducible Builds Across Platforms

The build system auto-detects the target platform — Go or SvelteKit — and applies the correct compilation flags, runs svelte-check or go vet as pre-build gates, and ensures the build exits zero before anything ships. Builds are deterministic: same source input produces the same output, every time, on every machine. No environment-specific surprises, no "works on my machine" — just a single command that either passes or fails with clear diagnostics.

// TEST_SUITE

Governed Test Execution

Tests are not optional afterthoughts bolted on before a release — they are governance gates woven into every step of the pipeline. Unit tests run via sbx test unit, end-to-end tests via sbx test e2e, both wrapped with the correct platform flags and traceable to the user stories that justified writing them. No test coverage, no merge. Every test failure traces back to a specific scenario, and every scenario traces forward to the code that implements it.

// MULTI_PLATFORM

One Workflow, Multiple Platforms

Go backends and SvelteKit frontends share the same CLI commands, the same SDLC pipeline, and the same governance rules. sbx build auto-detects the platform from the directory structure. sbx run manages dev servers with port allocation from a central registry. sbx check runs the platform-appropriate type checker. The developer never needs to remember which flags belong to which tool — the CLI handles it.

// CLI_REFERENCE

Engineering Commands

The entire build, test, and run lifecycle is CLI-driven — six commands that cover compilation, dev servers, testing, and type checking across all platforms in the monorepo. Select a command below to see its usage and output.