rules-creator

Define project standards using CLAUDE.md guidelines and .claude/rules constraints.

6|1|Updated Dec 8, 2009
One-click install
npx skills add https://github.com/jey3dayo/dotfiles --skill rules-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rules-creator
Source: https://github.com/jey3dayo/dotfiles/tree/main/agents/skills-internal/rules-creator
Command: npx skills add https://github.com/jey3dayo/dotfiles --skill rules-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Claude Code rules provide a practical guide to define and enforce consistent project standards by combining guideline-level content with machine-enforceable rules.

Core Features & Use Cases

  • Two-layer rule structure: CLAUDE.md guidelines for philosophy and recommended practices, and .claude/rules for enforceable constraints.
  • Path-scoped enforcement: use frontmatter paths to limit rule applicability to specific files or directories and support recursive discovery.
  • Hierarchical precedence: project-level rules override user-level rules to maintain governance while allowing team-specific customization.
  • Reusable resources: templates, examples, and references to accelerate policy creation and compliance.

Quick Start

Place CLAUDE.md at the project root and add your rules under .claude/rules/ to start enforcing standards with CI or tooling.

Frequently Asked Questions about rules-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define and enforce project-specific coding standards with Claude Code?

You define project-specific coding standards by structuring guidelines in a root CLAUDE.md file and placing enforceable policies under .claude/rules, enabling Claude Code to apply them during development.

What is the two-layer rule system in Claude Code and how does it work?

The two-layer rule system separates philosophical guidelines in CLAUDE.md from machine-enforceable constraints in .claude/rules, allowing you to manage recommended practices and strict policies separately.

Can I scope Claude Code rules to apply only to specific files or directories?

Yes, you can scope rules to specific files or directories using frontmatter paths, which limits rule applicability and supports recursive discovery within your project structure.

How do project-level rules override user-level rules for team-specific customization?

Project-level rules override user-level rules through hierarchical precedence, maintaining overall governance while allowing teams to apply customized policies and standards to their specific directories.

What is the best way to structure CLAUDE.md and .claude/rules to enforce API design policies?

Place your architecture and API design philosophy in the root CLAUDE.md, then create specific enforceable API constraints as files under .claude/rules, using frontmatter paths to target relevant directories.

Do I need additional dependencies to enforce project standards in CI pipelines?

No additional dependencies are required; you place CLAUDE.md at the project root and rules under .claude/rules, then integrate rule enforcement directly with your existing CI or tooling.