Refactor tool implementations format

Changed from hidden sections to visible 'Tool Implementations:' header with individual tool names as expandable links. This improves discoverability while maintaining clean organization.

Author: inmve

README.md

@@ -58,17 +58,24 @@ Create context files that persistently guide tools about your project's structur
 > "`CLAUDE.md` is a special file that Claude automatically pulls into context when starting a conversation. This makes it an ideal place for documenting: common bash commands, core files and utility functions, code style guidelines, testing instructions."
 > — [Anthropic](https://www.anthropic.com/engineering/claude-code-best-practices#:~:text=CLAUDE.md%20is%20a%20special%20file)
 
+**Tool Implementations:**
+
 <details>
-<summary><strong>🛠️ Tool Implementations</strong></summary>
+<summary><strong>Claude Code</strong></summary>
 
-**Claude Code**: Run `/init` to auto-generate smart context files that make Claude understand your codebase instantly. Claude analyzes dependencies, scripts, and architecture automatically. Use `/memory` to edit and add project-specific gotchas.
+Run `/init` to auto-generate smart context files that make Claude understand your codebase instantly. Claude analyzes dependencies, scripts, and architecture automatically. Use `/memory` to edit and add project-specific gotchas.
 
 - For new projects: Run `/init` in your project root to create a starter `CLAUDE.md`
 - For existing codebases: Run `/init` and Claude will analyze your project structure, dependencies, and configuration files to automatically generate essential information
 - Use `/memory` for full editor interface or `#` as quick shortcut to add notes
 - Memory file hierarchy: `~/.claude/CLAUDE.md` (global) and `./CLAUDE.md` (project-specific)
 
-**Cursor**: Create `AGENTS.md` for project rules, then use @codebase and @docs for dynamic context. Cursor's superpower is real-time understanding of your entire codebase through @-mentions.
+</details>
+
+<details>
+<summary><strong>Cursor</strong></summary>
+
+Create `AGENTS.md` for project rules, then use @codebase and @docs for dynamic context. Cursor's superpower is real-time understanding of your entire codebase through @-mentions.
 
 - Create `AGENTS.md` at project root (also supports legacy `.cursorrules`)
 - Real-time context: Use `@codebase` to pull in relevant files automatically, `@docs` to reference documentation, `@git` to understand recent changes
@@ -276,18 +283,25 @@ Stop waiting for one AI agent to finish before starting another - run multiple a
 > "I disable all permission checks. Which basically means I run claude --dangerously-skip-permissions. More specifically I have an alias called claude-yolo set up."
 > — [Armin Ronacher](https://lucumr.pocoo.org/2025/6/12/agentic-coding/#:~:text=I%20disable%20all%20permission%20checks)
 
+**Tool Implementations:**
+
 <details>
-<summary><strong>🛠️ Tool Implementations</strong></summary>
+<summary><strong>Claude Code</strong></summary>
 
-**Claude Code**: Use `--dangerously-skip-permissions` on launch or `/permissions` to change permission strategy during coding session.
+Use `--dangerously-skip-permissions` on launch or `/permissions` to change permission strategy during coding session.
 
 - Run `claude --dangerously-skip-permissions` to enable autonomous mode where Claude runs uninterrupted without permission prompts
 - Switch during session: Use `/permissions` to manage tool permissions mid-session without restarting
 - When to use: Fixing lint errors across multiple files, simple refactoring and variable renames, routine code updates and migrations
 - Safety: Best used in containers or VMs for isolation, avoid on critical production systems
 - Setup alias: Many users create `alias cc='claude --dangerously-skip-permissions'` for quick access
 
-**Codex CLI**: Use `--full-auto` on launch or `/mode` to change permission strategy during coding session.
+</details>
+
+<details>
+<summary><strong>Codex CLI</strong></summary>
+
+Use `--full-auto` on launch or `/mode` to change permission strategy during coding session.
 
 - Enable full autonomous mode with `codex --full-auto` or use in-session `/mode` command
 - Switch during session: Use `/mode` to hot-swap between permission levels without losing session context
@@ -310,16 +324,23 @@ Begin with faster/cheaper models for routine tasks, then escalate to more powerf
 > "Sonnet 4 handles 90% of tasks effectively. Switch to Opus when Sonnet gets stuck. Recommend starting with Sonnet and providing comprehensive context."
 > — [Sankalp](https://sankalp.bearblog.dev/my-claude-code-experience-after-2-weeks-of-usage/#:~:text=Sonnet%204%20handles%2090%25)
 
+**Tool Implementations:**
+
 <details>
-<summary><strong>🛠️ Tool Implementations</strong></summary>
+<summary><strong>Claude Code</strong></summary>
 
-**Claude Code**: Use `/model` to switch between models based on task complexity. Start with cheaper Sonnet 4 for routine work, escalate to fast Opus 4.1 when stuck.
+Use `/model` to switch between models based on task complexity. Start with cheaper Sonnet 4 for routine work, escalate to fast Opus 4.1 when stuck.
 
 - Use `/model` to switch models during your session
 - Cheaper, faster option: `Claude Sonnet 4`
 - Top-graded option: `Claude Opus 4.1`
 
-**Codex CLI**: Use `/model` to escalate when needed. Start with `gpt-5-medium` for most tasks, switch to `gpt-5-high` when you hit complex problems.
+</details>
+
+<details>
+<summary><strong>Codex CLI</strong></summary>
+
+Use `/model` to escalate when needed. Start with `gpt-5-medium` for most tasks, switch to `gpt-5-high` when you hit complex problems.
 
 - Use `/model` to switch models during your session
 - Cheaper, faster option: `gpt-5-medium`
@@ -341,16 +362,23 @@ Reset the AI's context window between unrelated tasks to prevent confusion and i
 > "During long sessions, Claude's context window can fill with irrelevant conversation, file contents, and commands. This can reduce performance and sometimes distract Claude. Use the `/clear` command frequently between tasks to reset the context window."
 > — [Anthropic](https://www.anthropic.com/engineering/claude-code-best-practices#:~:text=During%20long%20sessions%2C%20Claude's%20context)
 
+**Tool Implementations:**
+
 <details>
-<summary><strong>🛠️ Tool Implementations</strong></summary>
+<summary><strong>Claude Code</strong></summary>
 
-**Claude Code**: Use `/clear` command to reset the context window and start fresh.
+Use `/clear` command to reset the context window and start fresh.
 
 - Run `/clear` between unrelated tasks to prevent context pollution
 - Preserves your memory files (CLAUDE.md) while clearing conversation history
 - Essential for long coding sessions to maintain performance
 
-**Cursor**: Start new chat sessions or use conversation management features.
+</details>
+
+<details>
+<summary><strong>Cursor</strong></summary>
+
+Start new chat sessions or use conversation management features.
 
 - Use Cmd/Ctrl+Shift+L to start a new chat for unrelated tasks
 - Chat history is automatically managed to prevent context overload
@@ -372,17 +400,24 @@ Don't let AI go too far down the wrong path - interrupt, provide feedback, and r
 > "Press Escape to interrupt Claude during any phase (thinking, tool calls, file edits), preserving context so you can redirect or expand instructions. Double-tap Escape to jump back in history, edit a previous prompt, and explore a different direction. You can edit the prompt and repeat until you get the result you're looking for."
 > — [Anthropic](https://www.anthropic.com/engineering/claude-code-best-practices#:~:text=Press%20Escape%20to%20interrupt%20Claude)
 
+**Tool Implementations:**
+
 <details>
-<summary><strong>🛠️ Tool Implementations</strong></summary>
+<summary><strong>Claude Code</strong></summary>
 
-**Claude Code**: Use Escape key to interrupt and redirect Claude at any time.
+Use Escape key to interrupt and redirect Claude at any time.
 
 - Press `Escape` to interrupt Claude during any phase (thinking, tool calls, file edits)
 - Double-tap `Escape` to jump back in history and edit a previous prompt
 - Context is preserved so you can redirect or expand instructions
 - Edit the prompt and retry until you get the desired result
 
-**Cursor**: Use Cmd/Ctrl+K to stop generation and provide new instructions.
+</details>
+
+<details>
+<summary><strong>Cursor</strong></summary>
+
+Use Cmd/Ctrl+K to stop generation and provide new instructions.
 
 - Stop generation with `Cmd/Ctrl+K` when you see it going off track
 - Provide corrective feedback immediately rather than waiting