askill
setup-rules

setup-rulesSafety 95Repository

Set up Claude Code rules in a project by symlinking from the rbw-claude-code templates. Use this skill when users want to add Python coding standards, anti-slop rules, or other shared rules to their projects.

0 stars
1.2k downloads
Updated 1/24/2026

Package Files

Loading files...
SKILL.md

Setup Rules

This skill helps you set up Claude Code rules in your project by creating symlinks to shared rule templates. This allows you to maintain consistent coding standards across multiple projects.

Available Rule Sets

Python Rules

Comprehensive Python coding standards extracted from best practices:

RuleDescription
asyncio.mdStructured concurrency, TaskGroup, fault isolation
typing.mdModern type hints, Protocols, TypeVar
architecture.mdSOLID principles, dependency injection
testing.mdTDD, pytest patterns, fixtures
prohibited.mdBanned practices checklist

General Rules

RuleDescription
anti-slop.mdPrevent AI-generated code slop

Quick Setup

Option 1: Link All Python Rules

# Create .claude/rules directory in your project
mkdir -p .claude/rules

# Get the path to rbw-claude-code (adjust as needed)
RBW_CLAUDE_CODE="${HOME}/.claude/plugins/marketplaces/rbw-claude-code"

# Symlink all Python rules
for rule in asyncio typing architecture testing prohibited; do
  ln -sf "${RBW_CLAUDE_CODE}/templates/rules/python/${rule}.md" .claude/rules/
done

# Optionally add anti-slop
ln -sf "${RBW_CLAUDE_CODE}/templates/rules/anti-slop.md" .claude/rules/

Option 2: Link Specific Rules

mkdir -p .claude/rules

RBW_CLAUDE_CODE="${HOME}/.claude/plugins/marketplaces/rbw-claude-code"

# Just asyncio and typing
ln -sf "${RBW_CLAUDE_CODE}/templates/rules/python/asyncio.md" .claude/rules/
ln -sf "${RBW_CLAUDE_CODE}/templates/rules/python/typing.md" .claude/rules/

Option 3: Use the Setup Script

bash ${CLAUDE_PLUGIN_ROOT}/skills/setup-rules/scripts/setup-rules.sh

The script will interactively guide you through selecting which rules to install.

Manual Installation (Copy Instead of Symlink)

If you prefer to customize rules per-project:

mkdir -p .claude/rules

RBW_CLAUDE_CODE="${HOME}/.claude/plugins/marketplaces/rbw-claude-code"

# Copy rules (can be modified)
cp "${RBW_CLAUDE_CODE}/templates/rules/python/"*.md .claude/rules/
cp "${RBW_CLAUDE_CODE}/templates/rules/anti-slop.md" .claude/rules/

Verify Installation

Check your rules are properly linked:

ls -la .claude/rules/

You should see symlinks pointing to the template files, or copied files if you chose that option.

Project Structure After Setup

your-project/
├── .claude/
│   └── rules/
│       ├── asyncio.md -> /path/to/templates/rules/python/asyncio.md
│       ├── typing.md -> /path/to/templates/rules/python/typing.md
│       ├── architecture.md -> ...
│       ├── testing.md -> ...
│       ├── prohibited.md -> ...
│       └── anti-slop.md -> /path/to/templates/rules/anti-slop.md
├── src/
└── ...

Updating Rules

When rules are updated in rbw-claude-code:

  • Symlinked rules: Automatically get updates when you pull the latest rbw-claude-code
  • Copied rules: Need to be manually updated or re-copied

Removing Rules

# Remove specific rule
rm .claude/rules/asyncio.md

# Remove all rules
rm -rf .claude/rules/

Troubleshooting

Symlink shows as broken

The target path may have changed. Re-run the setup:

rm .claude/rules/*.md
# Re-run setup commands

Rules not being applied

  1. Check the rules directory exists: ls .claude/rules/
  2. Verify file permissions: ls -la .claude/rules/
  3. Ensure symlinks point to valid targets: file .claude/rules/*

Want to override a specific rule

Copy just that rule instead of symlinking:

# Remove symlink
rm .claude/rules/asyncio.md

# Copy and customize
cp "${RBW_CLAUDE_CODE}/templates/rules/python/asyncio.md" .claude/rules/
# Edit .claude/rules/asyncio.md as needed

Install

Download ZIP
Requires askill CLI v1.0+

AI Quality Score

74/100Analyzed 2/24/2026

Well-structured skill with clear, actionable instructions for setting up Claude Code rules. Provides multiple setup options (symlink all, specific rules, script, manual copy), verification steps, and troubleshooting. Slightly penalized for internal-only signals (path in .codex/.claude directory, project-specific tags). Content is complete with good clarity but reusability is limited due to tight coupling with rbw-claude-code project structure.

95
90
60
85
92

Metadata

Licenseunknown
Version-
Updated1/24/2026
PublisherRBozydar

Tags

llmtesting