// Manages practice rules. Use when user states a preference or approach, or asks to add/modify rules for coding, architecture, tooling, or best practices.
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.
Go conventions for hexagonal architecture, project structure, error handling, testing, and observability. Use when writing Go services.
| name | eser-rules-manager |
| description | Manages practice rules. Use when user states a preference or approach, or asks to add/modify rules for coding, architecture, tooling, or best practices. |
Manages development rules across skills. Before working, apply all rules in
.claude/skills/*/SKILL.md.
.claude/skills/<name>/references/rules.md.claude/skills/<name>/SKILL.md key principles if needednpx -y claude-skills-cli validate .claude/skills/<name>name (kebab-case), description (<1024 chars)architecture-guidelines, design-principles, coding-practices,
javascript-practices, tooling-standards, go-practices,
security-practices, workflow-practices, ci-cd-practices
See skill-format.md for complete skill format requirements.