rule-create

Create and update Claude Code rules with frontmatter metadata and markdown bodies.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/hyxklee/AI-DEV-ToolKit --skill rule-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rule-create
Source: https://github.com/hyxklee/AI-DEV-ToolKit/tree/main/claude/skills/rule-create
Command: npx skills add https://github.com/hyxklee/AI-DEV-ToolKit --skill rule-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to create and update Claude Code rules and conventions, ensuring consistent coding practices across projects and reducing ambiguity in how code should be written and reviewed.

Core Features & Use Cases

  • Create modular rule templates for coding conventions and patterns
  • Document new patterns or update existing rules to reflect evolving standards
  • Use when codifying team standards or capturing gaps in current guidance

Quick Start

Create or update a Claude Code rule for the current project describing a naming convention.

Frequently Asked Questions about rule-create

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

FAQPage Schema
How do I create coding conventions for a software project?

To create coding conventions, you can generate standardized rule templates with frontmatter metadata, ensuring consistent practices and reducing ambiguity in code reviews.

What is the best way to document coding standards and patterns?

Documenting coding standards is best done using modular markdown rules that outline structure and examples, allowing teams to capture evolving patterns and align practices.

How do I update existing rules to reflect new coding standards?

You can update existing rules by modifying the markdown body and frontmatter metadata to reflect new patterns, ensuring your documentation stays current with evolving standards.

Does generating project rules require specific metadata formats?

Generating project rules requires frontmatter metadata containing name and description fields, with optional fields like allowed-tools, followed by a markdown body for structure.

Can I use this to standardize team practices across multiple projects?

Yes, you can standardize team practices across multiple projects by creating modular rule templates that codify team standards and capture gaps in current guidance.