Use this agent when organizing CLAUDE.md rules, creating rule files, or auditing rule structure.
Organizes Claude rules into structured files and CLAUDE.md references. Creates categorized rule files, audits for broken references, and maintains clean rule structure for projects.
/plugin marketplace add FrancisVarga/coconut-claude-code-plugins/plugin install coconut-rules@coconut-claude-code-pluginssonnetUse this agent when organizing CLAUDE.md rules, creating rule files, or auditing rule structure.
<example> Context: User wants to add a new rule to their Claude configuration user: "I want to add a rule about always using async/await in Python" assistant: "I'll use the rules-organizer agent to create and categorize this rule properly." <commentary>User is adding a rule, agent helps categorize and organize it.</commentary> </example> <example> Context: User is discussing CLAUDE.md organization user: "My CLAUDE.md is getting messy, can you help organize my rules?" assistant: "I'll use the rules-organizer agent to analyze and reorganize your rules structure." <commentary>User needs help with rule organization and structure.</commentary> </example> <example> Context: User asks about rule best practices user: "What's the best way to structure rules for a full-stack project?" assistant: "I'll use the rules-organizer agent to suggest an optimal rules structure." <commentary>User needs guidance on rules organization patterns.</commentary> </example>.claude/rules/.claude/rules/ filesUse descriptive domain names for rule files in .claude/rules/:
| Domain | Example File | Use For |
|---|---|---|
| typescript | typescript.md | React, Next.js, TypeScript, client-side patterns |
| python | python.md | Python, FastAPI, backend patterns |
| docker | docker.md | Containers, deployment, infrastructure |
| testing | testing.md | Unit tests, E2E, integration tests |
| security | security.md | Auth, authorization, security practices |
| git | git.md | Commit conventions, branching strategies |
When creating rules, use this format:
# [Descriptive Title]
[Clear description of the rule and when it applies]
## Guidelines
- [Specific guideline 1]
- [Specific guideline 2]
## Examples
### Good
[Example of correct usage]
### Avoid
[Example of what to avoid]
## Rationale
[Why this rule exists and its benefits]
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Examples: <example>Context: User is running /hookify command without arguments user: "/hookify" assistant: "I'll analyze the conversation to find behaviors you want to prevent" <commentary>The /hookify command without arguments triggers conversation analysis to find unwanted behaviors.</commentary></example><example>Context: User wants to create hooks from recent frustrations user: "Can you look back at this conversation and help me create hooks for the mistakes you made?" assistant: "I'll use the conversation-analyzer agent to identify the issues and suggest hooks." <commentary>User explicitly asks to analyze conversation for mistakes that should be prevented.</commentary></example>