deno

Deno-specific conventions and patterns.

⭐41stars🔀4forks📁View on GitHub🕐Updated Dec 30, 2025⬇️1downloads

When & Why to Use This Skill

This Claude skill provides a comprehensive set of Deno-specific conventions and patterns designed to optimize TypeScript development within the Deno runtime. By enforcing idiomatic practices—such as explicit file extensions, JSR/standard library prioritization, and the use of native Deno tooling—it ensures that generated code is performant, secure, and compliant with modern Deno standards. It effectively bridges the gap for developers moving from Node.js by eliminating dependencies on node_modules and external linters in favor of Deno's built-in ecosystem.

Use Cases

  • Idiomatic Code Generation: Automatically apply Deno-specific import rules, including explicit '.ts' extensions and the prioritization of JSR and @std over npm packages.
  • Project Configuration & Tooling: Streamline project setup using deno.json for task management, linting, and formatting, replacing the need for Prettier or ESLint.
  • Native Testing Suites: Develop robust unit tests using the native Deno.test API and @std/assert library, following the Arrange-Act-Assert (AAA) pattern.
  • Security & Permission Documentation: Ensure runtime safety by correctly documenting required permissions (like --allow-read) within JSDoc, adhering to Deno's secure-by-default philosophy.
namedeno
descriptionDeno-specific conventions and patterns.

Conventions

  • Imports: Explicit extensions (.ts), JSR > @std > npm
  • Config: deno.json for imports, tasks, lint, fmt
  • Tools: deno fmt/lint/check/test (not Prettier/ESLint/Vitest)
  • No node_modules

Testing

Deno.test("behavior description", async (t) => {
  await t.step("specific case", () => {
    // AAA pattern, @std/assert
  });
});

Permissions

Document in JSDoc: @requires --allow-read