ruvnet

Claude-SPARC Automated Development System For Claude Code

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

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

ruvnet

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

ruvnet

# SPARC Agentic Development Rules

Core Philosophy

1. Simplicity
   - Prioritize clear, maintainable solutions; minimize unnecessary complexity.

2. Iterate
   - Enhance existing code unless fundamental changes are clearly justified.

ruvnet

{
  "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

infomiho

Self-hosting is a great way to have control over your deployment infrastructure (you own the data) and a great way to keep the costs down (you pay a fixed amount per month). One of the smoothest way to manage your self-hosted deployment is Coolify.

Deploying Wasp apps to Coolify is straightforward:

• create your Coolify apps (client, server and db)
• build your app's Docker images (e.g. using Github Actions),
• trigger Coolify to pull the Docker images and deploy them.

It'll take you ~1 hour depending on your level of experience with servers and Github Actions.

Installing Coolify

tanhaa

Instructions for a mac on how to play with pyenv and poetry

Why both? Pyenv to manage multiple python versions. You can make virtualenvs with pyenv of course, but using poetry will simplify that process

# Install pyenv.
brew install pyenv

# Add pyenv initializer to shell startup script.
echo -e '\nif command -v pyenv 1>/dev/null 2>&1; then

mecmartini

{% set imagePath = 'public://images/default.jpg' %}
{% set responsiveimagestyle = {
  '#theme': 'responsive_image',
  '#responsive_image_style_id': 'my_responsive_image_style_id',
  '#uri': imagePath,
  '#alt': 'my alt text',
  '#attributes': { class: 'img-responsive' },
} %}
{{ responsiveimagestyle }}

cstroe

A distilled list of open-source CRM software

Source: https://opensource.com/business/16/2/top-6-open-source-crm-tools-2016 + community contributions

EspoCRM `github.com/espocrm/espocrm`_ PHP https://www.espocrm.com

jameswilson

<?php
// Place this file your theme's "templates" folder.

/**
 * @file
 * Theme override to display a pager.
 *
 * This is a backport of pager.html.twig from Drupal 8 to Drupal 7, which add
 * accessibility support for WCAG 2.0 section 2.4.9.
 *

awolfey

CKEDITOR.on('dialogDefinition', function(ev) {
  var dialogName = ev.data.name;
  var dialogDefinition = ev.data.definition;
  var dialog = ev.data.definition.dialog;

  switch (dialogName) {
    case 'image': //Image Properties dialog

      // Require alt text.
      var altField = infoTab.get('txtAlt');