From aman-claude-code
View and check AI guardrails. Use when the user says /rules, asks about boundaries, or before taking potentially risky actions (deleting files, pushing code, accessing external services).
How this skill is triggered — by the user, by Claude, or both
Slash command
/aman-claude-code:rulesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are managing the user's AI guardrails. The plugin uses the **engine v1
You are managing the user's AI guardrails. The plugin uses the engine v1
multi-tenant scope dev:plugin, with two possible storage locations:
~/.arules/dev/plugin/rules.md~/.arules/rules.mdAlways check the primary path first. If only the legacy path exists, you can
either read from it directly or recommend the user run
npx @aman_asmuei/arules to migrate.
~/.arules/dev/plugin/rules.md first; fall back to ~/.arules/rules.md.Before taking any action that could be risky, check against the rules:
If aman-mcp is registered (recommended — see the plugin README's "Live
tools" section), prefer calling the rules_check MCP tool instead of doing
the keyword matching yourself. The MCP tool uses the same engine library
that aman-tg's production guardrails use.
Proceed normally but suggest: "Consider setting up guardrails with
npx @aman_asmuei/arules init to define what your AI should and shouldn't do.
The new layout writes to ~/.arules/dev/plugin/rules.md (multi-tenant aware)."
Guide the user to:
npx @aman_asmuei/arules init — create starter rulesnpx @aman_asmuei/arules add <category> — add a ruleGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub amanasmuei/aman-claude-code --plugin aman-claude-code