plugins/core/skills/create-rule/SKILL.md
This skill should be used when developing custom rules for coding standards, conventions, or guidelines that Claude should follow. It covers rule structure, types, and best practices.
npx skillsauth add rbozydar/rbw-claude-code create-ruleInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Develop effective Claude Code rules. Rules are markdown files in .claude/rules/ that provide persistent instructions Claude follows during a session.
Not for: one-time instructions (tell Claude directly), dynamic content (use commands/skills), or tool configurations (use hooks).
# Rule Name
Brief description of what this rule enforces.
## Guidelines
Clear, actionable rules with examples.
## Checklist (optional)
- [ ] Quick verification items
Key principles: Be specific (vague rules get ignored), show examples (good vs bad), stay focused (one topic per file), be actionable (guide decisions).
Define coding standards. Copy and customize templates/standards.md:
cp ${CLAUDE_PLUGIN_ROOT}/skills/create-rule/templates/standards.md .claude/rules/my-standards.md
Use for: naming conventions, preferred patterns, type inference rules.
List things to avoid. Copy and customize templates/prohibited.md:
cp ${CLAUDE_PLUGIN_ROOT}/skills/create-rule/templates/prohibited.md .claude/rules/my-prohibited.md
Use for: banned patterns with good/bad examples, quick checklists.
Define formatting preferences. Copy and customize templates/style.md:
cp ${CLAUDE_PLUGIN_ROOT}/skills/create-rule/templates/style.md .claude/rules/my-style.md
Use for: import ordering, comment conventions, formatting preferences.
Define structural patterns for service layers, dependency direction, module organization.
Do: Use tables for quick reference, include code examples for every guideline, group related items, provide a checklist, keep rules under 200 lines.
Do not: Write walls of text, be vague ("write good code"), include too many topics in one file, repeat what other rules cover.
All templates are available at:
${CLAUDE_PLUGIN_ROOT}/skills/create-rule/templates/
├── standards.md # Coding standards template
├── prohibited.md # Prohibited patterns template
└── style.md # Style guide template
To add a rule to rbw-claude-code:
templates/rules/ or a subdirectorydevelopment
This skill should be loaded when writing, reviewing, or refactoring Python code to apply strict coding standards directly in the current context without spawning a subagent. It provides comprehensive Python development standards covering SOLID principles, asyncio patterns, type hints, testing, and production-quality code.
tools
This skill should be used when invoking the Gemini CLI for code review, plan review, or any prompt-based task. It provides correct invocation patterns emphasizing stdin piping and @ syntax over shell variable gymnastics.
development
Use this skill when writing, reviewing, or debugging Quickshell configurations (QML files for desktop shell UI on Wayland/Hyprland). Triggers on: QML files with Quickshell imports, shell.qml entry points, PanelWindow or FloatingWindow usage, Quickshell service integration (PipeWire, MPRIS, notifications, Hyprland IPC), Wayland layer-shell or session-lock code, custom bar/panel/widget/dock/OSD/lockscreen/launcher development, or any question about building a desktop shell with Quickshell on Hyprland.
development
This skill should be used when thorough, multi-perspective research with citations is needed. It performs comprehensive research using a diffusion research loop with domain specialization, supporting general web research and specialized domains (geopolitical with GDELT). Auto-detects domain from query or accepts an explicit --domain flag.