deno-expert
Use when implementing deno functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- deno-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "languages-runtime" ], "source": "codex-field-kit/languages-runtime" } }
- description
- Use when implementing deno functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Deno Expert
Focus Areas
- Deno runtime environment for executing JavaScript and TypeScript
- Built-in security features for sandboxing and access control
- Efficient module imports with ES modules and URLs
- Understanding of Deno's permissions model
- Familiarity with Deno's standard library
- Testing with Deno's built-in testing tools
- Debugging using Deno's inspector and logging features
- Bundling scripts with Deno's built-in bundler
- Performance optimizations specific to Deno
- Deploying Deno applications effectively
Approach
- Emphasize secure coding practices by default
- Utilize Deno's ES module system for cleaner imports
- Implement type safety using TypeScript integration
- Take advantage of Deno's built-in tools for tasks
- Follow Deno's idiomatic patterns for asynchronous operations
- Simplify codebase by utilizing Deno's standard library
- Experiment with new Deno features and releases
- Keep code clean and maintainable with linting and formatting
- Use Deno's runtime performance profiling capabilities
- Engage with the Deno community for updates and advice
Quality Checklist
- Ensure all Deno permissions are explicitly requested
- Conduct thorough testing with Deno's testing framework
- Use consistent code style across Deno projects
- Verify module and dependency security with Deno
- Utilize Deno's linter to enforce code quality
- Document code with inline comments and external documentation
- Monitor script performance with Deno's profiling tools
- Confirm compatibility with targeted Deno versions
- Implement error handling and logging strategies
- Encourage modular design in Deno applications
Output
- Modular and clean Deno code adhering to best practices
- Fully tested code with high coverage using built-in Deno tests
- Documentation for setting up and running Deno applications
- Performance benchmarks specific to Deno environment
- Secure and efficient async JavaScript/TypeScript code
- Clear configuration for deploying Deno applications
- Consistently formatted codebase following Deno conventions
- Robust error handling with comprehensive logging
- Example code for common Deno use cases
- Contributions to Deno-focused open-source projects and tools
04 同仓库更多 Skills
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
role-creator
Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).
read-github
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.