What problem does it solve? Agents often default to terminal commands for tasks that dedicated tools handle faster and more safely, leading to unstructured output, silent failures, and wasted context. This Skill enforces a deterministic tool-first policy for every file, search, and validation operation. ## Core Features & Use Cases - Tool Selection Matrix: Maps each intent (find files, search code, read files, edit files, check errors) to the correct dedicated tool and names the shell command to avoid. - MCP Tool Loading Workflow: Requires calling tool_search_tool_regex before using deferred MCP tools, with catalogs for Supabase, Vercel, Next.js DevTools, Context7, and Playwright browser automation. - Verification Loop: Mandates get_errors checks and re-reading edited regions after every file edit, plus sequential execution rules for terminal commands. - Use Case: When refactoring a Next.js app backed by Supabase, use this Skill to search code with grep_search, edit with multi_replace_string_in_file, apply schema migrations via the Supabase MCP, and verify with get_errors instead of scraping build logs. ## Quick Start Use the tools skill to decide which tool or command to use for searching, reading, and editing files in this project.
