eser

JavaScript/TypeScript conventions: ES modules, Deno runtime, React patterns, async/await, and type handling. Use when writing .ts, .tsx, or .js files, configuring imports, or building React components.

Development tooling: Deno runtime, JSR package registry, deno.json and package.json configuration, and editor settings. Use when setting up projects, choosing packages, or configuring build tools.

Agent roles, safety rules, file ownership, and cross-package change protocol. Use when AI agents work on this codebase, plan multi-package changes, or need boundary guidance.

Security practices: secrets in env vars, input validation, SSRF prevention, error sanitization, and production hardening. Use when handling authentication, secrets, user input, or preparing production deployments.

System architecture: ES modules, hexagonal architecture, project structure, ADRs, and testing strategy. Use when designing systems, planning directory layout, writing ADRs, or reviewing architecture.

CI/CD operations: GitHub Actions, Kubernetes, ArgoCD, and CI timeout configuration. Use when configuring pipelines, debugging deployments, or working with GitHub Actions. Do NOT use for general development workflow.

Code quality: error handling, validation, logging, DRY, and self-documenting code. Use when writing or reviewing code quality, handling errors, or validating inputs. Do NOT use for language-specific syntax (use javascript-practices or go-practices).

README and documentation conventions: import patterns in examples, emoji preservation, and descriptive text rules. Use when writing or editing README files, package documentation, or code examples in docs.

JS/TS conventions for syntax, modules, and types. Use when writing or reviewing JavaScript/TypeScript code.

Code design patterns: pure functions, immutability, composition, and async. Use when designing code or functions.

System architecture: modules, project structure, ADRs, and testing. Use when designing or reviewing systems.

CI/CD and operations practices including GitHub Actions, Kubernetes, and operational tooling. Use when working with deployment and infrastructure.

Code quality practices: error handling, validation, logging, and DRY. Use when writing or reviewing code.

Manages practice rules. Use when user states a preference or approach, or asks to add/modify rules for coding, architecture, tooling, or best practices.

Go conventions for hexagonal architecture, project structure, error handling, testing, and observability. Use when writing Go services.

Security practices including secrets management, input validation, SSRF prevention, and production hardening. Use for security-sensitive code.

JS/TS conventions for syntax, modules, and types. Use when writing or reviewing JavaScript/TypeScript code.

Go conventions for hexagonal architecture, project structure, error handling, testing, and observability. Use when writing Go services.

Code quality practices: error handling, validation, logging, and DRY. Use when writing or reviewing code.

Workflow rules for task execution, respecting user code, and git commits. Use when planning or executing development tasks.

System architecture: modules, project structure, ADRs, and testing. Use when designing or reviewing systems.

CI/CD and operations practices including GitHub Actions, Kubernetes, and operational tooling. Use when working with deployment and infrastructure.

Skill discovery and rule management. Use when starting any conversation to identify applicable skills, and when user states preferences or asks to add/modify rules.

Guidelines for asking clarifying questions when requirements are ambiguous. Use when scope is unclear, multiple approaches exist, or critical details are missing.

JS/TS conventions for syntax, modules, and types. Use when writing or reviewing JavaScript/TypeScript code.