.claude/skills/flow-setup-agent-code-style-ts-deno/SKILL.md
Adds TypeScript/Deno code style rules to project AGENTS.md. Use when setting up new Deno projects or when user needs to establish code style guidelines.
npx skillsauth add korchasa/ai-skel-ts flow-setup-agent-code-style-ts-denoInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Integrates TypeScript/Deno coding standards into AGENTS.md to maintain consistency.
Add code style rules to AGENTS.md after the "Project tooling Stack" section, before "Architecture".
## Code Style (Deno + TypeScript)
### Dependency Imports
- Use bare specifiers for dependencies defined in deno.json/imports
- Avoid direct jsr:/npm:/https: imports in source code
- Example: `import { assertEquals } from "@std/assert";` instead of `import { assertEquals } from "jsr:@std/assert";`
- **Exception:** Standalone scripts (e.g., in `framework/skills/*/scripts/`) that run without deno.json MUST use `jsr:` specifiers
### Dockerfile Optimization
- Use `deno compile` to create static binaries for production Docker images
- Implement multi-stage builds:
- Compilation stage: `denoland/deno:latest`
- Runtime stage: debian slim image
- Compile with explicit permissions: `--allow-net`, `--allow-read`, `--allow-env`
- Copy only compiled binary and necessary static files to runtime stage
- Set environment variables for proper network binding
tools
Scaffold a complete AI agent application skeleton with LLM integration, tool calling, observability, cost tracking, session management, and content fetching using @korchasa/ai-skel-ts. Use when the user asks to create an AI agent, add LLM integration, scaffold an AI application, or mentions "ai-skel", "agent skeleton", or "AI scaffold". Works with any programming language.
testing
Create structured specification for large features using phased decomposition. Produces documents/spec-{name}.md with dependency-ordered phases, atomic tasks, explicit boundaries, and per-phase status tracking.
documentation
Guidelines for writing comprehensive Product Requirements Documents (PRD)
development
How to write in informational style