add-rule

Create or update Claude Code rules from plain-language instructions.

15|3|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/Eigenwise/eigenwise-toolshed --skill add-rule-eigenwise
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: add-rule
Source: https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/live-rules/skills/add-rule
Command: npx skills add https://github.com/Eigenwise/eigenwise-toolshed --skill add-rule-eigenwise

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you turn a plain-language preference, guardrail, or workflow reminder into a live-rules entry that Claude injects at the right moment. It removes the need to manually edit low-level project config or keep repeating the same instruction.

Core Features & Use Cases

  • Create or edit rules: Add a new instruction or update an existing one in the project's live-rules file.
  • Scope rules correctly: Choose global, file-path, directory, prompt-keyword, or include-based behavior depending on when the rule should fire.
  • Use atomic storage safely: Write rule files under .claude/live-rules/rules/ and sync the generated manifest with the plugin-owned command.
  • Migration support: Help existing projects keep legacy .claude/live-rules.md rules while they transition to the atomic directory format.
  • Practical example: Use it to add a rule like "always run the linter before committing" or "prefer function components in TSX files" so Claude applies it automatically.

Quick Start

Ask the assistant to add a live rule for your desired instruction, specify when it should apply, and have it write the rule to the project's live-rules file.

Frequently Asked Questions about add-rule

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

FAQPage Schema
How do I add live Claude Code rules from plain-language instructions?▼

Live Claude Code rules work by storing instructions atomically in the .claude/live-rules/rules/ directory. A generated manifest is synced with a plugin-owned command to ensure instructions are reliably injected at the correct moments during repository workflows.

What's the best way to scope prompt-triggered reminders for repository workflows?▼

You can scope prompt-triggered reminders by choosing global, file-path, directory, or prompt-keyword behavior. This targets when the rule should fire based on your active repository context and edit-time guardrails.

How do I migrate existing live-rules.md files to atomic rule storage?▼

Migrating existing live-rules.md files to atomic rule storage is supported natively. The system helps legacy projects keep their rules while transitioning them into the atomic .claude/live-rules/rules/ directory format.

Can I use add-rule to enforce edit-time guardrails for specific file paths?▼

Yes, you can enforce edit-time guardrails for specific file paths by selecting the file-path or directory scope. This ensures the injected rule applies always-on guidance specifically when editing targeted files in your repository.

Why do my Claude Code live rules fail to inject reliably?▼

Claude Code live rules fail to inject reliably if rule frontmatter is missing, scope selection is incorrect, or the generated manifest is not synced with the plugin-owned command. Proper atomic storage and sync validation are required.