~ / rigs / JayCRL / MobileVC

JayCRL/MobileVC

Turn your phone into the control center for an AI coding assistant CLI session (Claude or Codex) running on your computer.

↗ GitHub ★ 186 mit updated 4mo ago project Claude CodeCodex
share on X
ARCHETYPE
Minimalist
Lean instructions, few tools, tiny context tax. Lets the model think.
CONTEXT TAX · EVERY TURN
~685 tokens
Featherweight · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details

Copy this rig

# review before running: this installs third-party code
$ npx degit JayCRL/MobileVC/.claude ./rig-mobilevc  # inspect, then merge into .claude/

MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.

$ curl -fsSL --create-dirs -o .claude/agents/flutter-backend-comm-analyzer.md https://raw.githubusercontent.com/JayCRL/MobileVC/main/.claude/agents/flutter-backend-comm-analyzer.md
$ curl -fsSL --create-dirs -o .claude/agents/flutter-behavior-simulator.md https://raw.githubusercontent.com/JayCRL/MobileVC/main/.claude/agents/flutter-behavior-simulator.md
$ curl -fsSL --create-dirs -o .claude/agents/flutter-integration-analyzer.md https://raw.githubusercontent.com/JayCRL/MobileVC/main/.claude/agents/flutter-integration-analyzer.md
$ curl -fsSL --create-dirs -o .claude/agents/architecture-analyzer.md https://raw.githubusercontent.com/JayCRL/MobileVC/main/mobile_vc/.claude/agents/architecture-analyzer.md

This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 7,204 rigs:

{
  "permissions": {
    "deny": [
      "Read(./.env)",
      "Read(**/.env)",
      "Read(~/.ssh/**)",
      "Bash(rm -rf *)",
      "Read(**/*.pem)",
      "Bash(rm -rf /)",
      "Bash(git push --force:*)",
      "Bash(sudo *)",
      "Read(.env)",
      "Bash(rm -rf /*)",
      "Read(./.env.*)",
      "Read(~/.aws/**)",
      "Bash(git push --force*)",
      "Bash(rm -rf:*)",
      "Read(**/*.key)",
      "Read(**/.env.*)",
      "Bash(sudo:*)",
      "Bash(git reset --hard*)",
      "Bash(git reset --hard:*)",
      "Read(.env.*)"
    ],
    "ask": [
      "Bash(git push:*)",
      "Bash(git push *)",
      "Bash(git commit:*)",
      "Bash(rm *)",
      "Bash(rm:*)",
      "Bash(git rebase *)",
      "Bash(wget *)",
      "Bash(npm publish:*)",
      "Bash(git commit *)",
      "Bash(gh pr merge *)"
    ]
  }
}

Subagents (4)

flutter-backend-comm-analyzer
model: sonnet
Use this agent when the user wants to analyze the communication mechanism between the Flutter client and backend server, evaluate potential plugins/dependencies, and get architectural recommendations
flutter-behavior-simulator
model: sonnet
Use this agent when the user wants to simulate Flutter client network requests against the backend using Python test scripts. This includes scenarios like testing button clicks, sending messages, navi
flutter-integration-analyzer
model: opus
Use this agent for Flutter-backend integration analysis: trace protocols, data models, event flows, or cross-end consistency. Also use for LOG-DRIVEN ROOT CAUSE ANALYSIS — when the user provides a ser
architecture-analyzer
model: sonnet
Use this agent when the user asks to analyze frontend-backend interaction logic, state management, session handling, reconnection mechanisms, or when they want to identify overly complex/entangled log

Similar rigs

copied ✓