Dan Capri MFD3000

Delete unused or obsolete files when your changes make them irrelevant (refactors, feature removals, etc.), and revert files only when the change is yours or explicitly requested. If a git operation leaves you unsure about other agents' in-flight work, stop and coordinate instead of deleting.
Before attempting to delete a file to resolve a local type/lint failure, stop and ask the user. Other agents are often editing adjacent files; deleting their work to silence an error is never acceptable without explicit approval.
NEVER edit .env or any environment variable files—only the user may change them.
Coordinate with other agents before removing their in-progress edits—don't revert or delete work you didn't author unless everyone agrees.
Moving/renaming and restoring files is allowed.
ABSOLUTELY NEVER run destructive git operations (e.g., git reset --hard, rm, git checkout/git restore to an older commit) unless the user gives an explicit, written instruction in this conversation. Treat t

Backend as a Service

Supabase - ~52K stars

Designed explicitly as an open source firebase alternative
Typescript based
Docker support

Appwrite - ~32K stars

Written in JavaScript and PHP
Docker based
Realtime support across all services

Intro

This guide is specific to getting LND 0.5-beta and Bitcoind running on Ubuntu 16.04 LTS for mainnet. It is aging rapidly and includes steps not necessary on newer versions of LND. As of April 2021 it is very out of date for bitcoind. As of December 2021 it is outdated for LND too.

Original installation guide:

https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md

This guide is broken into the following sections:

Install bitcoind and set to start automatically
Install development tools and dependancies

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

	import anthropic
	import os
	import sys
	from termcolor import colored
	from dotenv import load_dotenv


	class ClaudeAgent:
	def __init__(self, api_key=None, model="claude-3-7-sonnet-20250219", max_tokens=4000):
	"""Initialize the Claude agent with API key and model."""

	# Windsurf Memory System: Advanced Coding Assistant

	I am Windsurf, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This drives me to maintain perfect documentation through the Windsurf Memory System. After each reset, I rely ENTIRELY on my Memory Bank to understand projects and continue work effectively. I MUST read ALL memory bank files at the start of EVERY task - this is not optional.

	## Core Identity and Operating Principles

	1. Memory-Driven Architecture: After each reset, you MUST read ALL memory bank files to regain context.
	2. Documentation Excellence: Maintain impeccable records as your future self depends entirely on them.
	3. Rigorous Performance Standards: Never compromise on quality standards or evaluation criteria.
	4. Structured Problem-Solving: Follow defined workflows and methodologies for all tasks.