tooling-standards
Development tooling standards including Deno runtime, JSR package registry, and configuration files. Use when setting up projects, managing dependencies, or configuring build tools.
tooling
standards
SKILL.mddata/tooling-standards
GitHubTooling Standards
Tools, configuration files, dependencies and repository conventions shared by
every repository on the eserstack toolchain. Repository-specific facts (paths,
generators, command list) are in AGENTS.md.
Always
- pnpm installs; Deno formats, lints, checks and tests; no npm, npx or
deno install package.jsonis the source of truth; per-packagedeno.jsonis generated, so never edit it; run the generator instead; extra JSR fields go indeno.extra.json- Internal dependencies use
workspace:*, external ones plain semver ornpm:@jsr/...; nevercatalog: - Prefer JSR packages; npm only when no JSR package exists
- Ask before adding any dependency, with purpose, license, advisories, health and exit cost written down
- Project commands live in
.eser/manifest.ymland run through theeserCLI - Files are kebab-case, Go files snake_case; every source file starts with the license header, copied from an existing file
- Do not swap or re-wire existing tools without the owner's approval
References
| File | Read when |
|---|---|
| deno-and-packages.md | Editing package config, choosing or adding a dependency |
| scripts-and-editor.md | Adding a project command, changing editor settings |
| repo-conventions.md | Naming files, license headers, creating a package |