Remotemini — Development skill for Claude Code

RemoteMini

An iPhone front-end for Claude Code sessions that run on a Mac at home. The phone talks to a small Node "desk" (`rc-backend/`) that sits beside Claude Code on the Mac; the desk is reachable only over a Tailscale tailnet, never the public internet.

This is a personal tool, built in the open. It is not packaged for other people yet: there is no installer, the docs are mostly Japanese, and the iOS app is distributed to one phone by ad-hoc OTA. What is meant to be reusable is the **harness**: the way changes are gated, verified and shipped.

Layout

Path	What it is
ios/	SwiftUI iPhone app (XcodeGen project, unit + UI tests)
rc-backend/	Node desk: session list, transcript digest, working-tree diff, OTA hosting
rc-backend/tools/	The harness: pre-commit gate chain, deploy and OTA scripts, PII checker
rc-backend/test/	Desk tests plus *-controls.sh negative controls for each gate
research/	Feature-parity notes against the native Remote Control experience
.harness/	Evidence per day, review logs, the redaction pipeline for this public copy

The harness, in one paragraph

Every commit runs a chain of gates (`rc-backend/tools/pre-commit-gates.sh`). Each gate has a matching *control*: a script that mutates the code or the docs in a way the gate must catch, and fails the build if the gate stays green. So the question asked of every gate is not "does it pass" but "can it still fail". Line references in Markdown are ratcheted against real files, cited test names must exist, evidence files must name what ran, and mutation targets must be killed by the test suite. Production effect (deploying the desk, cutting an OTA build) only happens through scripts that observe live state first and leave a verifier artifact behind.

Two repositories

The raw history lives in a private repository. This public one is a derived copy: `.harness/publish-public.sh` clones the raw repo into a sandbox, rewrites the w