leblondx/deno icon
public
Published on 4/8/2025
Deno

xpert in Deno2 Runtime, its APIs, JSR @std packages, Deploy™ and Subhosting, in Fresh the full stack web framework for JavaScript and TypeScript developers, in TypeScript v5.7, and compatible Tailwind.

Rules
Prompts
Models
Context

Prompts

Learn more
deno-init
Initialize a new Deno project
Create a new Deno project with the recommended file structure, including deno.json, 
necessary permissions, and ES module imports. The project should follow best practices 
as of 2025 and include configuration for unit testing.

Follow these strict formatting rules for all files:

1. File Title Header:
   - Must be the first content in the file (no blank lines above it)
   - Format: 
     /** FileName.ts
      * -------------------------------------------------------------------------------------------------------------------------
      * @file ./FileName.ts   @version 1.0.0   @date 2025-04-08
      * @description Brief description of the file.
      * -----------------------------------------------------------------------------------------------------------------------*/
   - Tags must be separated by exactly three spaces

2. Section Headers:
   - Must have exactly three blank lines before each section header
   - Format:
     /** 1. SECTION_NAME
      * -----------------------------------------------------------------------------------------------------------------------*/
   - No additional indentation before the comment block

3. Function Documentation:
   - Must have exactly three blank lines before the function documentation block
   - Format:
     /** 
      * FUNCTION_NAME
      * -------------------------------------------------------------------------------------------------------------------------
      * @function FUNCTION_NAME   @version 1.0.0   @public   @alpha   @date 2025-04-08
      * @param {TYPE} paramName - Description.
      * @return {RETURN_TYPE} - Description.
      * @description Brief description of the function.
      * -----------------------------------------------------------------------------------------------------------------------*/
   - Tags on the same line must be separated by exactly three spaces
   - The @description tag must always be the last one
format
Format the current Deno file according to standardized documentation
I'll format the current Deno file according to our standardized documentation requirements:
1. Add a proper file header at the very top (no blank lines above):
  /** {{fileName}}
    * -------------------------------------------------------------------------------------------------------------------------
    * @file {{filePath}}   @version 1.0.0   @date {{currentDate}}
    * @description Brief description based on file contents.
    * -----------------------------------------------------------------------------------------------------------------------*/

2. Add section headers with exactly three blank lines before each:
  /** 1. SECTION_NAME
    * -----------------------------------------------------------------------------------------------------------------------*/

3. Add function documentation blocks with exactly three blank lines before each:
  /** 
    * FUNCTION_NAME
    * -------------------------------------------------------------------------------------------------------------------------
    * @function FUNCTION_NAME   @version 1.0.0   @public   @alpha   @date {{currentDate}}
    * @param {TYPE} paramName - Description.
    * @return {RETURN_TYPE} - Description.
    * @description Brief description of the function.
    * -----------------------------------------------------------------------------------------------------------------------*/

I'll ensure all tags are separated by exactly three spaces and that @description is always the last tag.
Please format the entire file content and replace it with the properly formatted version.
add-deno-tasks
Add tasks for @public functions to deno.jsonc
I'll scan the codebase for functions with the @public tag in their documentation header and add them as tasks to deno.jsonc.

I'll look for patterns like:
```
/** 
 * FUNCTION_NAME
 * -------------------------------------------------------------------------------------------------------------------------
 * @function FUNCTION_NAME   @version 1.0.0   @public   @alpha   @date 2025-04-08
 * ...
 */
```

For each function with @public tag, I'll create a task in deno.jsonc with:
- Task name matching the function name
- Command to run the file with appropriate permissions

I'll first check if deno.jsonc exists, and create it if needed.

No Data configured

MCP Servers

Learn more

No MCP Servers configured