react-ui-org / react-ui / 28786109308

61%

push

github

Add Claude Code project configuration with chrome-host MCP bridge for browser automation

Introduce CLAUDE.md and a .claude/ directory so Claude Code works from the
project's documented conventions instead of guessing.

* CLAUDE.md — entry doc: project overview, the devcontainer command workflow,
  and an index of rules, agents and the `/commit` skill.
* .claude/rules/ — always-on rules (code, git, safety-guards) and path-scoped
  rules (frontend, styling, testing, docs) carrying the project conventions.
* .claude/skills/commit/ — the `/commit` skill for committing per project rules.
* .claude/agents/code-reviewer.md — a repo-tailored review agent.
* .claude/settings.json — scoped command permissions and enables the
  `chrome-host` MCP server (plus the GitHub and Context7 plugins).

Speaking of chrome-host MCP bridge:

Add tooling that lets an MCP-capable assistant in the `devcontainer` drive
Chrome running on the host via `chrome-devtools-mcp` over the Chrome DevTools
Protocol.

Because the container can only reach the host through `host.docker.internal`
and Chrome's DevTools endpoint rejects non-IP `Host` headers, a small loopback
proxy (`cdp_proxy.py`) runs inside the `node` container and forwards to host
Chrome, so the `Host` Chrome sees stays `127.0.0.1`.

Includes the host launcher (`start-host-chrome.sh`, throwaway profile opening
the docs site), the in-container launcher and entry scripts, native-Docker
host-gateway setup, MCP registration for Claude/Copilot (`.mcp.json`) and
OpenCode (`opencode.json`), and documentation.

105 of 204 branches covered (51.47%)

Branch coverage included in aggregate %.

159 of 230 relevant lines covered (69.13%)

6.73 hits per line