Monorepo scripts, package boilerplate, conventions. Use when: "how do I run", "bun run", "build this", "run tests", "typecheck", "create a new package", linting, scaffolding packages.
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
The monorepo uses consistent script naming conventions.
| Command | Purpose | When to use |
|---|---|---|
bun format | Fix formatting (biome) | Development |
bun format:check | Check formatting | CI |
bun lint | Fix lint issues (biome) | Development |
bun lint:check | Check lint issues | CI |
bun typecheck | Type checking (tsc, svelte-check, astro check) | Both |
bun test | Run unit tests (*.test.ts only) | Both |
bun bench | Run benchmarks (*.bench.ts; reports, no assertions) | Manual |
:check suffix = check only (for CI, no modifications)typecheck alone = type checking (separate concern, cannot auto-fix)test runs only *.test.ts; bench runs only *.bench.ts. A file is
one or the other : never both. Benchmarks print reports; tests assert.Start apps from the repo root, not by cd-ing into the app. Root
bun dev:<app> runs every process the app needs; for apps that talk to the
hosted API (epicenter, vocab, and the
api dashboard), it also starts @epicenter/api on localhost:8787 via
bun run --filter. Root bun dev:<app>:ui runs the app's frontend
alone when that split exists; for desktop apps, it maps to the package's
web dev or dev:ui. bun dev:api runs just the backend.
Inside a single package, the conventions are:
Non-Tauri apps use a single dev script that runs the underlying tool
directly (vite dev, astro dev, wrangler dev). Desktop apps keep that
dev (and dev:ui) as the web build and name the desktop shell
dev:desktop; the Epicenter app has no web build, so its dev aliases
dev:desktop. The suffix convention applies primarily to database
commands:
| Script | Meaning |
|---|---|
dev | The default local workflow. May still require Infisical login for app secrets (e.g. API keys), but only ever talks to local infrastructure at runtime. |
dev:ui | Desktop apps: the Vite dev server alone, no desktop shell. |
dev:desktop | Desktop apps: launches the native desktop app (tauri dev with the app's tauri.dev.conf.json). The Epicenter app's dev aliases this. |
db:*:local | Runs against local Postgres. Works without Infisical login. |
db:*:remote | Wraps with infisical run --env=prod. Production data; treat as admin. |
There is no dev:remote. Production data is reached only through :remote db
scripts and deploy, never through a development server.
Run type checking to verify:
bun typecheckThis runs bun run --filter '*' typecheck which executes the typecheck script in each package (e.g., tsc --noEmit, svelte-check).
When creating a new package in packages/, follow this exact structure.
package.json{
"name": "@epicenter/<package-name>",
"version": "0.0.1",
"exports": {
".": "./src/index.ts"
},
"license": "AGPL-3.0-or-later",
"scripts": {
"typecheck": "tsc --noEmit"
},
"dependencies": {},
"devDependencies": {
"@types/bun": "catalog:",
"typescript": "catalog:"
}
}Key conventions:
exports only, no main/types: modern resolvers ignore main/types when exports is present. The entry point is ./src/index.ts; there is no build step, consumers import the source directly."workspace:*" for internal deps (e.g., "@epicenter/definition": "workspace:*")."catalog:" for shared versions managed in the root package.json catalogs.peerDependencies for packages consumers must also install (e.g., svelte in @epicenter/account, optional for a consumer without Svelte).license: AGPL-3.0-or-later. Before adding an MIT package, read "If MIT returns" in docs/licensing/licensing-strategy.md.tsconfig.jsonA leaf config picks a tier and adds nothing that repeats a base. For a Bun library:
{
"extends": "../../tsconfig.base.json",
"compilerOptions": {
"types": ["bun"],
"noUnusedLocals": true,
"noUnusedParameters": true
}
}A Svelte or browser library extends ../../tsconfig.dom.json instead. For all seven leaf tiers, the never-redeclare list, and the module strategy, see the tsconfig skill.
After creating the package, run bun install from the repo root to register it in the workspace.
EpicenterHQ/epicenter
04f87cb
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.