How this command is triggered — by the user, by Claude, or both
Slash command
/mantra:make-rule <source-file.md>The summary Claude sees in its command listing — used to decide when to auto-load this command
# Make Rule: Convert Markdown to Frontmatter Rule Convert a verbose, human-readable markdown file into a token-efficient frontmatter-only rule file. ## Workflow ### Step 1: Identify Source File If no argument provided, ask the user: > What is the path to the verbose markdown file you want to compact? Read the source file to understand its content. ### Step 2: Analyze and Convert Transform the verbose markdown into compact YAML frontmatter: **Conversion Rules:** - Remove prose, explanations, complete sentences - Use key:value pairs with minimal words - Apply operators: `→` (flow), `...
Convert a verbose, human-readable markdown file into a token-efficient frontmatter-only rule file.
If no argument provided, ask the user:
What is the path to the verbose markdown file you want to compact?
Read the source file to understand its content.
Transform the verbose markdown into compact YAML frontmatter:
Conversion Rules:
→ (flow), > (priority), | (alternatives)pattern (example: value)no:, skip:, never:Output Format:
---
# {Title} - Compact Reference
companion: {source-filename}
## {Section Header}
key: value, value, value
another-key: flow → sequence → result
---
After creating the compact version, ask the user:
Are any of these rules CRITICAL - meaning Claude must absolutely follow them without exception?
If yes, describe which rules are critical and why.
When the user identifies critical rules, apply emphasis markers:
Emphasis Levels (use sparingly):
| Marker | Use When | Example |
|---|---|---|
MANDATORY-REREAD: | Must re-read before specific actions | MANDATORY-REREAD: before-commit (use-thinking-block) |
## SECTION (BLOCKING REQUIREMENT) | Entire section is non-negotiable | ## ASSESSMENT (BLOCKING REQUIREMENT) |
required-before: | Must happen before an action | required-before: git-operations, implementation |
must-verify: | Must explicitly check | must-verify: format-requirements |
enforcement: | Trigger conditions | enforcement: if user says X → do Y |
never: | Absolute prohibitions | never: skip-tests, guess-values |
Guidelines for CRITICAL markers:
MANDATORY-REREAD: for top-level blocking behaviors(BLOCKING REQUIREMENT) for section headers onlyenforcement: for if→then trigger rules(use-thinking-block) for verification requirementsPresent the final compact rule file to the user:
.claude/rules/{name}.md/mantra:init --force if updating existing ruleBefore (verbose):
# Code Review Guidelines
When reviewing code, always check for security vulnerabilities first.
This is extremely important and should never be skipped.
## Style Checks
- Check for consistent naming
- Verify imports are organized
- Look for unused variables
After (compact with critical marker):
---
# Code Review - Compact Reference
companion: code-review.md
MANDATORY-REREAD: before-code-review (use-thinking-block)
## SECURITY (BLOCKING REQUIREMENT)
check-first: vulnerabilities (never-skip)
verify: injection, auth, data-exposure
## Style
check: naming-consistency, import-organization, unused-variables
---
npx claudepluginhub flexion/claude-domestique --plugin mantra/forceInteractively selects CLAUDE.md rule files, collects rules, summarizes changes, and applies them to the project or specified path after confirmation.
/audit-rulesAudits .claude/rules/ files across enforceability, token efficiency, conflict detection, and correctness risk dimensions. Supports --full and --mini depth flags.
/rules-evalEvaluates Claude Code rules in .claude/rules/ directories for quality, scoring frontmatter validity, glob patterns, content, organization, and token efficiency out of 100 points.
/CLAUDEScans recent user messages for behavioral signals to auto-propose hookify rules (/hookify). Lists (/list) and configures (/configure) rules in .claude/hookify.*.local.md files.
/candid-validate-standardsValidates Technical.md for vague unverifiable rules, linter overlaps, unclear boundaries/thresholds, and overly complex rules. --fix suggests rewrites; specify custom path.