Can I use this skill to define step-by-step procedures?

No, rules are meant for conventions and guidelines. Procedural instructions or 'how-to' guides should be implemented as separate Claude Code skills.

What is the difference between a rule and a law in Claude Code?

Laws are high-priority global constraints defined using the tag in CLAUDE.md, while rules are modular, often path-specific conventions stored in the .claude/rules/ directory.

How do I apply a rule only to specific files?

You can use the 'paths:' field in the rule's YAML frontmatter with glob patterns like 'src/api/**/*.ts' to restrict the rule to specific directories or file types.

Why should I keep my Claude rules under 50 lines?

Rules are automatically injected into Claude's context. Keeping them concise (under 50 lines) prevents excessive token consumption and ensures the agent remains fast and focused.

Claude Rule Architect

Name: Claude Rule Architect
Author: wayne930242

bywayne930242

•

Developer Tools

Generates modular, path-scoped rule files to enforce project-specific coding conventions and guidelines within Claude Code.

About

The write-rules skill is a specialized tool for Agentic Context Engineering, allowing developers to automate the creation and management of .claude/rules/ files. By utilizing glob patterns and path-scoping, it ensures that Claude receives the right instructions for the right files—such as API standards for backend code or testing protocols for spec files—without cluttering the global context. This modular approach optimizes token usage while maintaining strict adherence to project-specific architectural patterns and coding styles.

Key Features

Support for both global and directory-specific coding guidelines
Seamless integration with the .claude/rules/ architecture
Modular convention management to optimize context token usage
Automated validation for rule length and imperative syntax
4 GitHub stars
Path-scoped rule generation using advanced glob patterns

Use Cases

Enforcing domain-specific design patterns within a microservices repository
Maintaining consistent testing and documentation standards across a large codebase
Applying legacy code constraints only to specific legacy directories

About

Key Features

Support for both global and directory-specific coding guidelines
Seamless integration with the .claude/rules/ architecture
Modular convention management to optimize context token usage
Automated validation for rule length and imperative syntax
4 GitHub stars
Path-scoped rule generation using advanced glob patterns

Use Cases

Enforcing domain-specific design patterns within a microservices repository
Maintaining consistent testing and documentation standards across a large codebase
Applying legacy code constraints only to specific legacy directories