tooling-standards

eser's avatarfrom eser

Development tooling standards including Deno runtime, JSR package registry, and configuration files. Use when setting up projects, managing dependencies, or configuring build tools.

⭐83stars🔀4forks📁View on GitHub🕐Updated Jan 1, 2026

When & Why to Use This Skill

This Claude skill establishes and enforces modern development tooling standards centered on the Deno runtime and JSR package registry. It optimizes the developer experience by standardizing project initialization, dependency management, and configuration file structures (deno.json, package.json, tsconfig.json), ensuring a consistent and high-quality toolchain for TypeScript and JavaScript projects.

Use Cases

  • Project Initialization: Setting up new Deno-based projects with standardized configuration files and directory structures to ensure environment consistency.
  • Dependency Management: Migrating projects to the JSR registry and managing hybrid dependencies using the npm:@jsr/ prefix for improved performance and security.
  • Workflow Automation: Implementing unified commands for code formatting, linting, and testing using Deno's built-in toolchain (deno fmt, deno lint, deno test) to replace fragmented npm scripts.
  • Configuration Optimization: Managing complex TypeScript and runtime settings across multiple configuration files to maintain compatibility and best practices.
nametooling-standards
descriptionDevelopment tooling standards including Deno runtime, JSR package registry, and configuration files. Use when setting up projects, managing dependencies, or configuring build tools.

Tooling Standards

Standards for Deno runtime, JSR registry, and project configuration.

Quick Start

deno install    # install dependencies
deno fmt        # format code
deno lint       # lint code
deno test       # run tests

Key Principles

Deno: Use deno install/fmt/lint/test instead of npm commands

Config files:

  • package.json for dependencies and scripts
  • tsconfig.json for TypeScript
  • deno.json only for fmt/lint settings

Registry: Prefer jsr.io over npm. Use npm:@jsr/ prefix in package.json

Packages: JSR when available, npm when no JSR alternative exists

References

See rules.md for complete guidelines with examples.