Skip to content

Instantly share code, notes, and snippets.

View coder-r's full-sized avatar
🎯
Focusing

coder-r

🎯
Focusing
4 followers · 4 following
View GitHub Profile
@coder-r
coder-r / claude-sparc.md
Created June 8, 2025 18:54 — forked from ruvnet/*claude.md
The Claude-SPARC Automated Development System is a comprehensive, agentic workflow for automated software development using the SPARC methodology with the Claude Code CLI

Claude-SPARC Automated Development System For Claude Code

Overview

The SPARC Automated Development System (claude-sparc.sh) is a comprehensive, agentic workflow for automated software development using the SPARC methodology (Specification, Pseudocode, Architecture, Refinement, Completion). This system leverages Claude Code's built-in tools for parallel task orchestration, comprehensive research, and Test-Driven Development.

Features

  • Comprehensive Research Phase: Automated web research using parallel batch operations
  • Full SPARC Methodology: Complete implementation of all 5 SPARC phases
@coder-r
coder-r / VS-MCP.md
Created April 18, 2025 11:21 — forked from ruvnet/VS-MCP.md
This comprehensive guide outlines how to create a Model Context Protocol (MCP) server for VSCode that enables multiple workspaces or codespaces to collaborate seamlessly through STDIO communication. The implementation supports shared terminals, extension state synchronization, and collaborative editing.

Building a VSCode Remote Access MCP Server for Collaborative Agentic Development

Before diving into the implementation, let's understand what makes this solution valuable: it creates a bridge between isolated development environments, enabling real-time collaboration without the limitations of traditional remote development approaches.

MCP Server Architecture

The MCP (Model Context Protocol) server architecture consists of several key components that work together to facilitate communication between multiple VSCode instances:

  1. A centralized MCP server that handles message routing and state synchronization
  2. Client connections from multiple workspaces or codespaces
@coder-r
coder-r / .roomodes.json
Created April 16, 2025 09:49 — forked from ruvnet/.roomodes.json
This guide introduces Roo Code and the innovative Boomerang task concept, now integrated into SPARC Orchestration. By following the SPARC methodology (Specification, Pseudocode, Architecture, Refinement, Completion) and leveraging advanced reasoning models such as o3, Sonnet 3.7 Thinking, and DeepSeek, you can efficiently break down complex proj…
{
"customModes": [
{
"slug": "sparc",
"name": "⚡️ SPARC Orchestrator",
"roleDefinition": "You are SPARC, the orchestrator of complex workflows. You break down large objectives into delegated subtasks aligned to the SPARC methodology. You ensure secure, modular, testable, and maintainable delivery using the appropriate specialist modes.",
"customInstructions": "Follow SPARC:\n\n1. Specification: Clarify objectives and scope. Never allow hard-coded env vars.\n2. Pseudocode: Request high-level logic with TDD anchors.\n3. Architecture: Ensure extensible system diagrams and service boundaries.\n4. Refinement: Use TDD, debugging, security, and optimization flows.\n5. Completion: Integrate, document, and monitor for continuous improvement.\n\nUse `new_task` to assign:\n- spec-pseudocode\n- architect\n- code\n- tdd\n- debug\n- security-review\n- docs-writer\n- integration\n- post-deployment-monitoring-mode\n- refinement-optimization-mode\n\nValidate:\n✅ Files < 500 lines\n✅ No hard-coded