← ClaudeAtlas

ruleslisted

**Bare-slash canonical (Claude Code).** `/rules` resolves to this skill when both aria-knowledge and aria-cowork are loaded in the same session. RUNTIME GATE: if invoked from a non-Code runtime (no Bash tool available, e.g., Claude Cowork), the Runtime Gate section surfaces a notification suggesting `/aria-cowork:rules` and requires explicit user confirmation before proceeding — even in `auto` mode (ADR-094 §Part 3). Quick lookup into working rules. Use when user says '/rules', '/rules 22', '/rules dependencies', 'look up rule about...', 'what rule covers...', or references a specific rule number.
mikeprasad/aria-knowledge · ★ 12 · AI & Automation · score 66
Install: claude install-skill mikeprasad/aria-knowledge
# /rules — Quick Rule Lookup Look up rules from both the plugin's `working-rules.md` and the user's optional `user-rules.md`. ## Runtime Gate (per ADR-094) **Before Step 0:** Check that `Bash` is available. If `Bash` is NOT available (e.g., Cowork), surface: > ⚠️ **Runtime mismatch — you invoked aria-knowledge's `/rules` from a non-Code runtime.** > > Behavior is largely the same in both runtimes (both look up `working-rules.md` + `user-rules.md`); for the Cowork-native variant (reads from the attached knowledge folder), use `/aria-cowork:rules`. > > Proceed with the aria-knowledge variant anyway? (`y` / `n`) Wait for `y` / `yes`. **Gate applies even in `auto`** (ADR-094 §Part 3). If `Bash` is available, proceed to Step 0. ## Step 0: Resolve Config Read `~/.claude/aria-knowledge.local.md` and extract `knowledge_folder`. If the file doesn't exist, stop: "aria-knowledge is not configured. Run /setup to get started." Set two rules file paths: - **Plugin rules:** `{knowledge_folder}/rules/working-rules.md` - **User rules:** `{knowledge_folder}/rules/user-rules.md` (optional — may not exist for users on pre-v2.8.1 setups) If the plugin rules file doesn't exist, stop: "No working-rules.md found in your knowledge folder. Run /setup to repair the structure." If the user rules file doesn't exist, proceed with plugin rules only — this is the normal state for users who haven't added any custom rules. ## Step 1: Parse Argument Check what argument was provided: - **No argument