What problem does it solve? Admin and dev-tool pages in this repo repeatedly hand-roll the same MCP Inspector layout — a topbar over a three-column grid of tool tree, parameter form, and tabbed output — leading to duplicated CSS, inconsistent markup, and conversion bugs. This Skill standardizes that layout onto the shared InspectorShell, InspectorListItem, and InspectorTabs components. ## Core Features & Use Cases - Component Reference: Documents every prop and CSS classname of InspectorShell, InspectorListItem, and InspectorTabs so pages compose the layout without inventing new topbar/grid rules. - Two Guided Paths: A conversion path for migrating existing pages (inventory content, swap markup, migrate classnames, preserve behavior) and a scaffolding path for building new pages from scratch. - Verification Checklist: Enforces the repo's regression-guard, worktree workflow, emoji allowlist, UI build gate, and manual click-through before work is considered done. - Use Case: When adding a new admin page that needs a tool list on the left, an action form in the middle, and tabbed JSON output on the right, compose it directly on InspectorShell instead of copying McpInspectorPage's markup. ## Quick Start Ask the AI to convert an existing tool page to the inspector template or scaffold a new inspector-style page using the shared InspectorShell components.