deno

Standardize Deno TypeScript projects with deno.json, explicit imports, and Deno.test patterns.

43|4|Updated Dec 19, 2018

Search Tags:#typescript #testing #permissions #patterns #conventions #deno

Ready to run

npx skills add https://github.com/lambdalisue/dotfiles --skill deno

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deno
Source: https://github.com/lambdalisue/dotfiles/tree/main/home/claude/skills/deno
Command: npx skills add https://github.com/lambdalisue/dotfiles --skill deno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies best practices for using Deno in projects, reducing boilerplate and onboarding time.

Core Features & Use Cases

Deno-specific conventions: Explicit extensions (.ts), deno.json for imports, tasks, lint, fmt; no node_modules
Testing: Deno.test patterns and preferred testing style
Permissions: Document required permissions via JSDoc: @requires --allow-read
Use Case: Spin up a clean Deno project following these conventions to accelerate development

Quick Start

Start a new Deno project and apply the conventions by creating deno.json, and running deno fmt, deno lint, and deno test.

Frequently Asked Questions about deno

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up a Deno project with TypeScript conventions?▼

Set up a Deno project by creating a `deno.json` file for imports and tasks, using explicit `.ts` file extensions, and running `deno fmt` and `deno lint` to enforce conventions. This standardizes your TypeScript codebase and eliminates boilerplate across Deno imports and tooling.

What's the best way to test code in Deno?▼

Use Deno.test patterns for testing, which integrate directly with Deno's built-in test runner. This approach follows Deno conventions and works seamlessly with permission documentation via JSDoc metadata like `@requires --allow-read`.

How do I document and enforce Deno permissions in my project?▼

Document required permissions using JSDoc metadata annotations such as `@requires --allow-read` in your code. This makes permission requirements explicit and integrates with CI-ready workflows for automated permission checking.

Can I use Deno conventions without node_modules?▼

Yes, Deno conventions explicitly exclude `node_modules` and rely on remote imports defined in `deno.json`. This eliminates dependency management overhead and keeps your project clean and portable.

Why should I use deno fmt and deno lint in my workflow?▼

Deno fmt and deno lint enforce consistent code style and catch errors automatically as part of Deno's standardized tooling. This reduces manual code review overhead and ensures all contributors follow the same patterns.

Does Deno support CI-ready testing and linting workflows?▼

Yes, Deno integrates `deno test`, `deno lint`, and `deno fmt` with permission documentation via JSDoc, creating CI-ready workflows that validate code style, correctness, and security constraints automatically.