organize-rules

Organizes global Claude Code rules and skills through naming, splitting, merging, and placement conventions.

Updated Dec 25, 2021
One-click install
npx skills add https://github.com/kotahashihama/dotfiles --skill organize-rules-kotahashihama
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: organize-rules
Source: https://github.com/kotahashihama/dotfiles/tree/main/home/.claude/skills/organize-rules
Command: npx skills add https://github.com/kotahashihama/dotfiles --skill organize-rules-kotahashihama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Global Claude Code rules and skills accumulate over time and become duplicated, misplaced, or unenforced. This Skill provides a systematic method for writing, placing, splitting, merging, and deleting rules and skills so the configuration stays consistent and actually gets followed. ## Core Features & Use Cases - Placement decisions: Routes each piece of guidance to the right location (global rules, project rules, skills, hooks, CLAUDE.md, or auto memory) based on scope and enforcement needs. - Writing conventions: Defines naming patterns (snake_case for rules, verb-object kebab-case for skills), section structure, and formatting consistency across SKILL.md files. - Deviation diagnosis: Classifies unenforced rules into five failure types plus a hook-escalation path, with concrete fixes for each. - Use Case: After noticing a rule was repeatedly violated, use this Skill to diagnose whether the rule lacks a procedure, depends on memory, or should be moved into a hook, then restructure it accordingly. ## Quick Start Ask the assistant to review and reorganize the rules in ~/.claude/rules/ and skills in ~/.claude/skills/ using the organize-rules skill.

Frequently Asked Questions about organize-rules

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

FAQPage Schema
How do I organize Claude Code rules and skills?

Inventory existing files with ls and grep before adding anything, keep one topic per file, and link related rules via a Related section. Split files with multiple topics, merge duplicates, and delete rules whose behavior is now default.

Where should I put a new Claude Code rule or skill?

Decide by scope first: universal behavior goes in ~/.claude/, repository-specific guidance goes in the project's .claude/. Then decide by type: always-on conventions go in rules, multi-step procedures go in skills, mandatory enforcement goes in hooks.

What is the difference between Claude Code rules and auto memory?

Rules are user-approved conventions that apply across all repositories, while auto memory holds repository-specific facts the assistant writes itself. Never duplicate content between them since both load every session; promote universal preferences from memory to rules and delete the original.

Why is my Claude Code rule not being followed?

Unenforced rules typically fail in five ways: missing procedure, reliance on memory across sessions, the main rule buried after decision steps, existence only in prose rather than a prohibitions list, or missing quantity units. If rewriting fails repeatedly, move enforcement to a hook.

How do I make a new Claude Code skill discoverable?

Placing a skill in the dotfiles repository is not enough; symlink it into ~/.claude/skills/ and verify the link resolves and SKILL.md is readable. Also test with a nonexistent name to confirm the check itself works.