brewcode:rules

Synchronize project rules and knowledge into `.claude/rules/` directory files.

30|2|Updated Jan 24, 2026

Search Tags:#best practices #documentation #anti-patterns #project guidelines #rules #knowledge sync

Ready to run

npx skills add https://github.com/kochetkov-ma/claude-brewcode --skill brewcode-rules

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brewcode:rules
Source: https://github.com/kochetkov-ma/claude-brewcode/tree/main/brewcode/skills/rules
Command: npx skills add https://github.com/kochetkov-ma/claude-brewcode --skill brewcode-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the management of project-specific guidelines by automatically updating rule files based on knowledge sources or session learnings, ensuring consistency and adherence to best practices.

Core Features & Use Cases

Automated Rule Syncing: Updates .claude/rules/ with avoid.md and best-practice.md files.
Knowledge Integration: Extracts rules from KNOWLEDGE.jsonl files, specified file paths, or directly from the current session's conversation.
Use Case: After a code review session where several anti-patterns were identified, use this Skill to automatically add those patterns to your project's avoid.md file.

Quick Start

Use the brewcode:rules skill to list all existing rule files in the project.

Frequently Asked Questions about brewcode:rules

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

FAQPage Schema

How do I sync project rules and knowledge into Claude automatically?▼

Project rule syncing works by processing information from KNOWLEDGE.jsonl files, specified file paths, or session learnings to update the `.claude/rules/` directory. It maintains `avoid.md` and `best-practice.md` files, including domain-specific variants, ensuring project guidelines stay consistent.

What's the best way to document anti-patterns identified during a code review?▼

The best way to document anti-patterns from a code review is using a Skill that extracts them from the current session and automatically adds them to your project's `avoid.md` file. This ensures identified anti-patterns are saved as persistent project guidelines for future reference.

How do I maintain best-practice.md files for specific domains?▼

Maintaining best-practice.md files for specific domains is supported by generating domain-specific variants within the `.claude/rules/` directory. The Skill processes knowledge sources to create and update these files, keeping domain-specific guidelines organized and current.

Do I need a specific agent to process project guidelines from KNOWLEDGE.jsonl?▼

Yes, processing project guidelines requires a `bc-rules-organizer` agent for organizing the information. Additionally, validation scripts are required to perform integrity checks on the generated rule files to ensure correctness.

Can I list existing project rules before adding new best practices?▼

Yes, you can list existing project rules before adding new best practices. Running the Skill lists all existing rule files in the project, allowing you to review current guidelines before synchronizing new knowledge or session learnings into the `.claude/rules/` directory.