flowai-setup-agent-code-style-ts-deno

Insert TypeScript/Deno coding standards into AGENTS.md.

1|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/korchasa/foxcode --skill flowai-setup-agent-code-style-ts-deno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flowai-setup-agent-code-style-ts-deno
Source: https://github.com/korchasa/foxcode/tree/main/.claude/skills/flowai-setup-agent-code-style-ts-deno
Command: npx skills add https://github.com/korchasa/foxcode --skill flowai-setup-agent-code-style-ts-deno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides standardized TypeScript/Deno code style guidelines by injecting rules into AGENTS.md to ensure consistent project-wide conventions.

Core Features & Use Cases

  • Enforces TypeScript/Deno code style rules in AGENTS.md to maintain consistency.
  • Defines dependency import rules using bare specifiers from deno.json/imports and clarifies exceptions for standalone scripts in scripts/.
  • Proposes Dockerfile optimization practices, such as multi-stage builds and explicit permissions, to streamline production images.
  • Use Case: When starting a new Deno project or updating an existing repository to adopt a cohesive code style.

Quick Start

Insert the Code Style Rules into AGENTS.md after the "Project tooling Stack" section and before "Architecture".

Frequently Asked Questions about flowai-setup-agent-code-style-ts-deno

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

FAQPage Schema
How do I enforce TypeScript and Deno code style in AGENTS.md?

You can enforce TypeScript and Deno code style in AGENTS.md by inserting standardized coding rules into the file. This ensures consistent project-wide conventions by defining dependency import rules and Dockerfile optimization practices.

What are the Deno dependency import rules for bare specifiers?

Deno dependency import rules require using bare specifiers from deno.json/imports. This approach maintains consistency across the project, with explicit exceptions allowed for standalone scripts located in the scripts/ directory.

Do I need an existing AGENTS.md file to set up Deno project guidelines?

Yes, you need an existing AGENTS.md file located in the project root. The setup targets the "Project tooling Stack" and "Architecture" sections for insertion, ensuring added rules do not rely on non-existent references.

Where do I insert code style rules in AGENTS.md?

You insert code style rules in AGENTS.md after the "Project tooling Stack" section and before the "Architecture" section. This placement integrates TypeScript/Deno standards logically within the project guidelines.

What Dockerfile practices should I follow for Deno production images?

For Deno production images, you should follow Dockerfile optimization practices such as using multi-stage builds and applying explicit permissions. These practices streamline production images and enhance security.

When should I update AGENTS.md with TypeScript Deno coding standards?

You should update AGENTS.md with TypeScript Deno coding standards when starting a new Deno project or updating an existing repository. This ensures the codebase adopts a cohesive code style and maintains tooling integration.