메뉴
Krometrail MCP navigation guide. Load this skill first to understand which tool namespace to use. Covers the three tool namespaces (debug_*, chrome_*, session_*), when to use each, common pitfalls, and pointers to the detailed skill for each namespace.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | krometrail-mcp |
| description | Krometrail MCP navigation guide. Load this skill first to understand which tool namespace to use. Covers the three tool namespaces (debug_*, chrome_*, session_*), when to use each, common pitfalls, and pointers to the detailed skill for each namespace. |
Load this skill first. Then load the detailed skill for what you're doing.
Krometrail exposes three MCP tool namespaces. Picking the wrong one wastes sessions and produces confusing errors.
debug_* — Code debugger (DAP)Steps through source code, inspects variables, evaluates expressions.
Use when: Debugging Python, Node.js, Go, TypeScript, Ruby, Java, Rust, C#, C++, Swift.
Load the skill: Load krometrail-debug for the full tool reference, language setup, breakpoint syntax, and debugging strategies.
Pitfall: debug_launch runs a shell command — do NOT pass a URL. It will fail.
chrome_* — Browser recording & control (CDP)Launches Chrome, records browser events, and drives the browser with batch actions.
Use when: Observing a web app — reproducing a bug, recording a user flow, capturing network traffic, driving the browser (navigate, click, fill forms), or refreshing the page for a clean slate (chrome_refresh).
Load the skill: Load krometrail-chrome for the full tool reference, Chrome setup, step actions, and investigation strategies.
Pitfall: Always pass profile: 'krometrail' to chrome_start to avoid conflicts with any existing Chrome instance.
session_* — Browser session investigation (read-only)Queries recorded browser sessions from the local database.
Use when: Investigating what happened in a browser session recorded with chrome_* tools.
Load the skill: Covered in krometrail-chrome — session investigation tools are part of that skill.
| Goal | Load skill |
|---|---|
| Debug Python, JS, Go, Rust, Java, C++, C# | krometrail-debug |
| Record or observe a web app in Chrome | krometrail-chrome |
| Investigate a recorded browser session | krometrail-chrome |
| Drive the browser with clicks/navigation | krometrail-chrome |
debug_launch. It runs shell commands. Use chrome_start for browser tasks.chrome_start without profile may fail with a CDP error. Always use profile: 'krometrail' for an isolated instance./usr/bin/google-chrome) may delegate to an existing Chrome and exit immediately, causing chrome_start to fail. If this happens, ask the user to close their Chrome browser and retry. Do NOT suggest pkill — it can kill Electron apps (Discord, VS Code, etc.) that have chrome in their process names.debug_* tools require a session_id returned by debug_launch. All session_* tools accept session_id: "latest" for convenience.debug_stop. Debug sessions don't self-terminate. Call debug_stop(session_id: '...') when done or the debugger process will linger.krometrail-debug skill for per-language setup.debug_*)When using debug tools, read the reference for your target language:
references/python.mdreferences/node.mdreferences/go.mdkrometrail-debug skillBrowser recording and control via the krometrail CLI. Use when recording a browser session, driving the browser with batch actions, or investigating recorded sessions. Captures network, console, DOM, framework state, screenshots.
Runtime debugging via the krometrail CLI. Use when a test fails and reading the code isn't enough, when you need to inspect runtime values, or when a bug is in logic you can't trace statically. Set breakpoints, step through code, inspect variables, evaluate expressions — across 10 languages.
Project structural organization rules for TypeScript/Bun. Proactively scans for organizational issues and produces a prioritized plan. Defines the team's preferred file, folder, and module structure.
Project stylistic refactoring rules for TypeScript/Bun. Proactively scans for refactoring opportunities and produces a prioritized plan. Defines the team's preferred coding style.
Project code patterns and conventions. Auto-loads when implementing, designing, verifying, or reviewing code. Provides detailed pattern definitions with code examples.
React DevTools hook internals reference. Use when implementing or debugging React state observation — fiber tree traversal, hook linked lists, onCommitFiberRoot, state extraction, bug pattern detection.