メニュー
Development tooling standards including Deno runtime, JSR package registry, and configuration files. Use when setting up projects, managing dependencies, or configuring build tools.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | tooling-standards |
| description | Development tooling standards including Deno runtime, JSR package registry, and configuration files. Use when setting up projects, managing dependencies, or configuring build tools. |
Standards for Deno runtime, JSR registry, and project configuration.
deno install # install dependencies
deno fmt # format code
deno lint # lint code
deno test # run tests
Deno: Use deno install/fmt/lint/test instead of npm commands
Config files:
package.json for dependencies and scriptstsconfig.json for TypeScriptdeno.json only for fmt/lint settingsRegistry: Prefer jsr.io over npm. Use npm:@jsr/ prefix in package.json
Packages: JSR when available, npm when no JSR alternative exists
See rules.md for complete guidelines with examples.
JS/TS conventions for syntax, modules, and types. Use when writing or reviewing JavaScript/TypeScript code.
System architecture: modules, project structure, ADRs, and testing. Use when designing or reviewing systems.
CI/CD and operations practices including GitHub Actions, Kubernetes, and operational tooling. Use when working with deployment and infrastructure.
Code quality practices: error handling, validation, logging, and DRY. Use when writing or reviewing code.
Manages practice rules. Use when user states a preference or approach, or asks to add/modify rules for coding, architecture, tooling, or best practices.
Go conventions for hexagonal architecture, project structure, error handling, testing, and observability. Use when writing Go services.