jacobparis

sandbox.sh

Run Claude in an isolated Vercel Sandbox with full git access.

It uses the sandbox ID (sbx_asdfasdfasdf) as the branch name, so it's safe to push and then you can get your changes by pulling them from that branch

Examples

Test permissions are set up properly

Nadiar

Bootstrapping the Context System

This guide shows how to implement the two-tier context system (workspace + projects) in a new multi-root workspace.

Quick Overview

The context system consists of:

• Machine-optimized context maps - Auto-generated, compressed memory files
• SessionStart hooks - Automatically regenerate context on every session
• Two-tier structure - Workspace-wide + project-specific contexts

AshikNesin

Gemini CLI Integration for Claude Code MCP Server

A complete setup guide for integrating Google's Gemini CLI with Claude Code through an MCP (Model Context Protocol) server. This provides automatic second opinion consultation when Claude expresses uncertainty or encounters complex technical decisions.

Usage

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

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

kleneway

@cursor-tasks.md Go through each story and task in the cursor-tasks.md file. Find the next story to work on. Review each unfinished task, correct any issues or ask for clarifications (only if absolutely needed!). Then proceed to create or edit files to complete each task. After you complete all the tasks in the story, update the file to check off any completed tasks. Run builds and commits after each story. Run all safe commands without asking for approval. Continue with each task until you have finished the story, then stop and wait for me to review. 

ChristopherA

Git Worktree Best Practices and Tools

Last Updated: 2024-02-06

Overview

Git worktrees allow you to check out multiple branches simultaneously in separate directories, while sharing a single .git metadata store.

THere are some best practices, useful Git aliases, and shell functions for efficiently managing Git worktrees. It covers:

• Setting up Git aliases for worktree operations.
• Using shell functions for enhanced worktree management.

Zerg00s

// Get SharePoint List Fields in a table
function getListSchema(listName) {
    var siteUrl = _spPageContextInfo.webAbsoluteUrl;
    var endpointUrl = `${siteUrl}/_api/web/lists/getbytitle('${listName}')/fields?$filter=Hidden eq false`;

    fetch(endpointUrl, {
        method: 'GET',
        headers: {
            'Accept': 'application/json;odata=nometadata',
            'Content-Type': 'application/json;odata=verbose',

Zerg00s

{
	"info": {
		"_postman_id": "7f9a258e-feee-40a7-827f-760caa441e43",
		"name": "Cognitive Search API Reusable",
		"schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json",
		"_exporter_id": "641744"
	},
	"item": [
		{
			"name": "Create SharePoint Data Source",