Skip to content
/

roo-code-community (James-Cherished-Inc)

james-cherished-roo-community · James-Cherished-Inc/roo-code-community · ★ 0 · last commit 2025-12-11

Community hub for Roo Code users: one-command custom mode installation, Perplexity MCP setup, and a web UI for managing .roomodes configurations.

Best whenMode configuration should have a visual editor with redundancy analysis, not just a text file.
Skip ifBuilding custom research modes when MCP provides better integration
vs seeds
agent-os(Archetype 4 — markdown scaffold) for providing configuration artifacts without orchestration, but james-cherished-roo-c…
Primitive shape 4 total
MCP tools 4
00

Summary

roo-code-community (James-Cherished-Inc) — Summary

roo-code-community is a Roo Code community hub repository maintained by James-Cherished-Inc, providing three things: (1) a .roomodes file users can curl to instantly get a curated set of custom Roo Code modes, (2) a Perplexity MCP Server/ directory with a one-click bash installer (setup-perplexity-mcp.sh) that configures the official Perplexity MCP server (4 tools: perplexity_ask, perplexity_search, perplexity_research, perplexity_reason) in Roo Code, and (3) a Custom-Modes-Visualizer/ — a full React 19 + TypeScript + Tailwind web application (deployed via Cloudflare Workers, Vite-built) for viewing, editing, and managing Roo Code custom modes with features like table/smart views, redundancy analysis, YAML/JSON import-export, and a family system for organizing modes. The repository serves as a personal community aggregation point, not a framework; it explicitly invites contribution via PR and links to other Roo Code projects. Compared to the seeds, it is closest to agent-os (Archetype 4 — markdown scaffold + tooling conveniences) but uniquely ships a production web app as its primary UI surface for managing mode configurations — an approach not found in any seed framework.

01

Overview

roo-code-community (James-Cherished-Inc) — Overview

Origin

Created by James-Cherished-Inc (GitHub user / X: @JamesCherished), published December 2025, last updated December 2025. Stars: 0. The repository is described as "Roo Community, Welcome!" — a community aggregation point for Roo Code users.

Philosophy

The README is explicitly community-facing:

"Get my Custom Crew to replace Roo's default modes instantly in your workspace by running this single command..."

"Please give credit to the respective owners of the work you use or draw inspiration from, when possible."

"Please open a PR or contact me on X (@JamesCherished) to have your project included here."

The framework is not opinionated about development methodology. Its purpose is:

  1. Convenience: one curl command to install curated custom modes
  2. Discovery: aggregates Roo Code community projects
  3. Tooling: ships a web UI for managing .roomodes configurations

Deprecation Notes

The README archives two previous projects from this author:

  1. Researcher mode — integrated Perplexity for web search; deprecated because Roo Code's MCP integration made it redundant
  2. Task-Master — Jira-like task management; deprecated in favor of the evolved taskmaster-ai community project

Key Design Opinions

  1. Single-command installation is paramount — the curl install pattern (curl -L -o .roomodes <url>) makes adoption frictionless
  2. MCP over built-in modes — deprecated mode-based research in favor of Perplexity MCP server
  3. Web UI for prompt engineering — the Custom-Modes-Visualizer is a first-class tool, not an afterthought

Target Audience

Individual developers new to Roo Code who want pre-made custom modes and MCP integrations without configuration effort. Also prompt engineers who want a visual interface for managing .roomodes files.

02

Architecture

roo-code-community (James-Cherished-Inc) — Architecture

Distribution Type

bash-script-bundle — three separate install mechanisms for three separate components.

Install — Custom Modes

# Install .roomodes directly to workspace root
curl -L -o .roomodes https://raw.githubusercontent.com/James-Cherished-Inc/roo-code-community/main/.roomodes.

Note: The URL in README has a trailing period (.) which appears to be a typo. Actual file path is .roomodes.

Install — Perplexity MCP Server

# Clone or download
chmod +x "Perplexity MCP Server/setup-perplexity-mcp.sh"
./setup-perplexity-mcp.sh
# OR with API key:
./setup-perplexity-mcp.sh YOUR_API_KEY_HERE

Install — Custom Modes Visualizer (local dev)

# In Custom-Modes-Visualizer/
npm install
npm run dev   # Vite dev server

Repository Structure

roo-code-community/
├── README.md
├── RooCode-Badge-blk.svg
├── RooCode-Badge-white.svg
├── package-lock.json
├── Perplexity MCP Server/
│   ├── README.md
│   └── setup-perplexity-mcp.sh    # One-click Perplexity MCP installer
│
└── Custom-Modes-Visualizer/        # React web app
    ├── src/
    │   ├── App.tsx
    │   ├── components/             # Table, Smart view, form components
    │   ├── context/               # React context for mode state
    │   ├── data/                  # Mode data and defaults
    │   ├── pages/                 # Main views
    │   ├── test/
    │   ├── types.ts
    │   └── utils/
    ├── package.json               # React 19 + TypeScript + Tailwind + Vite
    ├── vite.config.ts
    ├── wrangler.jsonc             # Cloudflare Workers deployment config
    ├── vitest.config.ts
    └── tailwind.config.js

Note: The .roomodes file mentioned in the README (curl -L -o .roomodes) does NOT appear in the repository root listing — it may be hosted elsewhere or the URL has a typo.

Required Runtime

  • Custom Modes: Roo Code extension (VS Code)
  • Perplexity MCP: Node.js + npm + Perplexity API key
  • Visualizer: Node.js + npm (dev) or Cloudflare Workers (prod)

Target AI Tools

  • Roo Code (primary)
  • The Visualizer is tool-agnostic (manages .roomodes JSON files)

Tech Stack (Custom-Modes-Visualizer)

  • React 19
  • TypeScript
  • Tailwind CSS
  • Vite (build)
  • Cloudflare Workers (deployment)
  • Vitest (testing)
03

Components

roo-code-community (James-Cherished-Inc) — Components

Custom Modes (.roomodes)

The repository distributes a .roomodes file (exact content not in public repository listing — accessible via the curl URL referenced in README). The README describes it as "the Cherished Family" of custom modes designed to "replace Roo's default modes instantly."

Perplexity MCP Server

File Purpose
Perplexity MCP Server/setup-perplexity-mcp.sh One-click bash installer for official Perplexity MCP
Perplexity MCP Server/README.md Guide, examples, troubleshooting

4 tools configured by the installer:

  • perplexity_ask — Smart conversations with sonar-pro
  • perplexity_search — Enhanced web search with metadata
  • perplexity_research — Deep research with sonar-deep-research
  • perplexity_reason — Reasoning with sonar-reasoning-pro

The installer:

  • Checks Node.js + npm prerequisites
  • Validates Perplexity API key
  • Finds Roo Code config directory
  • Creates/updates mcp_settings.json
  • Creates backup of existing config
  • Tests the server

Custom-Modes-Visualizer (React web app)

Key Features:

  • Table View — inline editing of all modes with family filtering
  • Smart View — deep editing with cross-mode redundancy analysis
  • Prompt Builder — custom prompt construction (in development)
  • Import/Export — YAML/JSON support with selective mode export
  • Family System — organize modes into color-coded families
  • Redundancy Analysis — interactive highlighting of repeated words across modes
  • Global Config — set instructions applying to all modes
  • Auto-Save — instant persistence with localStorage backup

Tech Stack: React 19, TypeScript, Tailwind CSS, Vite, Cloudflare Workers

Deployment: Deployed to Cloudflare Workers (wrangler.jsonc config present)

Scripts

File Purpose
Perplexity MCP Server/setup-perplexity-mcp.sh Bash script — installs Perplexity MCP server into Roo Code config

Archived/Deprecated Projects

Project Status Reason
Researcher mode Deprecated Roo Code MCP integration supersedes it
AI-task-master Deprecated Author stopped using it

Total Component Count

  • Custom mode files: 1 (.roomodes — exact modes unknown, not in public listing)
  • MCP installer scripts: 1
  • Web app: 1 (Custom-Modes-Visualizer)
  • MCP tools configured: 4 (Perplexity)
05

Prompts

roo-code-community (James-Cherished-Inc) — Prompts

Note on Prompt Availability

The .roomodes file referenced in the README is not present in the repository's public file listing (the curl URL in the README has a trailing period that may be a typo). The exact mode definitions and their roleDefinition prompts are not accessible for direct analysis. The following excerpts come from the non-mode components.


Excerpt 1: Perplexity MCP Installer — Agent Interaction Pattern (setup-perplexity-mcp.sh)

#!/bin/bash
set -e

# Function to get OS type
get_os() {
    case "$(uname -s)" in
        Darwin*)    echo "macOS" ;;
        Linux*)     echo "Linux" ;;
        CYGWIN*|MINGW*|MSYS*) echo "Windows" ;;
        *)          echo "Unknown" ;;
    esac
}

# Finds Roo Code config directory across platforms
# Creates or updates mcp_settings.json with 4 Perplexity tools:
# - perplexity_ask (sonar-pro)
# - perplexity_search (enhanced search with metadata)
# - perplexity_research (sonar-deep-research)
# - perplexity_reason (sonar-reasoning-pro)

Script technique: Cross-platform installer with colored terminal output (ANSI codes), prerequisite validation, API key validation, config backup before overwrite, and success/failure feedback. The script is the "prompt" in the sense that it creates the MCP configuration that will be available to AI agents.


Excerpt 2: Custom Modes Visualizer — Redundancy Analysis Feature

The README describes the Smart View as providing:

"Deep editing with cross-mode redundancy analysis" "Redundancy Analysis: Interactive highlighting of repeated words across modes"

This feature is designed to help prompt engineers identify when the same instructions appear in multiple modes — a quality gate for .roomodes prompt engineering. While no code excerpt is available here, the UI feature itself is a prompting-methodology tool: it surfaces repeated instructions across mode roleDefinition and customInstructions fields.


Excerpt 3: README — Deprecated Researcher Mode Design Philosophy

### **Researcher** by @JamesCherished: Integrates Perplexity for web search and Lynx for 
page analysis, enabling autonomous research-augmented software engineering
https://github.com/James-Cherished-Inc/roo-research-mode

    * requires : Perplexity pro or Perplexity API
    * cost : a few cents per search for Perplexity

--> deprecated, as Roo Code's new integration for MCP (2025) allows for a more 
efficient use of Perplexity.

Design insight: The shift from embedded-mode research (Researcher mode with Perplexity and Lynx) to MCP-based research (official Perplexity MCP server) reflects the evolution of the Roo Code ecosystem — functionality that previously required custom mode definitions is now available via the MCP protocol.

09

Uniqueness

roo-code-community (James-Cherished-Inc) — Uniqueness

Differs From Seeds

This repository doesn't fit cleanly into any of the 5 archetypes from the seed comparison. The closest is agent-os (Archetype 4 — markdown scaffold, zero primitives) in that it provides configuration artifacts without hooks, commands, or skills. But it differs in one critical dimension: it ships a production web application (Custom-Modes-Visualizer) for managing those configuration artifacts. No seed ships a dedicated UI tool for managing its own configuration format.

The Perplexity MCP installer is architecturally similar to what ccmemory (seed) does for Neo4j — providing a scripted setup for an external service that provides capabilities to the AI. But ccmemory's MCP gives the AI a memory store; this gives the AI web search/research capabilities.

The Custom-Modes-Visualizer as Differentiator

Among all 7 frameworks in this batch and all 11 seeds, the Custom-Modes-Visualizer is the only dedicated prompt engineering UI for Roo Code custom modes. It provides:

  • Redundancy analysis across mode definitions (detects when the same instruction appears in multiple modes)
  • Family-based organization with color coding
  • Export in multiple formats (YAML/JSON)

This positions the repository not as a "framework" but as a "toolchain" — it provides the modes themselves AND the tool to manage them.

Positioning

  • Niche: Roo Code users who want a visual editor for custom modes
  • Key differentiator: Only project in corpus to ship a web app for managing AI agent mode configurations
  • Limitation: Zero stars suggest low adoption; the .roomodes file appears to have a broken URL in the README

Observable Failure Modes

  1. Broken curl URL — README's .roomodes URL ends with a period (typo), making the primary install method broken
  2. Zero stars, zero documented modes — the "Cherished Family" of modes is mentioned but exact content is not in the repo
  3. Deprecation announcements — two listed components are already deprecated, suggesting active churn
  4. Visualizer maturity — Prompt Builder listed as "in development"
  5. No methodology — without a development philosophy or workflow guidance, the repository's value depends entirely on the quality of the .roomodes file, which is undocumented

Cross-References

  • References taskmaster-ai (seed) in the deprecated section
  • Shares Roo Code targeting with roomodes-sellisd and roo-code-vibook in this batch
  • The Perplexity MCP installer pattern is analogous to roomodes-sellisd's mcp-config installer
04

Workflow

roo-code-community (James-Cherished-Inc) — Workflow

Installation Workflow

There are three independent install paths:

Path 1: Custom Modes

Step Action Artifact
1 Run: curl -L -o .roomodes <url> .roomodes file in workspace root
2 Open workspace in Roo Code Custom modes available in mode picker
3 Select desired mode Mode-specific behavior active

Path 2: Perplexity MCP

Step Action Artifact
1 Run setup-perplexity-mcp.sh <API_KEY> mcp_settings.json updated
2 Restart Roo Code Perplexity MCP tools available
3 Use in any mode 4 Perplexity tools accessible

Path 3: Custom Modes Visualizer

Step Action Artifact
1 Open web app (local dev or Cloudflare deployed) Visualizer UI
2 Import .roomodes file Modes displayed in table
3 Edit modes, analyze redundancy Edited modes
4 Export as YAML/JSON Updated .roomodes
5 Copy to workspace Updated modes in Roo Code

Approval Gates

None. All installs are one-shot commands.

Phase-to-Artifact Map

Phase Artifact
Custom modes install .roomodes in workspace
Perplexity MCP setup Updated mcp_settings.json
Visualizer: import Modes loaded in UI
Visualizer: edit Updated mode definitions
Visualizer: export .roomodes or YAML/JSON file

No Development Methodology

This framework does not prescribe any development phases, spec formats, or agent workflows. It is purely a configuration and tooling distribution.

06

Memory Context

roo-code-community (James-Cherished-Inc) — Memory & Context

Memory Mechanism

No dedicated agent memory system.

The Custom-Modes-Visualizer uses browser localStorage for auto-save of mode edits:

"Auto-Save: Instant persistence with localStorage backup"

This is UI state persistence, not agent memory.

Persistence

Component Storage Lifetime
Custom modes .roomodes file in workspace Project-scoped
Perplexity MCP config mcp_settings.json in Roo Code config dir Global (all workspaces)
Visualizer edits Browser localStorage Browser session (until export)

Cross-Session Continuity

The .roomodes file persists custom modes across Roo Code sessions. The Perplexity MCP configuration is global (all workspaces). No agent-specific memory or context accumulation.

State Files

None created dynamically by agents. All state is configuration files.

Memory Type

File-based configuration only. No database, no vector store, no cross-session context accumulation.

Context Injection

The custom modes in .roomodes inject their roleDefinition and customInstructions into Roo Code sessions automatically when that mode is selected. This is the closest analog to "context injection" in this framework.

07

Orchestration

roo-code-community (James-Cherished-Inc) — Orchestration

Multi-Agent Pattern

None. The framework distributes configuration files and a UI tool; it does not define or coordinate agents.

Execution Mode

  • Custom modes: interactive-loop (user selects mode, Roo Code uses it)
  • Perplexity MCP: event-driven (tools available when invoked in any mode)
  • Visualizer: one-shot (edit → export → apply)

Isolation

None.

Multi-Model Routing

None defined. Whatever model the user has configured in Roo Code.

Prompt Chaining

None.

Orchestration Pattern

none

The "Community" Pattern

Unlike frameworks that orchestrate agents, this repository orchestrates community resources: it aggregates links, projects, and tooling from the Roo Code community under one URL. The orchestration is human-curated rather than automated.

Consensus

None.

08

Ui Cli Surface

roo-code-community (James-Cherished-Inc) — UI / CLI Surface

Dedicated CLI Binary

None for the framework itself.

Local Web Dashboard / App

Custom-Modes-Visualizer — a full React 19 web application:

Feature Description
Table View Inline editing of all modes with family filtering
Smart View Deep editing with cross-mode redundancy analysis
Prompt Builder Custom prompt construction (in development)
Import/Export YAML/JSON with selective mode export
Family System Organize modes into color-coded families
Redundancy Analysis Interactive highlighting of repeated words across modes
Global Config Instructions applying to all modes
Auto-Save localStorage persistence

Stack: React 19, TypeScript, Tailwind CSS, Vite
Deployment: Cloudflare Workers (wrangler.jsonc config present)
Port: 5173 (Vite default dev port)

Shell Script

setup-perplexity-mcp.sh — colored terminal output installer:

chmod +x setup-perplexity-mcp.sh
./setup-perplexity-mcp.sh [API_KEY]

Features: prereq checks, API key validation, config directory detection (macOS/Linux/Windows), backup, test connection.

IDE Integration

Roo Code (VS Code):

  • .roomodes is read by Roo Code automatically
  • Perplexity MCP tools available in any mode after MCP setup

Web App vs. IDE

The Custom-Modes-Visualizer is the most notable UI surface in this batch outside of cursor/plugins. It runs in a browser (or could be deployed to Cloudflare), provides a first-class editing interface for .roomodes JSON, and is deployed as a standalone web application.

The Vite config and wrangler.jsonc suggest the app is deployed at a public URL (not documented in README).

Testing

vitest.config.ts present — the web app has a test suite.

Related frameworks

same archetype · same primary tool · same memory type

BMAD-METHOD ★ 48k

Provides a full agile delivery lifecycle with named expert-persona AI collaborators that elicit the human's best thinking rather…

Agent OS ★ 4.6k

Extracts implicit codebase conventions into token-efficient markdown standards files and injects them selectively into AI agent…

Claude Conductor ★ 367

Gives Claude Code a persistent, cross-linked, auto-analyzed documentation system so it retains codebase context across sessions.

Spec-Driver (Greenfield Spec-Driven Development) ★ 25

Prevents spec rot in AI-assisted development by making implementation changes flow back into evergreen, authoritative specs via…

Anthropic Knowledge Work Plugins ★ 16k

Role-specialized plugin bundles with live MCP connectors that turn Claude into a domain expert for enterprise knowledge workers.

Codex Integration for Claude Code (skill-codex) ★ 1.3k

Single Claude Code skill that handles Codex CLI invocation correctly (stdin blocking, thinking token suppression, session resume)…