← ClaudeAtlas

ruleslisted

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. (Code port — ADR-094.)
mikeprasad/aria-knowledge · ★ 16 · AI & Automation · score 64
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`. ## Step 0: Resolve Config Read `~/.gemini/antigravity/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:** go to Step 2 (index mode) - **Number with optional U prefix** (e.g., `22`, `U1`): go to Step 3 (lookup by identifier) - **Keyword** (e.g., `dependencies`): go to Step 4 (search mode) ## Step 2: Index Mode Read both files. Extract all rule headings (lines matching `### N. [title]` or `### UN. [title]`). Output a grouped list: ``` ## Working Rules Index ### Plugin Rules (working-rules.md) 1. Scope tasks tightly, but keep the whole system in view 2. Let errors guide where you add context ... ### Your Rules (user-rules.md) U1. Always run the linter locally before committing U2. Test data