What problem does it solve?
Creating Claude Code rules that follow official conventions is error-prone: users often create rules with invalid globs, duplicate content from CLAUDE.md, or use the wrong rule type (unconditional vs scoped), leading to rules that never load or conflict with existing instructions. This Skill eliminates those mistakes by providing a step-by-step guided workflow aligned with official Claude Code documentation.
Core Features & Use Cases
- Rule Type Decision Tree: Helps users correctly identify whether content should be a rule, CLAUDE.md entry, skill, or hook, avoiding misclassification.
- Glob Pattern Guidance: Provides canonical glob patterns and architectural stereotype patterns (e.g., Command.cs, IService.cs) to create accurate path-scoped rules.
- Templates & Examples: Includes pre-built templates for unconditional and scoped rules, plus real-world examples for common use cases like security rules, CQRS conventions, and feature-specific guidelines.
- Validation Steps: Guides users to validate globs against real project files and check for common anti-patterns like overly long rules or conflicting instructions.
- Use Case: A .NET development team can use this Skill to create a scoped rule that enforces CQRS command conventions for all *Command.cs files across the project, without affecting other file types.
Quick Start
Use the create-rule skill to generate a new scoped rule that enforces CQRS command validation standards for all files matching the **/*Command.cs glob pattern.