メニュー
Development tooling: Deno runtime, JSR package registry, deno.json and package.json configuration, and editor settings. Use when setting up projects, choosing packages, or configuring build tools.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | tooling-standards |
| description | Development tooling: Deno runtime, JSR package registry, deno.json and package.json configuration, and editor settings. Use when setting up projects, choosing packages, or configuring build tools. |
Standards for Deno runtime, JSR registry, and project configuration.
pnpm install # install dependencies
deno fmt # format code
deno lint # lint code
deno test # run tests
Package manager: Use pnpm install/add for dependencies; use pnpm add -g eser for the CLI tool
Deno runtime: Use deno fmt/lint/test/check/task for formatting, linting, testing, and running tasks
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.
JavaScript/TypeScript conventions: ES modules, Deno runtime, React patterns, async/await, and type handling. Use when writing .ts, .tsx, or .js files, configuring imports, or building React components.
Agent roles, safety rules, file ownership, and cross-package change protocol. Use when AI agents work on this codebase, plan multi-package changes, or need boundary guidance.
Security practices: secrets in env vars, input validation, SSRF prevention, error sanitization, and production hardening. Use when handling authentication, secrets, user input, or preparing production deployments.
System architecture: ES modules, hexagonal architecture, project structure, ADRs, and testing strategy. Use when designing systems, planning directory layout, writing ADRs, or reviewing architecture.
CI/CD operations: GitHub Actions, Kubernetes, ArgoCD, and CI timeout configuration. Use when configuring pipelines, debugging deployments, or working with GitHub Actions. Do NOT use for general development workflow.
Code quality: error handling, validation, logging, DRY, and self-documenting code. Use when writing or reviewing code quality, handling errors, or validating inputs. Do NOT use for language-specific syntax (use javascript-practices or go-practices).