Deno Development Skills
Modern Deno development knowledge for AI coding assistants. These skills teach your AI assistant how to build Deno applications using current best practices.
Skills
| Skill | Description |
|---|
| deno-guidance | Core Deno best practices, JSR packages, CLI commands |
| deno-deploy | Deployment workflows for Deno Deploy |
| deno-frontend | Fresh framework, Preact components, Tailwind CSS |
| deno-sandbox | Safe code execution with @deno/sandbox |
| deno-project-templates | Project scaffolding templates |
| deno-expert | Code review and debugging principles |
Key Principles
These skills enforce modern Deno practices:
- JSR over deno.land/x - Always use
jsr: imports; deno.land/x is deprecated
- npm: as fallback - Use
npm: packages when no JSR alternative exists
- Built-in tools - Encourage
deno fmt, deno lint, deno test, deno doc
- Fresh patterns - Island architecture with small, serializable-prop islands
Versioning
This project uses Semantic Versioning. When contributing changes:
When to Bump Versions
| Change Type | Version Bump | Example |
|---|
| Breaking changes | MAJOR (1.0 → 2.0) | Fundamentally altering how a skill works |
| New features, significant updates | MINOR (1.1 → 1.2) | Adding new guidance, updating documentation |
| Typo fixes, small clarifications | PATCH (1.1.0 → 1.1.1) | Fixing formatting, correcting typos |
Files to Update
When making changes, update the appropriate version numbers:
- Skill-specific changes - Update the skill's
version in its SKILL.md frontmatter
- Plugin releases - Update
version in both:
.claude-plugin/plugin.json.claude-plugin/marketplace.json
For Contributors
- Include version bumps in your PRs when changing skill content
- Use conventional commits (e.g.,
feat:, fix:, docs:) to indicate change type
- When in doubt, bump the MINOR version for content changes
Installation
These skills follow the Agent Skills Specification.
Claude Code
Option 1: Install as a plugin
# Step 1: Add the marketplace
/plugin marketplace add denoland/skills
# Step 2: Install the plugin
/plugin install deno-skills@denoland-skills
Option 2: Manual installation
Copy the skills you want to use:
# Clone the repository
git clone https://github.com/denoland/skills.git /tmp/deno-skills
# Copy individual skills to your personal skills directory
cp -r /tmp/deno-skills/skills/deno-guidance ~/.claude/skills/
cp -r /tmp/deno-skills/skills/deno-deploy ~/.claude/skills/
# ... or copy all skills
cp -r /tmp/deno-skills/skills/* ~/.claude/skills/
# Or for project-specific installation
cp -r /tmp/deno-skills/skills/* .claude/skills/
Cursor
Note: Agent Skills in Cursor are currently only available in v2.4+.
# Clone the repository
git clone https://github.com/denoland/skills.git /tmp/deno-skills
# Copy skills to your Cursor skills directory
cp -r /tmp/deno-skills/skills/* ~/.cursor/skills/
# Or for project-specific installation
cp -r /tmp/deno-skills/skills/* .cursor/skills/
VS Code with GitHub Copilot
Note: Agent Skills require the chat.useAgentSkills setting to be enabled (currently in preview).
# Clone the repository
git clone https://github.com/denoland/skills.git /tmp/deno-skills
# Copy skills to your project's skills directory
mkdir -p .github/skills
cp -r /tmp/deno-skills/skills/* .github/skills/
# Or for personal installation
cp -r /tmp/deno-skills/skills/* ~/.copilot/skills/
To enable Agent Skills in VS Code:
- Open VS Code Settings (Cmd/Ctrl + ,)
- Search for
chat.useAgentSkills
- Enable the setting
Other Platforms
For other AI coding assistants that support the Agent Skills specification, copy the skill directories from skills/ to your platform's skills directory. Check your platform's documentation for the correct location.
Usage
Once installed, your AI assistant will automatically apply Deno best practices when:
- Working in projects with a
deno.json file
- Creating new Deno applications
- Adding dependencies
- Deploying to Deno Deploy
- Building Fresh web applications
- Running user code in sandboxes
Documentation Resources
License
MIT License - see LICENSE
denoland