go-practices
Go conventions for hexagonal architecture, project structure, error handling, testing, and observability. Use when writing Go services.
Explorez les skills IA publiés de eser et consultez leurs instructions source.
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.
Code design patterns: pure functions, immutability, composition, and async. Use when designing code or functions.
Manages practice rules. Use when user states a preference or approach, or asks to add/modify rules for coding, architecture, tooling, or best practices.
Workflow rules for task execution, respecting user code, and git commits. Use when planning or executing development tasks.
CI/CD and operations practices including GitHub Actions, Kubernetes, and operational tooling. Use when working with deployment and infrastructure.
JS/TS conventions for syntax, modules, and types. Use when writing or reviewing JavaScript/TypeScript code.
Code quality practices: error handling, validation, logging, and DRY. Use when writing or reviewing code.
Development tooling standards including Deno runtime, JSR package registry, and configuration files. Use when setting up projects, managing dependencies, or configuring build tools.
System architecture: modules, project structure, ADRs, and testing. Use when designing or reviewing systems.
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.
Go conventions for hexagonal architecture, project structure, error handling, testing, and observability. Use when writing Go services.
JS/TS conventions for syntax, modules, and types. Use when writing or reviewing JavaScript/TypeScript code.
Guidelines for asking clarifying questions when requirements are ambiguous. Use when scope is unclear, multiple approaches exist, or critical details are missing.
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.
System architecture: modules, project structure, ADRs, and testing. Use when designing or reviewing systems.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.