deno-core

Automate Deno TypeScript project setup, configuration, imports, testing, and permissions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jahanson/cc-plugins --skill deno-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deno-core
Source: https://github.com/jahanson/cc-plugins/tree/main/deno-lsp/skills/deno-core
Command: npx skills add https://github.com/jahanson/cc-plugins --skill deno-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates Deno TypeScript best practices into a single, reusable guide that helps teams configure, import, test, and secure Deno projects from day one.

Core Features & Use Cases

  • Standardized configuration and tooling using deno.json(c) for consistent project setup
  • Clear guidance on imports, typing, and a strict permissions model to reduce risk
  • Security-first patterns and anti-patterns to avoid common pitfalls across Deno development

Quick Start

Initialize a new Deno project using these practices to ensure secure permissions, strict typing, and consistent configuration from day one.

Frequently Asked Questions about deno-core

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

FAQPage Schema
How do I set up a Deno TypeScript project with best practices for configuration and security?

Setting up a Deno TypeScript project requires standardizing configuration through deno.json(c), enforcing strict typing, applying a runtime permission model, and following security-first patterns to reduce risk from day one.

What is the best way to manage imports and permissions in a Deno codebase?

The best way to manage Deno imports and permissions is to enforce strict Deno configurations and runtime permission discipline through a unified, reproducible approach that applies security-first patterns across the codebase.

Can I apply strict Deno configurations to an existing TypeScript project?

Yes, you can apply strict Deno configurations to existing TypeScript projects. This approach automates best-practice workflows and enforces deno.json(c) usage, typing, and anti-pattern avoidance across both new and existing Deno codebases.

What common anti-patterns should I avoid when developing with Deno?

When developing with Deno, avoid bypassing the strict permissions model, skipping standardized deno.json(c) configuration, and neglecting security-first import and typing practices that expose the project to runtime risks.

Do I need a deno.json or deno.jsonc file for consistent project setup?

Yes, using a deno.json or deno.jsonc file is required for consistent project setup. It enforces strict Deno configurations, standardizes tooling, and ensures reproducible development workflows across the codebase.

Why does my Deno project fail when applying runtime permissions?

Deno projects often encounter failures with runtime permissions due to misconfigured strict permission models. Applying reproducible permission discipline and security-first patterns ensures the runtime environment matches the intended configuration.