// 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.
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.
| name | eser-rules-manager |
| description | 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. |
Two functions: (1) Discover and invoke relevant skills before ANY response, (2) Manage development rules across skills.
Before ANY response (including clarifying questions):
Even 1% probability requires checking skills first. This is not optional.
.claude/skills/<name>/references/rules.mdnpx -y claude-skills-cli validate .claude/skills/<name>| Skill | Triggers |
|---|---|
javascript-practices | JS/TS code, modules, types |
go-practices | Go code, hexagonal architecture |
workflow-practices | Task execution, git commits |
requirement-clarification | Unclear scope, multiple approaches |
security-practices | Auth, secrets, validation |
ci-cd-practices | GitHub Actions, Kubernetes, deployments |