frontend-10x-browser-debugging Cursor ruleA
frontend-10x-browser-debugging from kevin-liu-01/loop is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add kevin-liu-01/loop/.cursor/rules/frontend-10x-browser-debugging.mdc@git:20260330.383174bPins git:20260330.383174b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Cursor rule
- Repository
- kevin-liu-01/loop
- Path
.cursor/rules/frontend-10x-browser-debugging.mdc- Versions recorded
- 2
- Latest version
- git:20260330.383174b, committed Mar 30, 2026
- First version recorded
- Mar 28, 2026
- Size
- 1,937 bytes
- Repository stars
- 17
- License
- MIT
Prefer live-browser Chrome DevTools MCP for localhost and manual debugging; keep Playwright as deterministic fallback.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Browser Debugging Preference When browser automation or debugging is needed: - Prefer `chrome-devtools-live` when the user already has Chrome open, is logged in, or wants the agent to inspect the current browser state. - Prefer `chrome-devtools-port` when testing localhost repeatedly or when a reusable dedicated debug browser is better than the user’s normal browsing session. - Use Playwright when isolation, deterministic repro, or fresh auth state is the actual goal. - Do not default to Playwright if the user clearly wants the current browser session or selected DevTools state. - For localhost work, favor going straight into the browser via Chrome DevTools MCP before spinning up a fresh browser automation lane. Operational rules: - `chrome-devtools-live` requires remote debugging enabled at `chrome://inspect/#remote-debugging` and a user approval prompt. - `chrome-devtools-port` assumes Chrome was launched with a remote debug port, for example via `/Users/kevinliu/.codex/bin/open-chrome-debug.sh http://localhost:3000`. - Playwright is fallback, not the first move, for manual browser debugging. Cleanup rules: …
Read the whole file at its exact version.
How to install
mdr add kevin-liu-01/loop/.cursor/rules/frontend-10x-browser-debugging.mdc@sha256:8eb49c5075780ed4The line at the top of this page pins the label git:20260330.383174b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_xfkc2y6hqegpzqeh)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Mar 28, 2026 and Mar 30, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260330.383174b latest | 2026-03-30 | 383174b | 1,937 B | A | view · diff |
| git:20260328.8d98085 | 2026-03-28 | 8d98085 | 1,318 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (1937 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kevin-liu-01/loop · 17 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xfkc2y6hqegpzqeh GET https://markdownregistry.com/api/v1/resolve?ref=kevin-liu-01/loop/.cursor/rules/frontend-10x-browser-debugging.mdc GET https://markdownregistry.com/api/v1/blob/8eb49c5075780ed4f83c6cd1939bd33bf9ef8bcc798b9d2172fa9a084a656fa9
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: Cursor rules vs AGENTS.md · which agent file does what.